FrankBabz
asked on
Vista workstations not automatically reconnecting to server share on startup
I have a small network with 1 server (WS2003) and 5 workstations (Vista Ultimate) and a Linksys BEFSR81 Router (DHCP for workstations). The Router has passed the Vista diagnostics test as meeting all requirements. My problem seems to have started after upgrading all workstations to Vista.
The Problem: Occasionally and rather frequently when a workstation starts up in the morning, the Shared folder on the Server is not automatically reconnected. Manually trying to reconnect will have Vista diagnose the need to establish a new IP with the Modem. Frequently, a user must detach the share and reconnect manually. Doing that frequently is problematic, but worse than that it requires an administrator password and when I am not available, the user cannot proceed.
It seems to me that whatever the modem thought was the workstation’s IP is no longer valid (perhaps due to a power glitch that caused the modem to reset?). Yet, most always when Vista diagnoses the connection, and tells the Modem to assign a new IP, the connection is re-established. This rarely happened with XP.
I would like to know if there is a software option or setting option that will resolve this. I have considered giving all workstations a Static IP to see if that solves what (I’m guessing) to be a DHCP issue not being automatically attempted and reset by Vista.
Any suggestions would be greatly appreciated….
The Problem: Occasionally and rather frequently when a workstation starts up in the morning, the Shared folder on the Server is not automatically reconnected. Manually trying to reconnect will have Vista diagnose the need to establish a new IP with the Modem. Frequently, a user must detach the share and reconnect manually. Doing that frequently is problematic, but worse than that it requires an administrator password and when I am not available, the user cannot proceed.
It seems to me that whatever the modem thought was the workstation’s IP is no longer valid (perhaps due to a power glitch that caused the modem to reset?). Yet, most always when Vista diagnoses the connection, and tells the Modem to assign a new IP, the connection is re-established. This rarely happened with XP.
I would like to know if there is a software option or setting option that will resolve this. I have considered giving all workstations a Static IP to see if that solves what (I’m guessing) to be a DHCP issue not being automatically attempted and reset by Vista.
Any suggestions would be greatly appreciated….
ASKER
Wow! Thanks for the guidance....
I will be glad to try your suggestion, but you are taking me into a new learning curve territory, so please bear with me as I ask these questions:
1) I presume "logon.bat" will run whenever a User logs on to any workstation. Correct?
2) Please tell me what "net use * /delete /yes" does?
.
3) I presume I must do Step 2 for every user. Correct?
4) Please tell me how this fixes (what I think) is a Vista/Modem IP (out-of-sync) problem. Would it somehow force the modem to issue the workstation a new IP?
I will be glad to try your suggestion, but you are taking me into a new learning curve territory, so please bear with me as I ask these questions:
1) I presume "logon.bat" will run whenever a User logs on to any workstation. Correct?
2) Please tell me what "net use * /delete /yes" does?
.
3) I presume I must do Step 2 for every user. Correct?
4) Please tell me how this fixes (what I think) is a Vista/Modem IP (out-of-sync) problem. Would it somehow force the modem to issue the workstation a new IP?
ASKER
I am trying my best to research this myself, and I am having a problem with "net use /delete /yes"
The /delete cancels all network connectios, and /yes is a mystery. Will /delete also cancel the shared Dymo printer that is USB attached to the server? Was /yes meant to be persistent:yes ?
Thanks for your help with my questions...
The /delete cancels all network connectios, and /yes is a mystery. Will /delete also cancel the shared Dymo printer that is USB attached to the server? Was /yes meant to be persistent:yes ?
Thanks for your help with my questions...
the userlogon.bat will run only on user that you will apply the script on the AD.
the net use * /delete /yes will clean all the maps you have ... you can change the * to drive leter.
basically the script delete the network drive and reconnect every logon
you dont have to do the "delete" command you can make logon script only with net use x: \\file_server_name\shared_
try here for more help about this
http://technet.microsoft.com/en-us/library/cc779490(WS.10).aspx
the net use * /delete /yes will clean all the maps you have ... you can change the * to drive leter.
basically the script delete the network drive and reconnect every logon
you dont have to do the "delete" command you can make logon script only with net use x: \\file_server_name\shared_
try here for more help about this
http://technet.microsoft.com/en-us/library/cc779490(WS.10).aspx
ASKER
My server name is TED
The name of my server share is R (this is a folder on my server D drive)
On my workstation I want R: to point to \\TED\R
My Logo.bat is:
@echo off
net use R: \\TED\R
When I logged on to Workstation there was no R:
(Normall I would see R(\\TED) (R:) or r(\\TED) (R:) after manually mapping the share)
Sorry I need so much help.
The name of my server share is R (this is a folder on my server D drive)
On my workstation I want R: to point to \\TED\R
My Logo.bat is:
@echo off
net use R: \\TED\R
When I logged on to Workstation there was no R:
(Normall I would see R(\\TED) (R:) or r(\\TED) (R:) after manually mapping the share)
Sorry I need so much help.
ASKER
I meant to say Logon.bat
go to start > run >
make \\ted
navigate to the D drive and to the share folder.... copy the path from the address bar and paste in the logon.bat
net use r: \\ted\d\share folder
try to run the in CMD and see if you get any error or seccessful messege.
make \\ted
navigate to the D drive and to the share folder.... copy the path from the address bar and paste in the logon.bat
net use r: \\ted\d\share folder
try to run the in CMD and see if you get any error or seccessful messege.
ASKER
I entered
net use r: \\ted\D\Ster and \\ted\D:\Ster and \\ted\R
For all of 3 above same error 85 The local device name is already in use.
Is this because R is being used on a 2nd work station? I have need to have same user logged on to more than one work station at the same time. Also, in this testing I am logged on to the server, and the workstation(s)
net use r: \\ted\D\Ster and \\ted\D:\Ster and \\ted\R
For all of 3 above same error 85 The local device name is already in use.
Is this because R is being used on a 2nd work station? I have need to have same user logged on to more than one work station at the same time. Also, in this testing I am logged on to the server, and the workstation(s)
start >run> cmd > and net use > press enter
did you get any map list ?
did you get any map list ?
ASKER
I entered:
net use
I got:
New connections will be remembered
Status Local Remote Network
--------------------------
Disconnected R: \\TED\R Microsoft Windows network
The command completed successfully
net use
I got:
New connections will be remembered
Status Local Remote Network
--------------------------
Disconnected R: \\TED\R Microsoft Windows network
The command completed successfully
ok try to run from CMD net use r: /delete /yes
and now net use again if you got nothing on r then try net use r: \\ted\"share dir"
you can also try to use another letter for the map....
and now net use again if you got nothing on r then try net use r: \\ted\"share dir"
you can also try to use another letter for the map....
ASKER
I entered:
>net use r: /delete /yes
R: was deleted successfully
>net use
New connections will be remembered
There are no entries in the list
>net use r: \\TED\R
The command completed successfully
The R: is a drive used by all workstations, and there is a software program closely tied to having this R drive.
As administrator I also have a Z: drive that gives me access to the entire Server "D" drive
>net use r: /delete /yes
R: was deleted successfully
>net use
New connections will be remembered
There are no entries in the list
>net use r: \\TED\R
The command completed successfully
The R: is a drive used by all workstations, and there is a software program closely tied to having this R drive.
As administrator I also have a Z: drive that gives me access to the entire Server "D" drive
>net use r: \\TED\R
The command completed successfully
this is work now ?
The command completed successfully
this is work now ?
ASKER
>net use
New connections will be remembered
Status Local Remote Network
--------------------------
OK R: \\TED\R Microsoft..........
The command completed successfully
I went to workstation and logged on, but I do not see the R: drive
My Logon.bat is:
@echo off
net use R: \\TED\R
New connections will be remembered
Status Local Remote Network
--------------------------
OK R: \\TED\R Microsoft..........
The command completed successfully
I went to workstation and logged on, but I do not see the R: drive
My Logon.bat is:
@echo off
net use R: \\TED\R
try to run the net use R: \\TED\R manuelly on the workstation from cmd
can you see the R ??
can you see the R ??
ASKER
Yes. At the workstation after entering net use R: \\TED\R manually
I immediately saw the R: drive appear in "Computer" folder: R (\\TED) (R:)
I immediately saw the R: drive appear in "Computer" folder: R (\\TED) (R:)
ok now make a new logon.bat on the workstation with the command "net use R: \\TED\R"
put the file in the startup folder and restart the workstation... still get the map ?
put the file in the startup folder and restart the workstation... still get the map ?
ASKER
I copied my Logon.bat file from the Server to the workstation "All Users - Startup" folder.
I just had to see if it was corrupted.
And, as you will see below, it was working just fine, just not making the connection.
At the workstation:
I logged OFF then ON, and Viola! we have R (\\TED) (R:)
To be certain, I did a restart on the workstation and tried again, and we have R (\\TED) (R:)
I removed Logon.bat from the server scripts folder and cleared the User's profile.
To be sure: I powered off the server, and the workstation, and restarted both
Logged in to workstation, and we still have R (\\TED) (R:)
I am very pleased with your follow through, and the assistance you have provided.
AND...I will certainly award you full credit for your help.
Now, I will fix all the office workstations, and hope this cures the Vista/modem IP problem I have been having.
Do you think it will? If not do you think inserting.... net use R: /delete /yes .... is something to try?
I just had to see if it was corrupted.
And, as you will see below, it was working just fine, just not making the connection.
At the workstation:
I logged OFF then ON, and Viola! we have R (\\TED) (R:)
To be certain, I did a restart on the workstation and tried again, and we have R (\\TED) (R:)
I removed Logon.bat from the server scripts folder and cleared the User's profile.
To be sure: I powered off the server, and the workstation, and restarted both
Logged in to workstation, and we still have R (\\TED) (R:)
I am very pleased with your follow through, and the assistance you have provided.
AND...I will certainly award you full credit for your help.
Now, I will fix all the office workstations, and hope this cures the Vista/modem IP problem I have been having.
Do you think it will? If not do you think inserting.... net use R: /delete /yes .... is something to try?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Your support was more than outstanding, and very much appreciated.
In a month or two, I'll update you to advise if the modem/IP issue has been resolved.
Best wishes..... Frank
In a month or two, I'll update you to advise if the modem/IP issue has been resolved.
Best wishes..... Frank
ASKER
What works at home does not work at the office.
Both systems are identical except the office uses a different router the *BEFSR81 by Linksys" (home uses Cisco E3000)
At the office, >net set R: /delete /yes will cause the failure, at home, it does not cause a failure.
When office connection fails the following is true:
1) network diagnostics will offer to reset the IP and this always works.
2) net set R: \\TED\R - returns Network not found
3) ipconfig /reset - returns Network not found
4) ipconfig /renew - returns Network not found
Only option 1 works once there is a failure, and this requires Admin password.
Thanks for your assistance and any thoughts you may have.
Frank
Both systems are identical except the office uses a different router the *BEFSR81 by Linksys" (home uses Cisco E3000)
At the office, >net set R: /delete /yes will cause the failure, at home, it does not cause a failure.
When office connection fails the following is true:
1) network diagnostics will offer to reset the IP and this always works.
2) net set R: \\TED\R - returns Network not found
3) ipconfig /reset - returns Network not found
4) ipconfig /renew - returns Network not found
Only option 1 works once there is a failure, and this requires Admin password.
Thanks for your assistance and any thoughts you may have.
Frank
@echo off
net use * /delete /yes
net use x: \\file_server_name\shared_
Active Directory Users and Computers > Users > Double click user > Profile
Enter "logon.bat" (no quotes) in the "Logon script" box and click OK
Login from workstation as user modified in step 2. Drive x: should appear in My Computer.