Skip to contentSkip to conversation

tcp/ip + samba + dosemu

DISCUSSION Stas Sergeev 2 participants 3 messages Jun 24, 2006 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hello.

Quoted 1 line · Rafaе┌ Cygnarowski

DosEMU and Samba behaviour. But to use them all at the same time I *MUST* be able to run some Samba client under DosEMU. And question is: HOW?! Have ANYONE succeed with this?

Calm down, your problem is not with the samba client but with that you have not set up the tcp/ip properly. You choose the same address for the DOS client and the tap device (192.168.1.1, from your first message), and that can't work.
And before you ask - yes, there *is* an uptodate docs about that, but they were kept in secret for years. You won't find them pretty much anywhere in the net - what you will find is completely wrong and misleading. But if you get the latest dosemu sources from SVN and execute "make docs", the chances are it will generate the real docs for you (you will also have to search the source tree to find out exactly where it generated it - the obvious place will still contain an old docs, so do some searching). Most likely "make docs" will fail though, as the confidence level of these docs is too high. :) I really suspect only about 2-3 people know about their existance.

(CC me with replies, I am not in the list)

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hello.

Quoted 1 line · RafaÅ‚ Cygnarowski

Honestly... I will not care about Waterloo TCP/IP unless there be some samba client which uses packet driver :( Do you know such client? Or how to connect to samba server using eg. LanManager?

I think the only way is what you are already trying - odihlp. I looked up a couple of your messages but haven't found how it fails for you. The only problem I can remember getting it to work myself was that it required the very latest version of pdether which was difficult to find in the net.

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 10 lines
Quoted 3 lines · Rafał Cygnarowski

Honestly... I will not care about Waterloo TCP/IP unless there be some samba client which uses packet driver :( Do you know such client? Or how to connect to samba server using eg. LanManager?

I think the only way is what you are already trying - odihlp. I looked up a couple of your messages but haven't found how it fails for you. The only problem I can remember getting it to work myself was that it required the very latest version of pdether which was difficult to find in the net.

I found it: pdether v1.05 - pde105.zip somewhere... :) I don't remember now where.

My tries (current tries):

A. Environment:

- MSClient from ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT
- dosemu-1.3.3-1.i686
- kernel-2.6.16.20-1.athlon
- guest OS: MS-DOS 6.20
- pdether v1.05
- lsl.com v2.20 from Novell Client for DOS
(http://www.novell.com/coolsolutions/tools/downloads/dw271e.zip)
- odihlp.exe from Windows for Workgroups 3.11

B. How it is started?

1. config.sys content:

DEVICE=C:\NET\ifshlp.sys
DEVICE=C:\NET\PROTMAN.DOS /i:C:\NET
REM - in normal situation here should be NDIS driver loaded DEVICE=C:\NET\nemm.dos
DEVICE=C:\NET\tcpdrv.dos /i:C:\NET

and output produced:
Microsoft DOS TCP/IP NEMM Driver 1.0
Microsoft DOS TCP/IP Protocol Driver 1.0a
Copyright (c) Microsoft Corporation, 1991. All rights reserved. Copyright (c) Hewlett-Packard Corporation, 1985-1991. All rights reserved. Copyright (c) 3Com Corporation, 1985-1991. All rights reserved.

2. c:\net\net initialize
The command completed successfully.

3. c:\net\lsl
Novell Link Support Layer for DOS ODI v2.20 (960401)
(c) Copyright 1990 - 1996, by Novell, Inc. All rights reserved.

BUFFERS 8 1600
The configuration file used was "C:\NET\NET.CFG". Max Boards 4, Max Stacks 4
Buffers 8, Buffer size 1600 bytes, Memory pool 0 bytes.

4. c:\net\pdether
Ethernet Packet Driver MLID, v1.05, built Mar 20 1995 at 12:55:52 PDEther installed successfully.

5. c:\net\odihlp.exe
Microsoft WorkGroups ODI/NDIS3 Mapper Version 1.0
Copyright (C) Microsoft Corporation 1993
Powiązany z adapterem: PDETHER

6. c:\net\netbind.com
MS-DOS LAN Manager v2.1 Netbind
Error: 33 Unable to bind.
^^^^^^^^^^^^^^^^^^^^^^^^^
And here problem starts. Acording to
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1998090116540425
it's some kind of problem with my config files. Document above describes error messages for netbind.exe which comes from another software - I hope these messages are equal.

C. Config files

1. c:\net\net.cfg

Link Support

	Buffers 8 1600

Link Driver PDETHER
Int 60
Frame Ethernet_II
Protocol IP 800 Ethernet_II
Protocol ARP 806 Ethernet_II
Protocol RARP 8035 Ethernet_II

2. c:\net\protocol.ini

[network.setup]
version=0x3110
netcard=ms$odimac,1,MS$ODIMAC,4
transport=ms$ndishlp,MS$NDISHLP
transport=tcpip,TCPIP
lana0=ms$odimac,1,ms$ndishlp
lana1=ms$odimac,1,tcpip

[TCPIP]
NBSessions=6
SubNetMask0=255 0 0 0
IPAddress0=0 0 0 0
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=pdether
LANABASE=1

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=pdether

[net.cfg]
PATH=C:\net\net.cfg

[MS$ODIMAC]

[pdether]
DriverName=PDETHER$

[Link Driver PDETHER]
data=Frame Ethernet_II
data=Link Driver PDETHER

3. c:\net\system.ini

[network]
sizworkbuf=1498
filesharing=no
printsharing=no
autologon=yes
computername=TESTER
lanroot=C:\NET
username=TESTER
workgroup=WORKGROUP
reconnect=yes
dospophotkey=N
lmlogon=0
logondomain=WORKGROUP
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
; netcard=elnk.dos -- original driver
transport=ndishlp.sys,tcpdrv.dos,nemm.dos
devdir=C:\NET
LoadRMDrivers=yes

[386enh]
TimerCriticalSection=5000
UniqueDosPSP=TRUE
PSPIncrement=2

[Password Lists]
*Shares=C:\NET\Shares.PWL

Signature · 6 lines
Rafał Cygnarowski
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html