tucktech
asked on
Network path not available after sign in
Hello experts,
We are currently in between switching from an old server to another. We have a script that upon login maps a network drive. The network path is located on ServerOld \\ServerOld\Share. When logging in, most users will have an issue mapping this. After waiting for about 3-5 minutes, you are able to map and connect no problem. The ServerNew does not have a share folder that is shared or mapped. The UNC path is also not available upon log in but after the 3-5 minutes, works fine. I was wondering where would be a good place to start to resolve this issue? Thank you!
We are currently in between switching from an old server to another. We have a script that upon login maps a network drive. The network path is located on ServerOld \\ServerOld\Share. When logging in, most users will have an issue mapping this. After waiting for about 3-5 minutes, you are able to map and connect no problem. The ServerNew does not have a share folder that is shared or mapped. The UNC path is also not available upon log in but after the 3-5 minutes, works fine. I was wondering where would be a good place to start to resolve this issue? Thank you!
Hayes Jupe
whats the results when you ping the server from the command line? and tracert ? is there a delay? is the network path taken the expected path ?
ASKER
Ping and tracert both report as normal. No delay and directly to server
ok, thats a good start.
other things i would try
- try to manually map the drive - is it immediate when done manually ?
- check event logs on both client and server, particularly the security log
- firewall log on the server.... unlikely, but will only take a second to check
other things i would try
- try to manually map the drive - is it immediate when done manually ?
- check event logs on both client and server, particularly the security log
- firewall log on the server.... unlikely, but will only take a second to check
ASKER
I will note that this started when we first created a new share drive on the new server. We eventually deleted the share from the new server and left it on the old server.
ASKER
I can not map the drive manually unless I wait for a few minutes. Then it works correctly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also after it works, I can log in and out it tends to work fine. Just seems that if the system is sitting (overnight typically and logged out) then it occurs the next morning.
yer - that doesnt surprise me... once it sorts out whatever is being delayed, its ok... but once the drive loses its persistent connection, it has to re-auth..... that still make me think its auth related.
what are the client and server OS's ?
what are the client and server OS's ?
ASKER
Client Windows 10
Server Windows Serv 2016
Server Windows Serv 2016
ASKER
I tried changing the mapping to use the IP versus the hostname. Worked fine this morning but a user restarted twice today and both times it needed to be manually added again.
ASKER
Update:
I added a pause at the end of the script to see what it says when it fails.
System error 64 has occurred.
The specified network name is no longer available.
Mapping through explorer gave this similar error:
The mapped network drive could not be created because the following error has occurred:
The specified network name is no longer available.
----------
I did a ping and tracert right after while it still would not connect.
Ping results:
Packets: sent=4 received =4 Lost =0
Approximate round trip times in milli-seconds:
Minimum = 0ms, maximum = 0ms, average 0=ms
Tracert results:
Tracing route to server (ip)
1 1ms <1ms <1ms server.domain.ad
Tracecomplete
After the ping and tracert it mapped fine through explorer.
I added a pause at the end of the script to see what it says when it fails.
System error 64 has occurred.
The specified network name is no longer available.
Mapping through explorer gave this similar error:
The mapped network drive could not be created because the following error has occurred:
The specified network name is no longer available.
----------
I did a ping and tracert right after while it still would not connect.
Ping results:
Packets: sent=4 received =4 Lost =0
Approximate round trip times in milli-seconds:
Minimum = 0ms, maximum = 0ms, average 0=ms
Tracert results:
Tracing route to server (ip)
1 1ms <1ms <1ms server.domain.ad
Tracecomplete
After the ping and tracert it mapped fine through explorer.