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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win2k DNS problem? Help!

Status
Not open for further replies.

TwistedAdmin

IS-IT--Management
May 6, 2002
28
US
Hello all.

I've got a Win2k Server running Active Directory. It doesn't get used heavily as it merely hosts a network accounting package with licensing for multiple concurrent connections.
Recently, it's come to my attention that it's ceased transponding DDNS update information. After looking into this, I also found that it could no longer browse web-pages either by name or by IP and that IIS is no longer responding to HTTP requests. However, PING and TRACERT works from the CLI for name and IP addresses of destinations on the Internet but not for other servers/PCs within my own LAN. Also, the server still responds to Terminal Services sessions.
I've checked Event Viewer and spotted this as the most likely relevant entry:

===============================
Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5782
Date: 3/19/2006
Time: 10:47:42 AM
User: N/A
Computer: SERVER2005
Description:
Dynamic registration or deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system.
Data:
0000: 7c 26 00 00 |&..
==========================

I don't know why it's claiming there are no DNS servers... I've got DNS set up on it... and DNS was working fine up until about a month or so ago (when Comcast came in and put in an SMC cable-modem/router... not that I think that has anything to do with it... but thought I'd add that just in case).
Any thoughts or advice on this would be greatly appreciated.

TIA,
TwistedAdmin
 
Check the tcp/ip settings on your network interface card on the DNS server. The DNS setting should point back to it's own IP address or to 127.0.0.1 (loopback address).

Cable-modem/routers tend to also provide DHCP services. This can cause problems if you are running your own DHCP server. You don't need both running DHCP. If the router is providing DHCP, it probably isn't providing the DHCP options to the clients that you would want.

The standard is to hand out DCHP options pointing to your DNS server and no others (i.e. internet). Your DNS server will provide all DNS resolution. For internet, you delete the "." root zone and create a forward to your ISP's DNS server in DNS.

To check settings, goto a client computer and get a DOS prompt and type IPCONFIG /ALL


Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA
 
Just to close this out... the actual cause of all of the problems was that the gigabit switch the server was plugged into... was not plugged into the auto-uplink port of the switch that connected the router to the network. All-in-all, once the wiring was straightened out, everything was back to norm.

[ A+ Certified, Net+ Certified ]

"Old men are always young enough to learn."

~ Aeschylus

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top