nancywva
asked on
Network Drives Are Inaccessible
Network drives are inaccessible on only one workstation on the network. The drives, the shared files, were available as usual until Friday morning.
Workstation is running Windows 7 Professional. Server is Windows Small Business Server 2003, SP3.
The problem computer and user have both been working on the network for over a year. Suddenly the networked drives show up as not available.
Removed the computer from the server. Re-connected the computer to the server, using a different computer name. The workstation can ping the server. The server can ping the workstation. Tried re-mapping the network drives, and that does not work. The message indicates that the server is inaccessible, although the server can be reached by entering its IP address in a browser. The security software was disabled temporarily on both the workstation and the server to see if it was causing a problem.
The computer definition on the server for the problem workstation looks fine, as does the user definition. All other users can see the networked drives with no problem.
Does the user have to be removed and re-defined? Does this mean removing and re-connecting the computer again? Is there a way to fix the problem without going through this process?
Workstation is running Windows 7 Professional. Server is Windows Small Business Server 2003, SP3.
The problem computer and user have both been working on the network for over a year. Suddenly the networked drives show up as not available.
Removed the computer from the server. Re-connected the computer to the server, using a different computer name. The workstation can ping the server. The server can ping the workstation. Tried re-mapping the network drives, and that does not work. The message indicates that the server is inaccessible, although the server can be reached by entering its IP address in a browser. The security software was disabled temporarily on both the workstation and the server to see if it was causing a problem.
The computer definition on the server for the problem workstation looks fine, as does the user definition. All other users can see the networked drives with no problem.
Does the user have to be removed and re-defined? Does this mean removing and re-connecting the computer again? Is there a way to fix the problem without going through this process?
This sounds like a DNS issue. Can you ping the server by hostname? Try setting the workstations DNS to the IP of the server and try adding the share. You can also add the mapped drive with IP such as \\192.168.1.10\shared folder. If its not a DNS issue, I would do a quick virus scan on the workstations.
I have seen similiar situations happen when one server is the only dns. Try issuing the following command on the workstation ipconfig /flushdns and see if it fixes the workstation after a server reboot.
ASKER
To TheBadKarma: the workstation's DNS is already set to the IP of the server. Mapping the drive using the IP address did not work either. I will try to ping the server by hostname and let you know.
To wbluna: I have issued the flushdns command and am re-booting the server now. Stay tuned for results.
Thanks to both of you for your suggestions.
To wbluna: I have issued the flushdns command and am re-booting the server now. Stay tuned for results.
Thanks to both of you for your suggestions.
Make sure you flushdns AFTER server reboot!
ASKER
To TheBadKarma: Theworkstation can ping the server by IP address and also by host name.
To wbluna: After issuing the flushdns command and re-booting both the server and the workstation, the problem continues to exist.
To wbluna: After issuing the flushdns command and re-booting both the server and the workstation, the problem continues to exist.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You hit the nail on the head mikeewalton. The credentials were old and inaccurate. Once they were deleted, the problem was solved.