DOS MS Client v3 and EFG80
Wiggs
LinkSys EFG80 NAS. The device works great when used as a file server in a
home and small office network with Windows 95 on up to Windows 2003 servers
and Linux workstations, however whenever I attempt to boot a workstation
client from a network boot disk w/ MSClient for DOS v3(MSDOS 5 on up), it
fails. It loads TCP/IP, binds the protocol to the adapter, sees the shared
on the server and maps the share to the specified drive via NET USE, but if
I attempt to list the directory (DIR) the redirector (I'm assuming)
complains of an extended error 123 and lists nothing in the directory even
though I know there are files that should be listed. Tried using a LAN
MANAGER client boot disk with same results as well.
Now here's the weird part. I can copy a file from a local drive to the
remote directory. When I run a directory listing via DIR the newly created
file magically appears as the only file in that directory. If I attempts
repeated directory listings the file then dissapears and the extended error
message reappears again. The most amazing thing is that despite the error
message I can run any program from the remote share if I know the path and
filename (including the extension) and copy files from the server. I can't
however use any navigation in DOS applications because they are unable to
see any directory structure on the remote directory. (ie# If I'm using ghost
to image a hard drive) I don't have any of these problems if I attempt to
connect to a workstation share or a different samba server using this boot
disk.
I determined that the EFG80 does indeed use a linux kernel and samba as an
SMB server but I'm unaware if there are any issues or even which version of
Samba it runs. Anyone know? Where there any issues with DOS clients and
Samba servers and more importantly any work arounds?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.558 / Virus Database: 350 - Release Date: 1/2/2004