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

I have a situation whereby there are 3 sites.

Site a - User site
Site b - User site
Site c - datacentre

Site a can talk to site c fine Site b can not talk to everything in site C

In particular, workstations in site b are struggling to communicate properly with site c. For example - there are servers that we can ping, tracert, even telnet on port 80 (or other app ports) to but cannot for example browse network shares on them. Microsoft Network Monitor shows connections are made during these attempts, but I cannot browse and get the following message:

"\\server\share" is not accessible. You might not have permissions to use this network resource. Contact the admin of this server to find out if you have access permissions. The specific network name is no longer available.

The server is available and I do have access. I can access without issue from Site A.

Where should I start looking?

share|improve this question
Can you give some IP schemes? Firewalls? How are they configured? – Bart De Vos May 25 '12 at 11:11
OK so site a is on a 172.16.5.x range. site b is 172.16.16.x and the servers in site c are on 192.168.245 range. – Kip May 25 '12 at 11:34

My first guess, without further info, is that the connection between B and C is not fully transparent.

Can you RDP to a server in C (either from A or B) ? Then do some ping and tracert tests from C to B and see it that works.

If that doesn't work you most likely have a routing issue from C to B.

If it does work the base connectivity is there in both directions. In that case the culprit is most likely some firewall/filter between B and C that kills some protocols (SMB/CIFS).

As Bart already stated: Without more details it hard to be more specific.

share|improve this answer
Tracert between all sites and destinations works fine. Our comms guys have assured us there are only routers / switches in place and no firewalls in place. Tracert from site C servers (the ones we are struggling to reach) completes to both site a and site c – Kip May 25 '12 at 11:35
Then I'm a bit at a loss. Try using FQDN's in stead of just a servername in connections. If that makes a difference I would guess that thre is some sort of DNS and/or WINS issue on site B. – Tonny May 25 '12 at 11:47
Just tried using FQDN and IP - still no luck. Thanks for the suggestions – Kip May 25 '12 at 12:24

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.