Lan and Wab AD Servers - everyone can ping website except for client pc's inside office lan

[tym...@ivie-ent.com]

Hi All,

For several years we had been running a Remote Dedicated Win2000 Server
for our website 'www.ivie-ent.com' it also handled the companies smtp
and pop3. Eveyone in the main office could access the web including our
website with no problems.

The other day our remote web server named 'ivie-ent.com' was
compromised to host someones warez (it was NOT setup as a domain
controller, atleast not that i remeber) so i changed server providers
and I got a Remote Dedicated Win2003 SBS, it is setup as
'ivie-ent.com'. I setup the AD 'ivie-ent.com' as required and it is
setup as the forest root, IIS, DNS, etc, The problem is that i can
access the internet website ok, normal visitors are also getting to the
site just fine. However the guys in our office on our Lan can access
anything on the web except for our own 'ivie-ent.com' website, they
cannot even ping the new web server which is 72.9.253.122. For them it
times out at the last hop before the web server.

Our Main Office's Lan Server is a Win2000 SB edition and it has always
been running as the local domain controller with a FQDN of
'xxxxx.ivie-ent.local' (xxxxx is actually something else, but i left it
out). The server has one nic which goes to a switch/hub that is shared
by other lan client pc's. The switch cable then runs to the Linksys
router which is setup to act as the internet gateway. All client PC's
are WinXP Pro and are using Static IP's for the Lan.

To remedy this we have tried adding (A) Record entry's for 'www' hosts
into the Lan Server's DNS Forward zone to point to web servers ip. This
didn't help anything.

There are only a couple of other things i can think of:
1. Do I need to add the web servers ip into the gateway and dns on the
Lan servers single nic card settings?
2. Do I need to add the web servers ip into the gateway and dns on the
Linksys router settings?
3. Do I need to add the web servers ip into the root hints?

Any other suggestions.

[Kevin D. Goodknecht Sr. [MVP]]

Is server that hosts this website behind the same NAT device (router) as the
LAN users?
If it is, then you need to access the website by its private IP address not
the public IP address. To do that for only the name www.ivie-ent.com you
will need a forward lookup zone using www.ivie-ent.com as its name, then add
a new host, leave the name field blank and give it the private IP address of
the web server.
After you create this you will need to run ipconfig /flushdns before
accessing the site to clear the cached record on the client.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

[Todd J Heron]

You meant point CNAME to the www record. Pointing "www" to the IP address
of a webserver is a host (A) record.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

[tym...@ivie-ent.com]

Ok, I fixed it. It was incorrect subnet mask setting on my alternate
ip's in network connections. BTW the ivie-ent.com site is in an
external datacenter.