Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

All my servers are in the same domain on the same network. ServerA cannot access ServerB through UNC path. However DNS resolves correctly for ServerB from ServerA. For example "ping ServerB" works as expected.

ServerB can reach ServerA through UNC path without any problem. Likewise all other servers and clients can reach ServerB through UNC path without any problem. The software firewall on ServerB is not turned on and there are no hardware firewalls getting in the way.

This makes no sense and I don't know how to troubleshoot it. Nothing shows up in the event logs of ServerA and ServerB has one event (repeatedly): Event ID: 3019, Source: MrxSmb.

ServerA is Server 2008 R2. ServerB is Server 2003 R2. I have other 2008 R2 servers that connect without any problem.

share|improve this question
does \\ipaddressofserverb\sharename work? – tony roth Aug 19 '10 at 4:26
Sorry for having neglected this post. The answer is yes. The IP address works. – idon'twearsuits Dec 15 '11 at 23:45
Additionnally, can you access the share through \\\sharename ? – T. Fabre Jan 4 '13 at 14:12
@T.Fabre I have not experienced this problem a long time so I am going to delete the question. Hopefully you get this message so you know why the question is gone. -- Apparently I can't delete the question because of the answers. I'll try something else. – idon'twearsuits Jan 4 '13 at 18:12

If you can't reach a computer's hostname / computer name, but you can ping its IP address, you have DNS problems. Most likely you have duplicate DNS entries for the unreachable computer, and the short-term fix is to just delete the outdated entry. Tweaking the expiration settings is the long-term fix, but it takes some reading to get it right (mostly because the terminology is pretty arcane).

share|improve this answer
Thanks for your response. A few points: 1. DNS does work. I can ping the hostname and the IP address will be returned. 2. There is only one A record and one PTR record for ServerB. 3. All other computers in the domain are able to resolve/access ServerB. If it were a DNS issue I believe this would affect the whole network but this is not the case. To clarify my process, I'm using DNS Manager on my DC to check the records. – idon'twearsuits Aug 18 '10 at 18:21

Are you trying to access a share in your UNC path, or just the server? What about permissions on your share (the share you are attempting to access on ServerB)?

share|improve this answer
Thanks for your response. 1. Anything that uses the UNC path fails. But yes, specifically, I'm trying to access a share. 2. The permissions are OK. The error is "Path does not exist" vs "Access Denied". But besides that a user can access the share without a problem through the IP address. – idon'twearsuits Aug 18 '10 at 20:40

Can ServerA access any other SMB resources via UNC? Is NetBIOS over TCP/IP enabled and verified working correctly on ServerA?

share|improve this answer
Yes, ServerA can access other resources via UNC. I have not messed with NetBIOS so it would be in its default state on Server 2008 R2. – idon'twearsuits Aug 19 '10 at 22:36
Can ServerA access ServerB shares via UNC with FQN versus NetBIOS? – user48838 Aug 20 '10 at 13:45

Try to check if there is some drive mapping already.

To do that, open the explorer windows, then choose tools -> disconnect network drive. Ins the list of connections check if there is already a connection to the server / drive that you're trying to do.

Then choose it and press ok to disable it.

share|improve this answer
up vote 0 down vote accepted

This issue cannot be solved any longer because the servers do not exist anymore.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.