Clicky

I have a workstation that will not map the network drives via the dns name. I have a .cmd file that runs when the user logs in and when I run the .cmd file with \\servername\share nothing is mapped on the workstation. If I run a .cmd file with \\ipaddress\share the drive maps fine and the user can access the network share. I added the IPAddress and Servername information to the Host file on the workstation and that seemed to help for a day or so and now it will not work again.

Any suggestions on what might be going on and how to fix this would be great. Thanks in advance.

asked 11/22/2011 04:04

ochness's gravatar image

ochness ♦♦


11 Answers:
This sounds like a DNS issue, or a NetBIOS over TCP/IP issue related to browsing.  Can you ping the server by name?
link

answered

hypercat's gravatar image

hypercat

Yes, the workstation is able to ping the server by it's name. I'm not sure what is going on...any other thoughts?
link

answered 2011-11-22 at 13:37:07

ochness's gravatar image

ochness

Go into the NIC properties on the workstation, edit the TCP/IP properties. On the WINS tab, click the button for "Enable NetBIOS over TCP/IP." Reboot the workstation and then try again.
link

answered 2011-11-22 at 13:56:56

hypercat's gravatar image

hypercat

Also make sure that this button is selected on the server end.
link

answered 2011-11-22 at 14:04:32

hypercat's gravatar image

hypercat

Is the workstation service running?

link

answered 2011-11-22 at 14:05:04

dacasey's gravatar image

dacasey

Look at your services,  check to see if the Computer Browser and Workstation services are both started.

If not there are a variety of reason, you should have a clue in your system or application logs.
link

answered 2011-11-24 at 20:39:18

dacasey's gravatar image

dacasey

when you ping the servername, does it provide the correct IP address?

can you browse to the share manually (start>run>\\servername)?

did you have to add the DNS records to other workstations hosts file too or just this one?
the fact you had to add it means the workstation wasnt resolving DNS correctly in the first place. If its on a domain it could have all sorts of issues if it cant get DNS right.
link

answered 2011-11-24 at 20:42:07

totallytonto's gravatar image

totallytonto

Thank you to everyone for your responces.

The Computer Browser and Workstation service are both running. I am able to ping the server via the server name and it returns the correct IP address. This is the only workstation that is having this issue, all other workstations resolve mapped drive via \\servername\share just fine.

Any other suggestions would be great. This is becoming a real annoyance to the user.

Thanks.
link

answered 2011-11-28 at 07:08:20

ochness's gravatar image

ochness

can you map the drive from a command prompt manually and see what error is shown?
link

answered 2011-11-28 at 12:19:34

totallytonto's gravatar image

totallytonto

I have found the problem. It appears that somehow the OffLine files sync had gotten turned on and was not making a connection to the server and thus blocking all of the mapped drives from connecting. I disabled the OffLine files and am now able to map to all the network shares.

Not sure why the OffLine file thing caused an issue, but turning that off seems to have fixed the problem.

Thanks for the help and suggestions.
link

answered 2011-11-28 at 12:23:43

ochness's gravatar image

ochness

I found the reason the drives were being blocked from being mapped. I would like this question closed.

Thanks.

link

answered 2011-11-28 at 13:34:30

ochness's gravatar image

ochness

Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×1
×1
×48

Asked: 11/22/2011 04:04

Seen: 304 times

Last updated: 12/17/2011 05:18