We are running a 7 computer network with Windows 2000. We have a server running Windows 2000 Server. All of our computers are connected by a hub to the server. Our internet cable service is run through a Linksys router and into the server. We have recently lost connection to the internet and have not been able to send emails, but we have been able to receive emails. The server is still able to connect online and send and receive emails. We were able to use a proxy server as our LAN in order to access the internet. We had to change our SMTP email address to the IP address in order to send emails. This is a temporary fix and we would like to fix the real problem. When we run the cmd prompt and type tracert computing.net, the message is 'Unable to resolve target system name computing.net' Each workstation can successfully ping the server and vice versa. I know this is a DNS problem, but I don't know how to fix it. I ran nslookup from a client and this was the output: *** Can't find server name for address 192.168.0.1: Non-existent domain *** Default servers are not available Default Server: UnKnown Address: 192.168.0.1 This is the nslookup from the server: *** Can't find server name for address 192.168.0.1: Non-existent domain Default Server: ns1.dl.cox.net Address: 68.1.208.30 DHCP is also enabled. Any help will be greatly appreciated. Thank you!

Is the server set up to forward DNS queries from its clients, or as a DNS server itself? If not, then the problem is you have no DNS server available to computers on your network.

Thank you for your response. I was not the one who set up the server and I am just learning about DNS and setting it up. How can I tell if the server is a DNS server? I know it is not solely a DNS server and I know that in the DNS snap-in, we have a forward lookup zone that has our domain and our computers in the domain visible. The forward lookup zone shows that our domain is AD Integrated and running.

How to repair your DNS tables http://www.tweaksforgeeks.com/RepairDNS.html

How completely irrelevant. amfan, it's a pretty safe bet that your server is not setup as a DNS server or forwarder. At least if it is, it's not working. You said "We were able to use a proxy server as our LAN in order to access the internet". I'm assuming you are referring to the Windows 2000 server here. How exactly do you have it set up as a proxy? Are you using Internet Connection Sharing? If not, you may need to configure the DNS service as well. The reason you had to change [y]our SMTP email address to the IP address in order to send emails is the same reason nslookup from the client machine fails. The proxy server is working to provide Internet access, but it is not acting as a DNS server or forwarder. As you already discovered, one workaround for this is to use IP addresses instead of hostnames for servers you want to connect to, such as your ISP's SMTP server. You can also do this for DNS servers. If you configure the client machines to use 68.1.208.30 as their DNS server, you will at least have functional name resolution while you're fixing the problem on your proxy server.