Website Issue

[adfreek]

Friend of mine has a Windows 2000 Server running IIS and a website which is accessible via the internet (

http://www.companyname.com)

but will not resolve for internal employees. His is the set up:

The W2K Server is dual homed with a public NIC and private NIC. This server hosts the website. This server is also a DNS server (the thing does everything unfortunately). The public NIC is 67.93.xxx.xxx and the private is 192.168.1.x. In the DNS server, there is a zone for the comanyname.com with a

http://WWW cname

record with the public address. This is an AD shop and the AD domain name is companyname.local. Why would internal users being able to browse

http://www.yahoo.com

and not

http://www.companyname.com

? Their DNS settings point to the private NIC as the primary DNS Server?

Help

 

[GlenJohnson]

Can a user try a tracert to the

http://www.companyname.com

and see where the problem starts? Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

 

[spikestik]

I am having the same problem as I posted a similar question earlier in the day. What I have found is that if you go to the server and type in the loopback address... 127.0.0.1 ... your site will resolve locally on the server.

When I ping our company domain name we get a good response from the public IP. When we tracert we also get a good trace with the public IP.

Why would you be running DNS internally if the users are pointing to a remote DNS server? You may want to use internal and external.

So we are not sure what the heck is going on.

It sound like you have a small company, if I may suggest;
remove the public IP card that you have, and use a port forwarding scenerio. Having public and private NIC's serve no real purpose. If you are looking and bandwith issues...goto the Intel Proset Cards and you can D/L the free teaming software for them and team them so that you can auto manage the bandwith.