DHCP and FQDN

[Scruff]

Afternoon all, hope your half-term is less stressful than mine =)

 

anyone know why dhcp would be registering some machines with FQDN and some without

 

here is a screenshot if i'm not making any sense....

 

http://www.protocolic.co.uk/edugeek/dhcp.JPG

[NetworkGeezer]

Are all machines on the domain?

 

You didn't show the MACs are the machines from the same manufacturer?

[Scruff]

Yeah they're all on the domain, same machine type (HP DC5100 SFF) and all from the same image.

 

The machines that don't have the domain in there aren't managing to update DNS also.

[Geoff]

The machines that don't have the domain in there aren't managing to update DNS also.

 

Fix this, and the problem will disappear.

[Scruff]

ANy ideas what might be wrong with that then ?

[Geoff]

Well the default for windows DNS is to require secure updates. If anythings gone wrong (duplicate SIDs, Kerberos time issues, secure channel failed, etc) the machine wont be able to update it's DNS records.

 

So you need to troubleshoot whats going wrong on these 'broken' machines. I'd start with netdiag.

[Guest]

try new sid to get rid of the duplicate sid issue

info here

http://www.microsoft.com/technet/sysinternals/Security/NewSid.mspx

we tend to run it on all ghosted pcs, as windows is not too keen on duplicate sids

[Scruff]

okie dokie,

 

Netdiag is reporting a fail as below:

 

Kerberos test. . . . . . . . . . . : Failed

[FATAL] Kerberos does not have a ticket for host/ABBEY10.

 

 

LDAP test. . . . . . . . . . . . . : Failed

[WARNING] The default SPN registration for 'HOST/ABBEY10' is missing on DC '

crstgs004.CRSTG.LOCAL'.

[WARNING] The default SPN registration for 'HOST/ABBEY10' is missing on DC '

crstgs006.CRSTG.LOCAL'.

[FATAL] The default SPNs are not properly registered on any DCs.

 

I removed the machine from AD, reattached to the domain (after running /fix)

 

released the dhcp lease and renew and same problem is still there, any ideas ?

 

Cheers chaps

[Scruff]

misterbusy-2,

 

That was my first action, still no joy though

 

Cheers

[Geoff]

Looks like a kerberos problem. 99% of the time it's because the machines time is not in sync with the server.

[tosca925]

I have had this problem as well, not sure how many machines though. I have had a few win32time errors in the event logs of a couple of servers so i guess Geoff is right.

 

Something i must sort out soon, will check when i am back in next week.

[Scruff]

I managed to get the machines registering dns ok with the 'Use this connection's DNS suffix in DNS registration' checkbox but the machines that were working originally don't have it set so it's not the root cause but has temporarily satisfied me.

 

I looked into the error being returned by Netdiag and there is an MS kb article stating it could be an error with the netdiag tool itself so i'm a little back to square one with resolving the overall difficulties with getting this network running correctly :|

 

oh well, back to the grind, it must be good if i'm working on a sunny sunday...