Re: [WARNING] Failed to query SPN registration on DC

Tech-Archive recommends: Fix windows errors by optimizing your registry

runing both now, this may take a while will post back unedited results once
completed.


"Paul Bergson [MVP-DS]" <pbbergs@xxxxxxxxxxxxxxx> wrote in message
news:50259049-A9DF-4012-9A66-DAAD33E17A5A@xxxxxxxxxxxxxxxx
You said dcdiag is clean but how about rerunning. With the switches
defined below:

DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL
dc's in the forest. If you have significant numbers of DC's this test
could generate significant detail and take a long time. You also want to
take into account slow links to dc's will also add to the testing time.


--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Andrew Story" <andrewDOTstoryATjameswalkerDOTbiz> wrote in message
news:uEgbMovdJHA.3692@xxxxxxxxxxxxxxxxxxxxxxx
Morning,

Yes have unteamed the NIC's, and have the secondary one disabled. Just
moved the first NIC to the top of the binding order (it was second in the
list) and ran through Jorge's list of taks below but still the same
error, even rebooted the server.

The server is listed as a NS on it's own copy of the DNS zone, but not on
any other DC's.....


"Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
wrote in message news:OdS2NjsdJHA.1272@xxxxxxxxxxxxxxxxxxxxxxx
In news:eO6WdejdJHA.5540@xxxxxxxxxxxxxxxxxxxx,
Andrew Story <andrewDOTstoryATjameswalkerDOTbiz> requesting assistance,
typed the following:
No joy I'm afraid guys, sames errors persist. Have tried Jorge's
suggestion also.


Those SPN errors are still prevalent even after unteaming the NICs?
After unteaming, make sure you disable one of the NICs, and move the
other NIC to the top of the binding order in Network
Connections\Advanced Menu\Advanced. Re-run the registration process Paul
outlined. See if that helps.

Also, curious, in DNS properties, Nameservers tab, do both DCs (or all
DCs for that matter), show up?


Ace





.

Relevant Pages

  • Re: [WARNING] Failed to query SPN registration on DC
    ... Andrew Story requesting assistance, ... Those SPN errors are still prevalent even after unteaming the NICs? ... Also, curious, in DNS properties, Nameservers tab, do both DCs, show up? ...
    (microsoft.public.windows.server.active_directory)
  • Re: [WARNING] Failed to query SPN registration on DC
    ... moved the first NIC to the top of the binding order (it was second in the ... Those SPN errors are still prevalent even after unteaming the NICs? ... Also, curious, in DNS properties, Nameservers tab, do both DCs (or all DCs ...
    (microsoft.public.windows.server.active_directory)
  • Re: [WARNING] Failed to query SPN registration on DC
    ... You said dcdiag is clean but how about rerunning. ... With the switches defined below: ... Those SPN errors are still prevalent even after unteaming the NICs? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Slow browsing within folders
    ... There are 2 DCs acting as DNS too. ... I was wondering if it would be possible, since the server has 2 NICs to add ... an additional CPU and split 1 NIC per CPU. ...
    (microsoft.public.windows.server.networking)
  • Re: Multihomed Domain Controller Setup
    ... >so that the DCs can have network access to the internal subnet computers. ... >Should I not use the second NICs and connect all DCs to live subnets only? ... will the internal subnet clients authenticate okay and get the GPOs ...
    (microsoft.public.windows.server.active_directory)