oosama123MemberJanuary 2, 2012 at 2:55 am #157314
hello, first of all sorry for my language i hope you can understand me :)
Yesterday I did migration from server 2003 to 2008.
I installed a new 2008 machine then I transferred the roles the removed the 2003 from my server ( it was virtual).
The 2008 take the ip of 2003 (10.0.0.5) but not the name
2003 name = dc.domain.com
2008 name =cd-2008.domain.com
Now everything’s goes fine but at event viewer there is many errors , and when I restart the server it take long time to start.
The errors :
Log Name: DNS Server
Date: 1/2/2012 11:53:38 AM
Event ID: 7062
Task Category: None
The DNS server encountered a packet addressed to itself on IP address 10.0.0.5. The packet is for the DNS name “_ldap._tcp.mss.com.jo.”. The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.
Log Name: Directory Service
Date: 1/2/2012 11:52:27 AM
Event ID: 1645
Task Category: DS RPC Client
User: ANONYMOUS LOGON
Active Directory Domain Services did not perform an authenticated remote procedure call (RPC) to another directory server because the desired service principal name (SPN) for the destination directory server is not registered on the Key Distribution Center (KDC) domain controller that resolves the SPN.
Destination directory server:
Thank you and sorry again …
pjhutchMemberJanuary 2, 2012 at 5:54 am #312760
Re: after upgrade , problem with DNS and Ad
Sounds like problems with DNS and its getting itself confused.
1. Open Network adapter and make sure its properties are set correctly and make sure that its own address is in the DNS list.
2. Open cmd prompt and run IPCONFIG /RegisterDNS to re-register itself in DNS
3. Open DNS Mgmt console and check everything:
a) Make sure that the Host (A) address and reversable addresses and names are correct.
b) At the root make sure that its own address is correct and names match and
c) Check all SRV records are correct.
d) Run the SETSPN on its account to fix any SPN errors.
You must be logged in to reply to this topic.