• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

Windows 2000 Network, Routing to external site of same domain name as internal network

I have three offices, one in London, Paris and Munich. These networks are part of the acompany.com Windows 2000 domain. The London office is connected to a US office over a 256K Frame Relay line.

Our US counterparts, in the same domain, have a website, hosted on a public facing IP address.This is accessible from the outside ok. The address of the website is myweb.acompany.com

The website can be accessed fine from the outside, fine from within the UK office, but not from within the Munich or Paris offices. Munich is connected to London via PPTP tunnel between Watchguard firewalls at each end. Paris currently has a PPTP connection to the UK Watchguard set up from a server in the Paris LAN.

We use an internal DNS server in the UK, which resolves names ok. I have set the German servers to use that DNS server, this is fine and an nslookup reveals the correct IP address for myweb.acompany.com Have done the same in France.The France server gets to the website ok. The German servers do not. No clients in the Paris or Munich offices can get to the website.

I think its either DNS or routing, not sure which, any help is appreciated.

0
gmoore96
Asked:
gmoore96
1 Solution
 
PennGwynCommented:
Your tests indicate that DNS is working, which leaves a routing issue.  Can you try a traceroute (Windows spells it tracert) from a German server to the web server?  How far does it get?  How does this compare to results when done from Paris?  What about to a German server address from the web server?

0
 
AdmiralDaveCommented:
The fact Your office's conntectivity works other than the website i would be veru surprised if it was routing you may also look at your firewall rules to enusre that the ip range in Munich and Paris is Allowed to port 80

My first test would be to ping the server by name from the munich and paris office's if you can ping then Do a tracert and see where it stops and check that firewall.

That should give you a bit to go on :)
0
 
gmoore96Author Commented:
Sorry for the late reply, this was finally sorted out, routes needed adding to the US webserver for return traffic to the Munich and Paris offices. Please close the questions.
0
 
GhostModCommented:
PAQed, with points refunded (250)

GhostMod
Community Support Moderator
0

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

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