our website is not working in the local network

[catchross]

hello all

i have a strange problem, my organization website is working to the outer world but it is not woking inside the network. can anybody help please

[Georg Pauwen]

Hello,

are you using a proxy server ? If so, try and exclude the website from your proxy server With Internet Explorer, you find that option under:

Tools --> Internet Options --> Connections --> LAN Settings --> Advanced

Here, type the URL of your website.

You have to restart Internet Explorer for these changes to take effect.

HTH,

Georg

[slade]

A number of things could be causing this problem. You could also be running in to NAT issues. If you have a service network addressed differently than your LAN (both could be internet nets) and your web server is on this service net you might need to do a little NAT tuning depending on your firewall.

For example, your LAN is 10.0.1/24 and your service net is 10.0.2/24. Your web server translates from 10.0.2.something out to a public IP. When your LAN stations attempt to contact the host, some global NAT setting could break the connection. The details may or may not be that important to you, but what you would want to be sure of is that when your internal machines contact the public IP of your internal web server, the NAT translates the packet so that it is directed to the INTERNAL ip instead. Eg.

10.0.1/24 going to public.ip.of.webserver translate to destination internal.ip.of.webserver.

[Colleen050]

I had the same problem.

Make sure the DNS settings are not both set to internal IP addresses in your TCP/IP properties. You will need an external DNS IP to access beyond your own gateway.

[cro9uk]

i had a similar problem with our win2k network. We had our website hosted externally and could not see it from the internal network. This is how i sorted it:

the internal clients were looking for www.mydomain.com, the internal dns servers saw mydomain.com and looked for a server on the network called www (which the fqdn would be www.mydomain.com) as they thought the server was on our network they did not do a recursive query!

i did a ping www.mydomain.com from the outside, recorded the hosting webservers ip address, and simply created an entry in our internal dns records for a new host called www and gave it the ip address of the hosting webserver.

Bingo! problem solved (for me anyway).