General discussion

Locked

Disconnected Network Drives on XP Pro

By jimmy ·
I am in the process of upgrading a number of workstations from Windows 98 SE to Windows XP. These are less than 1 year old computers that were purchased with XP Pro, but we wiped them and loaded 98 SE to keep everything standardized. Now we are going back and upgrading XP back onto them. The problem I am having is that most of these machines are listing the network drives that are mapped by the login script, as disconnected drives. When you click on them they show the drive contents, but some of our older software will not allow us to access information on a drive that is registering as "Disconnected Network Drive." If I manually disconnect the drive, and manually remap it, then that one drive is fine, until the next reboot.

We have a Windows 2000 Server, SP4, running AD as our domain controller. We are also using DHCP and login scripts.

Any Ideas?

This conversation is currently closed to new comments.

28 total posts (Page 1 of 3)   01 | 02 | 03   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by LMon In reply to Disconnected Network Driv ...

Try this link hopefully it will help you!


http://support.microsoft.com/default.aspx?scid=kb;en-us;283492&Product=winxp

Collapse -

by jimmy In reply to

I had already seen that article, but I am not connecting to a Windows 95/98 machine, but to a 2000 AD Domain Controller.

Collapse -

by sgt_shultz In reply to Disconnected Network Driv ...

Share-level mapped network drives are not connected after you restart your computer
View products that this article applies to.
This article was previously published under Q283492
SYMPTOMS
When you restart your computer that is running Microsoft Windows XP Professional, some of the earlier mapped network drives may be disconnected. A red "X" appears for the network drives that are disconnected.

This behavior may occur if all the following conditions are true:
You have a computer that is running Microsoft Windows 95 or Microsoft Windows 98 as a network file server in Share-level access control in a peer-to-peer network. By using share-level access control, you can supply a password for each shared resource.
You have multiple shared folders on the computer that is running Windows 95 or Windows 98, and each shared folder has a different password.
From the computer running Windows XP Professional, you connect to more than one password-protected folder that is shared on the Windows 95-based or Windows 98-based computer.
You select the Remember my password check box for each folder that is shared on the Windows 95-based or Windows 98-based computer.
CAUSE
This behavior occurs because when you connect to a Windows 95-based or Windows 98-based computer that has multiple password-protected shares, Stored User Names and Passwords (Credential Manager) only remembers the password for the last shared folder where you connected.

Collapse -

by sgt_shultz In reply to

WORKAROUND
To work around this behavior, manually reconnect the network drives that are disconnected. To do so, follow these steps:
Right-click Start, and then click Explore.
In the left pane, click My Computer.
In the right pane, double-click the network drive icon with the red "X" displayed on it.
In the Connect to \\computer name\shared folder name dialog box select the user name from the User name list.
In the Password field type the password, and then click OK.
STATUS
This behavior is by design.
MORE INFORMATION
Stored User Names and Passwords is a feature of Microsoft Windows XP that stores user names and passwords for servers. With this feature users can connect to servers with user names and passwords that are different from those that are used to log on. The user can store these user names and passwords for later reuse.

Note Microsoft Windows XP Home Edition lacks the Stored User Names and Passwords feature for network share connections. Windows XP Home Edition stores only Remote Access Services/Virtual Private Networking and Microsoft .NET Passport credentials.
REFERENCES
For additional information about Stored User Names and Passwords, click the following article numbers to view the articles in the Microsoft Knowledge Base:
306992 HOW TO: Manage stored user names and passwords on a computer in a domain in Windows XP

306541 HOW TO: Manage stored user names and passwords on a computer that is not in a domain in Windows XP

281660 Behavior of stored user names and passwords

Collapse -

by jimmy In reply to

I am trying to find the FIX for the problem, not a workaround. I stated that I could manually disconnect and reconnect get by the problem. However, we have about 8 mapped drives, and manually remapping those on each boot is not practical. My setup is a Windows XP Pro SP1a workstation (multiple) connecting to a Windows 2000 SP4 Server running ISA Server. There are no XP Home computers, and no drives mapped to any WIndows 9x machines.

Collapse -

by CG IT In reply to Disconnected Network Driv ...

tricky problem.

I'll assume that your logon script specifies that when workstations log to map a particular share located on some computer on the network as a network drive. When workstations log on and the script runs, the share can't be found. Further, you mention that once logged on workstations can then map the drive, and that you "upgraded" W98 machines to XP, I would also look at DHCP. Since DHCP provides workstations with information like name servers, DNS servers, WINS server and DHCP updates AD/DNS with client info you might want to age all DHCP records that would contain reference to W98 machines, release/renew workstations and see if that clears up the problem.

Collapse -

by CG IT In reply to

man that reads badly. Look at your script. the script might be the problem. Look at DHCP. Since in a AD environment DHCP can update AD/DNS with client info BUT with a long TTL might not have updated records with new client info when you upgraded to XP you might have to age all records to get rid of any old client references to W98 machines. Depends on how you have DHCP configured.

Collapse -

by CG IT In reply to

you might no think DHCP applies to mapped drives but in a AD environment, DHCP provides clients with info about what services are available on the network and DHCP also updates AD and DNS with client info. e.g machine accounts and since machine accounts name to IP address mapping are held in DNS without correct information or up to date information, the name to IP address mapping isn't updated. That is the DHCP TTL. It works both ways. you might want to age all DHCP records so that the updates for new XP machines [even though its an upgrade and not a new install] get posted. you might want to flush DNS cache records just as an added measure to ensure current records.

Collapse -

by jimmy In reply to

I will check the TTL. All of the shares are on the SERVER, which is the domain controller, and is up. The drive mappings completely successfully in the login script, but when looked at through explorer, they register as "Disconnected Network Drive (F:)" or whatever drive letter should be assigned. The clients only receive 1 DNS address, which is the address of the AD Domain Controller (and only Server on the network). WINS is not active, so only DNS is passed. When one of these "Disconnected" drives is selected in explorer, it shows the contents and seems to be fine. The biggest problem is when a few programs attempt to access information on one of these, and immediately fail because it is registered as disconnected. PEACHTREE is one that will only allow access to drives that are in a completely operational state, with all lights green, so to speak.

I have flushed DNS on the server, and all of the workstations in question, and still the same results on reboot.

Thanks for the input. I am on my way to check TTL right now.

Collapse -

by LMon In reply to Disconnected Network Driv ...

Try this if not try this site it may help you out.

net use /persistent:yes is default settings for NT and win2000/XP. This is why when you have mapped some network drives and check the reconnect at logon, or your network uses logon script to map network drives, the mapped network drives may show red Xs after rebooting. If you enable echo and pause the logon script or if using net use to map the same drive manually, you may get "System error 85 has occurred. The local device name is already in use." One thing you may want to try to avoid the red X is using net use /persistent:no, for example, net use i: \\servername\folder /persistent:no.


http://www.chicagotech.net/mapping.htm

Back to Windows Forum
28 total posts (Page 1 of 3)   01 | 02 | 03   Next

Related Discussions

Related Forums