Discussion Locked

Event ID 5504 and 5000

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am getting a repeated error 5504 on my NT 4.0 Server. With this error are several different IP addresses throughout the event log. The server is a DNS as well as a WINS server. At this time serveral clients are not able to find a domain server to connect to (the server these services are running on). My question is this... what causes this error, and what can I do to fix this error. The error 5000 relates to the excessive amounts of time that this error is being reported. Thank you to anyone who can assist me with this.

5 replies

by stillatit

The error definition is:

5504 (Warning) DNS_EVENT_INVALID_PACKET_DOMAIN_NAME
DNS Server encountered invalid domain name in packet from %1. Packet is rejected.

What is happening is that some remote client is sending your DNS server a request for a name which includes invalid characters. The Microsoft DNS will accept these names, and use WINS to look them up (since it cannot forward them to another DNS since they are invalid).

You need to look at your systems and make sure that their names are valid names according to DNS. The official rules, per RFC 952, are:
---
A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.).

Notethat periods are only allowed when they serve to delimit components of "domain style names." (See RFC-921, "Domain Name System Implementation Schedule," for background.)

No blank or space characters are permitted as part of a name. No distinctionis made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign or period.
---

If you have workstations with names which are not valid by these rules, change the names.

Good luck.

by csorpha

With relation to the computer names, they are valid. My naming scheme is that of the users first six letters of their last name and the first letter of their first name. The IP addresses that are called out in the event are not included in my DHCPscope however.

by james a bailey

Just some advice, if you do already ignore it. A good source for finding out what causes these errors is:

www.microsoft.com

In the search box, type in the event number, and it will bring back possible matches. usually the first page will have a link to the event id. This will take you to an explination of the problem, why it happens, and possible solutions.

by csorpha

Tried that first. Unfortunately Microsoft's site didn't provide anything useful with several different search attempts.

by frobo

Hi,

if you have w2k Pro clients so they are the Problem. The w2kPro client uses DDNS and tries to record his name in DNS, but NT 4.0 doesn?t supports that so the paket is rejected. This is normal and you can disable this feature on the network tab of the client config.

Hope it helps

Frobo

This discussion is closed to new replies.