[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 296
  • Last Modified:

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?
0
nancywva
Asked:
nancywva
1 Solution
 
TheBadKarmaCommented:
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.
0
 
wblunaCommented:
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.
0
 
nancywvaAuthor Commented:
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.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
wblunaCommented:
Make sure you flushdns AFTER server reboot!
0
 
nancywvaAuthor Commented:
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.
0
 
mikeewaltonCommented:
Make sure the network you're on is listed as a "Domain Network" on the Win 7 machine. Turn firewall off for "Domain Networks", go to Credential Manager on the 7 machine and make sure there are no remembered credentials for any domain objects.
0
 
nancywvaAuthor Commented:
You hit the nail on the head mikeewalton.  The credentials were old and inaccurate.  Once they were deleted, the problem was solved.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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