I have a new server running 2003. This new server sits on a different subnet from our dns servers. This server can resolve dns requests for websites, i.e. But it will not resolve requests for internal pings. If I try to ping the DNS server by name, it wont work. If I ping by IP address, it works fine. I have Windows XP machines on this other subnet and they resolve DNS just fine using the same settings. And sine I can resolve External addresses, but not internal, I am confused. I also can not join the domain, because it claims it cant find a domain controller.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Server 2003 and Server 2000
- Thread starter jfc1003
- Start date
- Thread starter
- #3
NSLOOKUP shows the correct dns server, mvs_filesrvr, and the correct IP 192.168.20.3 . And I can ping the IP. The funny thing is if I try to nslookup the DNS server, I get the following:
mvs_filesrvr.mvhospital.local cant find mvs_filesrvr: server failed
So it cant find itself. The DNS server is w2k. The W2k3 server has not been configured at all, just a plain install with static IP address. So is there somehting you have to do to make the W2k server allow responses to the w2k3 for local network requests? No other machine does this, only the w2k3 server.
mvs_filesrvr.mvhospital.local cant find mvs_filesrvr: server failed
So it cant find itself. The DNS server is w2k. The W2k3 server has not been configured at all, just a plain install with static IP address. So is there somehting you have to do to make the W2k server allow responses to the w2k3 for local network requests? No other machine does this, only the w2k3 server.
- Status
Similar threads
- Locked
- Question
- Locked
- Question