Nslookup works, yet Web browsing fails...

[Guest]

I'm configuring a new AD domain. The new Domain Controller DC1 has 2
NICS, 192.168.0.240 & 192.9.200.118. The existing NT4 domain is using
192.9.200.x. I'm intending to migrate all the IPs over to 192.168.0.x
at the same time as the AD upgrade, and want DC1 to sit on both
networks until it's all done.

I appear to have DNS configured correctly, with DC1 as standard primary
and a second DC, DC2 as standard secondary for the new AD domain.
Dynamic updates work ok, replication between the 2 is ok. I have DC1
set to forward non-authoritative DNS requests out to the existing
default gateway on the 192.9.200.x network. DC1 can do name resolution
both for it's own AD domain, and for external (internet) names. The
192.9.200.x network is able to access the internet etc. no problems.

Problem: I can run NSLOOKUP and resolve names & IPs from the new AD
domain. But - web browsing doesn't work, both on the 2 domain
controllers, and on any client introduced to the 192.168.0.x network.
WTF? It's as if http is disabled on DC1.
Anybody know what I'm missing?
Any help would be greatly appreciated.

 

[Steven L Umbach]

Make sure that the computers that can not access the internet have access to
a default gateway that can access the internet. Apparently they can resolve
internet names via the AD dns but may not actually be able to access the
internet. From one of those computers try the tracert command to something
like yahoo.com to see if they have internet access. --- Steve