Server 2000 can't talk outside local net

Normally a 2000 server is configured with the DNS service, then all workstations/svrs use the 2000 for DNS as its service is configure with forwarders to handle 'non local' resolutions. If your DNS on the 2000 server is properly configured try a tracert www.yahoo.com from a command prompt to see if it resolves okay.

this sounds like that one where dns server is not pointing to itself for dns...i think if you look up your symptoms at support.microsoft.com mskb you will find the instructions...

I would check all the basics.

Is this an AD controller by the way? If so is DNS on the server?

Check that DNS is correct if it is setup on the server. (even
though the ping is an ip address and needs no resolution). Flush
the cache and check for any host files or ip filters. Try a tracert
and see where you sre going and stopping. Disable any software
firewall and examine any firewall logs too.

Good Luck,

razz

Thanks for all the quick responses! Yes this is the Domain Controller (only one server in this network). I believe DNS is setup on this server. Workstations get their DHCP info from the Netscreen firewall/gateway. First DNS address points to the server, second to the firewall, third to ISP public. If I set the server to obtain an address automatically (but leave DNS static on the server), then the server can access the Internet just fine. When I change back to static IP, I'm back to local subnet only. Would WINS have anything to do with this? Still, I'll check DNS setup on the server and make sure it's functioning ok. Occassionally when adding new workstations, they cannot find a domain controller.

Thanks again.
Jon

A couple notes to add here:

The DHCP should be on the server not the firewall. And a server SHOULD NEVER BE DYNAMIC except for your testing.

What is your internal domain name and ext? Are you using a .local or a .com internally? It should NOT be a .com or the like.

How are the DNS address' setup on the server? Did you use the real ip or a 127.0.0.1? The server should be pointing at it's address.

Is DNS setup as a root, is there a "." zone? The the DNS server should have root hints and forwarders. It should not have a "root" zone.

DNS on the server is set incorrect I would bet. If some new stations can't find the SRV records for logon then that is the issue. Well, I should ask, are the workstations XP/2000 or 9x clients? If XP/2000 they look for the Domain Controller in DNS. 9x clients would use WINS. The fact that the server as static looses access but dynamic has access is your clue. Something it is getting from DHCP is different. Try this, Set the server static. You said it will fail. Now, make the primary DNS the isp address and see what happens.

Good Luck,

razz

I think you should check your tcp/ip bindings first, then you make sure that the server is pointing to itself for DNS. If the server could access internet and you are sure you didn't change anything, try uninstalling TCP/IP and reinstall, or remove it from the registry(a safer method) and copy from the registry of a known working machine
P.S. backup your reg first.

THanks for all the help. I think my DNS forwarding may not be functioning. DNS is running on this server. It is not a root server, but is configured for the domain. I right-clicked on the DNS server and selected properties and setup forwarding addresses. I checked the root hints, which looked fine. Just to make sure, I expanded them again from the install CD and copied cache.dns into the DNS folder. In Monitoring tab, a simple DNS test is successful, but a recursive (external) DNS test fails. I now have DHCP setup on this server, but they could not access the Internet until I added the external DNS addresses in the DHCP server configuration. So the workstations are still up and running, but not using the forwarding from the one and only Win2000 server. I've doubled checked the DNS addresses in the forwarding tab and they're correct. Any ideas on how to fix forwarding??

Thanks,
Jon

OK. Problem found. I was examining the log files on the firewall and noticed that the source address translation for NAT for all the workstations was different than the server. The server looked like it was sending from the T1 router, while other clients were sending from the firewall/gateway. With Netscreen tech support, it turns out that I had a Mapped IP address that had an incorrect netmask setting. This policy was disabled, so I didn't think that would affect anything. But, as soon as we changed the netmask to 32, the server source addresses came from the firewall and I had Internet access. :)
Thanks to all for all your help and comments. I think this is a great forum and a great help.

Thanks,
Jon

This question was closed by the author