DNS Errors with Windows 2003 SBS Domain

I have an account with a single domain and a Windows 2003 Small Business Server that is having DNS problems.  The error I'm getting is "The DNS server encountered a packet addressed to itself on IP address xxx.xxx.xxx.xxx.  The packet will be discarded.  This condition usually indicates a configuration error."
I checked the Forwarders list and it is not forwarding to itself, but although I am familiar with DNS services, it seems somewhat of a "dark art" to me.  It tells me to check the Master lists of secondary zones, Notify lists of primary zones, Delegations of subzones, etc, but I'm not sure what I am checking for.

This site has a single Domain Controller and it is the DNS server, with a single Domain....  I figure it shouldn't be that complicated.  I looked around and did notice that I am showing what appears to be two IP addresses in DNS that are associated with the server.  That I think might be my problem.  The server only has one network card and only has one IP address assigned to that card.  The two addresses are 192.168.1.2 and 192.168.1.108.  The address that is correct is the 192.168.1.2 and I have no idea where the other (.108) came from.

My questions are....  1. Can I delete the instances of the 192.168.1.108 from the DNS without screwing something up.  2.  What would be the best way to go about that.  and 3. Is this a likely cause of my problem?
Thanks...

dwar08Asked:
Who is Participating?
 
BWaringConnect With a Mentor Commented:
If the single server has one network card, and that card only has 192.168.1.2, then yes, remove all those references to 192.168.1.108.... just highlight each one and delete... also confirm that the IP settings for the network card point to the server itself - 192.168.1.2 - as the only DNS server... then in the DNS server setup you can add your ISP's DNS servers as forwarders (but do not include your own IP as a forwarder)....
0
 
Rob WilliamsConnect With a Mentor Commented:
Also, if there is more than one NIC make sure it is disabled and not just disconnected.
In the DNS management console under properties of the server on the interfaces tab make sure DNS is bound ONLY to the 192.168.1.2 address.
I assume this is not a virtual machine and .108 is a virtual NIC?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
dwar08Author Commented:
Thanks for the input...  I have checked and confirmed the following....

The IP settings for the network card point to 192.168.1.2 as the only DNS server and under the server properties in DNS management console, the forwarders point to only the ISP's DNS servers.

There is only one physical network card in the server and it is not a virtual machine.  Under the interfaces tab in the server properties of the DNS management console DNS is bound to only the 192.168.1.2 address...  I have provided screen shots of those items...

What about the two entries under Forward Lookup Zones > _msdcs.fourstarfab.local.  The Alias (CNAME) entries.  Are those duplicates?  Do I need to delete one of those?  If so how do I determine which one to delete?  I am including a screen shot of that entry also...
Thanks...
IPConfig.JPG
Forwarders.JPG
IFaces.JPG
FSFab-FLZ-1.JPG
0
 
BWaringConnect With a Mentor Commented:
Once you have removed the other entries, you can remove and recreate the _msdcs.fourstarfab.local zone very easily... see this article:  http://support.microsoft.com/kb/817470/ under 'Case 2" halfway down...
0
 
dwar08Author Commented:
Thanks for the info guys.... I have to wait for this weekend to get a maintenance window to make the changes.....  Will see what happens.....
0
 
BWaringCommented:
Wondering if you were able to make the changes and if it resolved the issue?
0
 
dwar08Author Commented:
Sorry for the late reply.... I was not able to get a maintenance window until this last weekend due to the business quarter end.  I made the changes and it really has made no difference.  I am still getting the intermittent "packet addressed to itself" errors.  I am also experiencing random machines taking a VERY long time to log into the domain at times and have had to map drives on occasion using the IP address rather than the machine name...  I'm pretty sure I have a DNS issue, but I can't figure out where it is.....
0
 
BWaringCommented:
So now you only have the 1 IP address on the server? And there are no other references to .108 anywhere else?

Old article, but still valid: http://support.microsoft.com/kb/218814 check these areas...

0
 
dwar08Author Commented:
Yes I only have 1 IP address on the server and I can find no other references to the .108 address.  I'll take a look at the article and see if I can find anything in it that will help...
Thanks for your help...
0
 
dwar08Author Commented:
I'm going to close this one since essentially my questions were answered completely even though it has not solved my problem.  I will reopen another thread at a later date.
Thanks for your help....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.