Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

At work I can connect to the Team Foundation Server (TFS) from Visual Studio and do all the source control etc. that I need to. However, when working from home and connected to work via VPN I cannot connect to TFS.

I tried pinging the TFS server from home (over VPN) and from work and in both cases it can see the server. I also tried entering IP address instead of the DNS name and the same story: works from the work computer but not the one at home.

Any idea why this is or how it could be resolved?

share|improve this question
Error messages? – womble May 5 '09 at 4:07
up vote 2 down vote accepted

I would look at the route between the two. Are the routing rules different between the two subnets. Are there firewall rules that are only letting traffic through from your dev net but not from your VPN net?

share|improve this answer
I did a tracert between the two and they go through completely different routes to get to TFS. – Guy May 5 '09 at 5:30
I would guess there is a firewall or routing rule that does not allow the traffic run nmap or some other port scan to see what ports you see on the remote host. Then talk to a network admin about the differences you are seeing – trent May 5 '09 at 6:25

We ran into the same issue. It ended up being a setting within IIS and it was set to an old IP address with in Web Management Service. Double check that also.

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.