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

In news:B013DB84-6B04-4ED1-A6B3-AC77A6E2C0BA@xxxxxxxxxxxxx,
Paul Bergson <pbbergs@xxxxxxxxxxxxx> requesting assistance, typed the following:
The second commad I have should verify the dns service records on
your DC's. I assume you got no errors, but that surprises me with the
event log you also noted. When I asked you to over write the first
couple of octets it would have helped to keep them common, unless the
x.x was consistent across the lan, but you have a network with 8100+
devices if I did my math correctly. I wanted to see if you have
placed your dc in the proper subnet. From this I can't tell, but the
error doesn't appear to point to a network issue that I can see
anyways.
I would suggest for now try unteaming your dc and doing a stan alone
nic and disabling the second one to see if this helps.


Paul,

Funny (actually interesting), you mentioned unteaming the NICs. I must agree. It might actually be causing the problem, unless there's something else such as a security template applied, IPSec, or something else we are not aware of on the DC.

I ran into a similar situation with a friend's network. One of the DC's teamed NICs took a split second dump (more like 2 seconds), but re-initialized. After that, that specific DC failed to replicate or communicate with other DCs. I had a difficult time to nail down the problem. First time I've seen it. I wasn't able to get permission to unteam the NIC. Actually I really didn't want to until I got another DC up and running, whether a VM or physical, before attempting it, because it also had Exchange on it. To bandaid it to at least keep Exchange going, I pointed DNS to one of the other DCs, as well as changed Exchange's DC references. I got it going at least until they can get a VM DC up, as well as an intermediary VM Exchange up and running so I can use it to move MBXs, PFs, etc, off this machine, then remove Exchange, force demote it, then rebuild it to be only an Exchange server and move the MBXs, PFs, etc, back to it.

So you may be on to something concerning the teaming possibly causing the problem.

Also, to the original poster (Andrew):
Please run the following and post any errors in the results:
netdiag /v /fix
dcdiag /v /fix

--?
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.

.

Relevant Pages

  • Re: Internet Mail Wizard
    ... Got to Device Manager and make sure the NIC drivers have been removed. ... Click the network adapter, and then click Uninstall on the Action menu. ... >I have installed Exchange 2003 only have one nic in machine. ... > There were two nics installed when I setup exchange but I took the one ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 can not send externally
    ... If the external NIC is enabled we can recieve ... problems with receiving aren't server problems but network routing or name ... the exchange services fixed the email sending issue. ... multiple NICs is often confused. ...
    (microsoft.public.exchange.admin)
  • Re: SBS 2003 Pop3 Access
    ... Enable POP3 collection from Exchange 2003 on SBS 2003 ... either the external NIC (if you have 2 NICS in the SBS server) or to the ... NIC in the SBS server (if you only have a 1 NIC network setup). ...
    (microsoft.public.windows.server.sbs)
  • Re: Advice needed - running Exchange
    ... know how, or if, you can setup Exchange using just 1 NIC. ... Network configuration - Two NICs, a static IP address, ISA, router: ... my SBS server, or can I just use the one. ... I have a dynamic IP with the ISP. ...
    (microsoft.public.windows.server.sbs)
  • Re: Same two Domain Names in the same network
    ... in migrating exchange from old server to the new. ... Both these domain exist in the same network. ... "Meinolf Weber" wrote: ... roles can only be on a dDC not on a member server. ...
    (microsoft.public.win2000.dns)
Loading