Occupied
asked on
Native File Access / CIFS and DOS
Hi, I've setup a Netware 6.0 SP5 server with Native File Access, I have applied update: cifspt5 TID2968723 also...
When I try to map a drive from DOS to the Netware server I get this error by NET.EXE: "error 58: the network has responded incorrectly."
A search on Novell.com brought up the fact that support for DOS is somewhat experimental but it should work anyway... See TID10077423 for more information on that.
I also found this http://www.novell.com/coolsolutions/netware/qna/client.html#3005519 and tried that update instead (an older cifs.nlm file) but that one gave me this error from NET.EXE instead: "Error 66: The network resource type is incorrect."
The reason I need CIFS support via DOS is because I use Norton Ghost and want to use the Netware server to store the Ghost files on...
I was also trying to mount the server from a Linux 2.6.9 client with the cifs.ko file but that did not work either... It did mount the filesystem but as soon as I tried to transfer anything the computer hung and this message repeated on the Netware console: "WriteX: 356 bytes, inParm->DataLength = 357, errorCode = 94"
The command I used to mount was: mount.cifs /\/\192.168.0.2/\RAID0 /hdd -o user=xxx,password=xxx,rw
TID2968723: http://support.novell.com/cgi-bin/search/searchtid.cgi?/2968723.htm
TID10077423: http://support.novell.com/cgi-bin/search/searchtid.cgi?/10077423.htm
When I try to map a drive from DOS to the Netware server I get this error by NET.EXE: "error 58: the network has responded incorrectly."
A search on Novell.com brought up the fact that support for DOS is somewhat experimental but it should work anyway... See TID10077423 for more information on that.
I also found this http://www.novell.com/coolsolutions/netware/qna/client.html#3005519 and tried that update instead (an older cifs.nlm file) but that one gave me this error from NET.EXE instead: "Error 66: The network resource type is incorrect."
The reason I need CIFS support via DOS is because I use Norton Ghost and want to use the Netware server to store the Ghost files on...
I was also trying to mount the server from a Linux 2.6.9 client with the cifs.ko file but that did not work either... It did mount the filesystem but as soon as I tried to transfer anything the computer hung and this message repeated on the Netware console: "WriteX: 356 bytes, inParm->DataLength = 357, errorCode = 94"
The command I used to mount was: mount.cifs /\/\192.168.0.2/\RAID0 /hdd -o user=xxx,password=xxx,rw
TID2968723: http://support.novell.com/cgi-bin/search/searchtid.cgi?/2968723.htm
TID10077423: http://support.novell.com/cgi-bin/search/searchtid.cgi?/10077423.htm
Dose it work from windows ? (IE. dose it work at all)
ASKER
Yes, it works fine from a Windows 2000 workstation...
ASKER
I should add that the DOS client works fine if I mount a Windows 2000 share... The same goes for the Linux client...
Have you considered using a DOS/WIN Client32 boot disk to login to NetWare and map a drive using NetWare protocols?
ASKER
There is no Novell TCP/IP client for DOS and that would not solve the problem that I can not access the server from my Linux clients either...
I beg to differ. I have made DOS boot disks that log in using IP. The NETX client will only log in using IPX, but the VLM client and the Client32 can be used to log in via IP. Here are a couple of IP boot disk links for you.
http://www.novell.com/coolsolutions/tools/1666.html
http://www.veder.com/nwdsk/
and last, but not least - from Symantec themselves, an IP boot disk for Ghost:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000042409333225?Open&src=&docid=2000110312324125&nsf=ghost.nsf&view=pfdocs&dtype=&prod=&ver=&osv=&osv_lvl=
http://www.novell.com/coolsolutions/tools/1666.html
http://www.veder.com/nwdsk/
and last, but not least - from Symantec themselves, an IP boot disk for Ghost:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000042409333225?Open&src=&docid=2000110312324125&nsf=ghost.nsf&view=pfdocs&dtype=&prod=&ver=&osv=&osv_lvl=
Disregard the Symantec link. They only talk about IPX, the dirty dogs.
The concept is the same, though. Use one of the other IP boot disks and add the Ghost programs to the disk. I believe I had good luck with the nwdisk setup.
The concept is the same, though. Use one of the other IP boot disks and add the Ghost programs to the disk. I believe I had good luck with the nwdisk setup.
ASKER
A program from Symantec would not help as it is not the TCP/IP protocol or NetBEUI protocol that is the problem, it is the CIFS protocol that is at fault here.
And the Linux client still wont be able to connect...
And the Linux client still wont be able to connect...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
But did they make it available for 6.0 servers also?
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10079796.htm