tapkep
asked on
Can't map network share (from MSDOS 6.2 to NT 3.51 Server)
Hello,
Recently I have encountered strange problem - MS-DOS 6.2 workstations can't connect to shared folder on Win NT 3.51 Server. The strange part is, that it happens only when booting:
net start
Cannor reconnect E: to \\SERVER\D (Error 53)
Do you want to continue restoring connections? (Y/N) [Y]:
Do you wish to continue connecting E: to \\SERVER\D
in future logon attempts? (Y/N) [Y]:
When computer boots, i can successfully ping server and map that disk using 'net' utility.
Network cards are 10 Mbps, switch - 3com SuperStack II 3300, ports are manually configured to 10 Mbps HD. Spanning Tree is enabled (if that matters).
Any ideas?
Recently I have encountered strange problem - MS-DOS 6.2 workstations can't connect to shared folder on Win NT 3.51 Server. The strange part is, that it happens only when booting:
net start
Cannor reconnect E: to \\SERVER\D (Error 53)
Do you want to continue restoring connections? (Y/N) [Y]:
Do you wish to continue connecting E: to \\SERVER\D
in future logon attempts? (Y/N) [Y]:
When computer boots, i can successfully ping server and map that disk using 'net' utility.
Network cards are 10 Mbps, switch - 3com SuperStack II 3300, ports are manually configured to 10 Mbps HD. Spanning Tree is enabled (if that matters).
Any ideas?
ASKER
Jonathan, it worked few weeks ago. Now, after 10 reboots, i was able to connect 2 times (8 times got error 53). Server and clients are connected to the same switch.
I will try to add pause before 'net start' in autoexec.
Push, I know how to connect to shared folder. The problem is - I can't do this from autoexec.bat. And yes, it worked 2 weeks ago without problem.
I will try to add pause before 'net start' in autoexec.
Push, I know how to connect to shared folder. The problem is - I can't do this from autoexec.bat. And yes, it worked 2 weeks ago without problem.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did you change your network password ?
ASKER
Jonathan, i tried to put 5 sec pause before "net start" - no effect. tried to move "net start" to autoexec.bat end (it was in the middle, before other drivers, such as keyport, mouse were loaded) - no effect. However, if i executed from command line "net stop" and right then "net start" - everything was ok. :-/
Push - no i haven't.
Push - no i haven't.
tapkep.
Are you by any chance using DHCP?
Jonathan
Are you by any chance using DHCP?
Jonathan
No the end of your "Net USe" statement add /PERSISTANT :NO
Try this inclufing the quotes
net use e: "\\servername\c$" /USER:admin
net use e: "\\servername\c$" /USER:admin
Hi, There
Do you delete share's in the batch files before creating them ?
Do you delete share's in the batch files before creating them ?
If you use /PERSISTANT :NO , you dont need to.
ASKER
No, I am not using DHCP, all IPs are static. Also there are according entries in hosts and lmhosts files.
Shared folder on server was connected to as 'persistent' (so each time it should be reconnected).
Network card is Compex FreedomLine 100TX (DEC chip). I will try to replace it with another NIC later today.
There were certain problems with connecting to this server before (had to slow down port speed to 10Mbps HD). I was able to correct this, but now I can't connect event in 10 Mbps HD mode. And it is 3 computers, all MSDOS 6.2 workstations (Compex FL100TX or FL10TX) with the same problem. There are no problems when connecting from WinNT WS or Win2000Pro.
Have tried connecting workstations to another switch (3com SuperStack3 4400, HP ProCurve 4140gl) - got the same error.
Server I am trying to connect to is Intergraph TD4 with AMD Lance NIC.
Shared folder on server was connected to as 'persistent' (so each time it should be reconnected).
Network card is Compex FreedomLine 100TX (DEC chip). I will try to replace it with another NIC later today.
There were certain problems with connecting to this server before (had to slow down port speed to 10Mbps HD). I was able to correct this, but now I can't connect event in 10 Mbps HD mode. And it is 3 computers, all MSDOS 6.2 workstations (Compex FL100TX or FL10TX) with the same problem. There are no problems when connecting from WinNT WS or Win2000Pro.
Have tried connecting workstations to another switch (3com SuperStack3 4400, HP ProCurve 4140gl) - got the same error.
Server I am trying to connect to is Intergraph TD4 with AMD Lance NIC.
ASKER
Tried Allied Telesyn AT-2501 NIC - does not have functioning DOS drivers :-/ Diagnostic reports, that card is and is functional, but 'net initialize' fails because of incorrect driver. Drivers were from allied telesyn website.
Also have tried to put in autoexec.bat
net use e: \\SERVER\D /persistent:no
net use f: \\SERVER\D /persistent:no
Connecting E: always fails (after timeout) with error 53, connecting F: - successful.
Also have tried to put in autoexec.bat
net use e: \\SERVER\D /persistent:no
net use f: \\SERVER\D /persistent:no
Connecting E: always fails (after timeout) with error 53, connecting F: - successful.
Disconnect E one time then try it
tapkep
Have you tried:
net use * \\server\d /persistent:no
The * should connect to the first available drive.
Jonathan
Have you tried:
net use * \\server\d /persistent:no
The * should connect to the first available drive.
Jonathan
ASKER
Don't forget, that we are talking about DOS... Locally there are only A (fdd), C and D (both hdd). I am sure, that there is no conflict using E: to connect remote share.
That means, that first attempt to connect to server (almost) always fails, while second attempt might be successful. I haven't tried to put * instead of letter (I know this option), but if i leave only "net use F: ...", i get error 53.
OK, happy weekend :)
Till monday... :-/
That means, that first attempt to connect to server (almost) always fails, while second attempt might be successful. I haven't tried to put * instead of letter (I know this option), but if i leave only "net use F: ...", i get error 53.
OK, happy weekend :)
Till monday... :-/
ASKER
Ok, have tried using
net use * \\server\d /persistent:no
net use * \\server\d /persistent:no
First try always fails, while second is successful.
Also tried addind NetBIOS (was only TCP/IP) - no change.
Any more ideas? :)
net use * \\server\d /persistent:no
net use * \\server\d /persistent:no
First try always fails, while second is successful.
Also tried addind NetBIOS (was only TCP/IP) - no change.
Any more ideas? :)
tapkep
Have you tried using the ip address of the computer instead of the NetBios name?
One other thing - I'm not sure if DOS has a "hosts" file - if it does you can try to add an entry into this file. When you do this it doesn't really matter if you use an IP address or a name the OS will translate the name to the associated IP, much like DNS.
Neither of these suggestions should make a difference, but you never know. Especially, when something weird is happening.
Either of these suggestions should eliminate name resolution as a problem.
Jonathan
Have you tried using the ip address of the computer instead of the NetBios name?
One other thing - I'm not sure if DOS has a "hosts" file - if it does you can try to add an entry into this file. When you do this it doesn't really matter if you use an IP address or a name the OS will translate the name to the associated IP, much like DNS.
Neither of these suggestions should make a difference, but you never know. Especially, when something weird is happening.
Either of these suggestions should eliminate name resolution as a problem.
Jonathan
ASKER
More weird things:
net use * \\xxx.xxx.xxx.xxx\d /persistent:no
ALWAYS fails :-/ Even when "net use * \\server\d" is successful.
net use * \\xxx.xxx.xxx.xxx\d /persistent:no
ALWAYS fails :-/ Even when "net use * \\server\d" is successful.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i always do this :
net use G: /delete
net use G: \\server\d
because the persistent parameter was not implemented in all versions of the net command
net use G: /delete
net use G: \\server\d
because the persistent parameter was not implemented in all versions of the net command
Could be a permissions/security timing issue?? Try this to verify:
net use f: \\server\d /USER:MYDOMAIN\username password
there is a space between username and password
net use f: \\server\d /USER:MYDOMAIN\username password
there is a space between username and password
ASKER
alextesi, i have tried including 5 and 10 seconds pause in autoexec.bat before calling 'net start' or 'net use'. Have not helped.
crissand, i have tried connecting computer to 3com SuperStack3 4400 and HP ProCurve 4148gl switches. The same. Ports are already configured as 10MBps HD (was auto, NIC is 10/100). Setting to HD helped for some time, but now i have problems even with 10 HD.
For spanning tree - i can't turn it off, since there are port trunks configured on each switch, can i?
elconomeno, /persistent works in my case.
Mazaraat, no additional persissions (or change) since everything worked. If it was the case - why only *first* attempt fails, while second is successful?
crissand, i have tried connecting computer to 3com SuperStack3 4400 and HP ProCurve 4148gl switches. The same. Ports are already configured as 10MBps HD (was auto, NIC is 10/100). Setting to HD helped for some time, but now i have problems even with 10 HD.
For spanning tree - i can't turn it off, since there are port trunks configured on each switch, can i?
elconomeno, /persistent works in my case.
Mazaraat, no additional persissions (or change) since everything worked. If it was the case - why only *first* attempt fails, while second is successful?
As I understand you use packet driver on the msdos workstation and netbios over tcp/ip to connect to nt3.51 server. That works and now it's not working.
If you did'n't change nothing on the server or workstation then the problem must be with the connection. Maybe the cable connection is faulty, try to change the patch and move the computer in another coupler.
If you did'n't change nothing on the server or workstation then the problem must be with the connection. Maybe the cable connection is faulty, try to change the patch and move the computer in another coupler.
ASKER
Found similar problem:
--------------------------
Q: When I power on my PC, I get the message "a file server could not be found." How do I fix that?
This is a well-known issue given the following situation:
1. The PC is directly-connected to a switch
2. The PC is running Novell's VLMs or Client32
3. The switch has Spanning Tree Protocol (STP) enabled
In this situation, when the directly-connected PC is powered on, the switch senses linkbeat on that port. This causes the switch to go through the four Spanning Tree states: blocking, listening, learning, and forwarding. It takes 30 seconds for the switch to complete that sequence and begin forwarding packets to and from that port. During those 30 seconds, Novell sends 3 requests for a server, then stops looking. By the time Spanning Tree completes its job, Novell reports that "a file server could not be found".
There are several workarounds available:
1. Disable Spanning Tree on the switch (if Spanning Tree is not needed, i.e. no loops in the network topology).
2. For VLMs, add a "pause" just after calling VLM.EXE in STARTNET.BAT. When the user reboots a PC, have them wait at least 30 seconds before continuing the sequence. This workaround is documented on Novell's Knowledgebase (www.support.novell.com, search for document 2920460).
3. For Client32, add a registry entry in the PC, as documented on Novell's Knowledgebase (search for document 2925582).
--------------------------
Well, i don't use Novell. But the problem seems like i need to wait at least 30 seconds before trying to connect to other computers. (quite strange, since i can ping them).
SuperStack II 3300 seems to support only STP (no RSTP)...
--------------------------
Q: When I power on my PC, I get the message "a file server could not be found." How do I fix that?
This is a well-known issue given the following situation:
1. The PC is directly-connected to a switch
2. The PC is running Novell's VLMs or Client32
3. The switch has Spanning Tree Protocol (STP) enabled
In this situation, when the directly-connected PC is powered on, the switch senses linkbeat on that port. This causes the switch to go through the four Spanning Tree states: blocking, listening, learning, and forwarding. It takes 30 seconds for the switch to complete that sequence and begin forwarding packets to and from that port. During those 30 seconds, Novell sends 3 requests for a server, then stops looking. By the time Spanning Tree completes its job, Novell reports that "a file server could not be found".
There are several workarounds available:
1. Disable Spanning Tree on the switch (if Spanning Tree is not needed, i.e. no loops in the network topology).
2. For VLMs, add a "pause" just after calling VLM.EXE in STARTNET.BAT. When the user reboots a PC, have them wait at least 30 seconds before continuing the sequence. This workaround is documented on Novell's Knowledgebase (www.support.novell.com, search for document 2920460).
3. For Client32, add a registry entry in the PC, as documented on Novell's Knowledgebase (search for document 2925582).
--------------------------
Well, i don't use Novell. But the problem seems like i need to wait at least 30 seconds before trying to connect to other computers. (quite strange, since i can ping them).
SuperStack II 3300 seems to support only STP (no RSTP)...
ASKER
OK, it seems that i have resolved problem (at least for now).
After disabling STP on SuperStack II 3300 (where all workstations *and* server were connected) there are no more 'error 53'.
I have tried moving workstations to different switch, but i haven't touched server.
After disabling STP on SuperStack II 3300 (where all workstations *and* server were connected) there are no more 'error 53'.
I have tried moving workstations to different switch, but i haven't touched server.
I've told ya! I'm glad you solved the problem.
Error 53 = "The network path was not found"
It may be trying to map the drive before your network devices are completely loaded.
-Jonathan