• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 332
  • Last Modified:

Drive Mappings not appearing

Windows server 2008R2, has been working fine.  Experienced power outage and for a reason not know, the backup power supply did not work properly.  Had to force server to power down.  Once restarted, several computers logged in properly and all drive mappings, using the drive mapping feature new to Windows 2008 with tne addon loaded for WinXP.  However, on serveral computers, you could log in but the drive mappings did not appears.  If we disconnected from domain, deleted computer and DHCP lease, then reattached to domain, then logged on and drive mappings appears.  However, on some computers, this still would not work.

Any suggestions on what is causing the problem and how to resolve.
2 Solutions
MichaelSystems EngineerCommented:
There may be a setting in the XP computers where it's keeping some old information. Try going to Start, Run, cmd, ipconfig /flushdns
are the drives being mapped using a login script or were they manually mapped on each computer? either way, do the following

net use * /del

and answer yes if it asks you if you want to continue. Then re-map the drives.

if you see a red cross on the drives but when you click on them, you are able to access the drive, then it is xp not refreshing the network connection status. in this case just clicking into these drives, should get them connected again.

Sometimes in XP, I've seen drives being mapped, but not showing up in explorer.
Have you tried accessing the drives from the command prompt on machines where you cannot see them?

For example, if you mapped "s:", but cant see it. Open cmd.
Type s:
See if dos see's the drive. If it does, use net use s: /delete to disconnect.
Repeat for all drives.
cwsoft05Author Commented:
What was causing the problem is the ISP, when they setup the router, also configured it to provide DHCP services.  When the power went down and the server was not back initially, the workstations came back up and go IP addresses from the router, not from the server.  Thus, they could not properly find the server domain and although some logged in, they did not get drive mappings and others came up with credential problems because of the IP address changes.

This should now correct the problem.

cwsoft05Author Commented:
The comment addresses the entire issue
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now