I administrate a small Windows 2000

[lilcam]

I administrate a small Windows 2000 network with three W2K servers (one being a domain controller and another being the primary DNS). Beginning two days ago, the DNS server stopped being able to browse the network. The System event log showed the following entry:

Source: NETLOGON Event ID: 5719
No Windows NT or Windows 2000 Domain Controller is available for domain sacred-heart.org. The following error occurred: Not enough storage is available to process this command.

A reboot fixed it for about ten hours. About twelve hours after that the DNS server needed yet another reboot.

I also found these troubling entries in the DNS event log:

Source: DNS Event ID: 140
The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service or reboot the computer. The event data is the error code.

Source: DNS Event ID: 404
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 0.0.0.0. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for
use. Restart the DNS server or reboot the computer.

Source: DNS Event ID: 408
The DNS server could not open socket for address 0.0.0.0.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this
machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parmeters\ ListenAddress value in the services section of the registry and restart.)

If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.


This last one has shown up several times. I can't browse the network, or even do DNS look ups, though the other two servers on the network have no problems seeing it, and the domain controller shows not unusual activity.

 

[jtb]

Please describe the network hardware a bit more... hub vs. switch?, UTP?, Wireless?, server location(s)?, server hardware, user count, internet or other external access, etc...

Thanks

JTB
Senior Infrastructure Specialist
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSE-W2K in progress)

 

[mattjurado]

That's odd its reading the server IP as 0.0.0.0.

What changes have been made recently? Also, look at the DNS server's TCP/IP Properties, its picking up an address of 0.0.0.0, maybe a second network card is having an issue?

Matt

 

[lilcam]

>>Please describe the network hardware a bit more... hub >>vs. switch?, UTP?, Wireless?, server location(s)?, >>server hardware, user count, internet or other external >>access, etc...

What's that gotta do with anything? Server located in the basement.

Anyways ... yea it's weird it's picking up 0.0.0.0.
Under properties of the DNS server it was set on "listen on all IP." I've since changed it to Listen on: ONLY the following." I have 10.1.1.7 listed which is the PDC/DNS Server

 

[lilcam]

Forgot : No changes made recently, but we are running low on space on the C drive. We have about 250MB.

 

[mattjurado]

That's an odd symptom (the 0.0.0.0 address). Usually low disk space will cause other problems, but you should know nt/2k doesn't play well when it starts to dip below 300-400mb.

Matt

 

[lilcam]

Since I made the change to have it listen for request only on this particular IP, I will need to reboot it later today. maybe it's picking up 0.0.0.0 since it was on listen to all available IP beforehand.

 

[KDluhy]

Are your drives partitioned? You should clear as many log files as possible to clear enough hd space for the page file to adjust. If you have more than one drive change the location of the page file to the other drive - increases performance and saves space on your root drive. Since you're a Bissnet school, the IBM servers should have the second HD installed.

 

[wbg34]

Could you post an ipconfig /all from the dns server.

Also are you running SMS on this server?

 

[lilcam]

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : school-house
Primary DNS Suffix . . . . . . . : sacred-heart.org
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sacred-heart.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-9A-E5-63
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.1.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.1.2
DNS Servers . . . . . . . . . . . : 10.1.1.7

 

[lilcam]

Not running SMS

 

[lewa8978]

You may want to check out:

Q279678 on Technet.

Jennifer

 

[bbyes]

Do you mean that the Domain Controller is running Active Directory, and DNS running on a separate machine? If so, you must install DNS on the same server that has AD running on it, and it should point to itself as the primary DNS server. You can make the other server a secondary.
Oh, and the disk space is an issue you don't want to overlook. Win2k is pretty greedy...

 

[shawnpd41]

BByes I disagree it is not required to have DNS and DC on same machine...nor does your DNS have to be Microsoft's...I am running a FreeBSD server strictly for DNS using Bind and Active Directory works very well...of course things would have worked better for longer if I would have had used a better password on my admin account and not gotten hacked but I digress!

 

[lilcam]

I goofed up the thread. AD and DNS are running on the same machine.

Anyways ... I think I fixed it. I had the DNS server listen on all IP, instead of itself. no error msgs in the event viewer. Yea, I will have to increase the size of drive C. My stupid co-worker likes to partitions his C drive really small and make everything else huge.