Re: [WARNING] Failed to query SPN registration on DC
- From: "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
- Date: Wed, 14 Jan 2009 23:21:12 -0500
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
.
- Follow-Ups:
- Re: [WARNING] Failed to query SPN registration on DC
- From: Andrew Story
- Re: [WARNING] Failed to query SPN registration on DC
- References:
- [WARNING] Failed to query SPN registration on DC
- From: Andrew Story
- Re: [WARNING] Failed to query SPN registration on DC
- From: Paul Bergson
- Re: [WARNING] Failed to query SPN registration on DC
- From: Andrew Story
- Re: [WARNING] Failed to query SPN registration on DC
- From: Paul Bergson
- Re: [WARNING] Failed to query SPN registration on DC
- From: Ace Fekay [Microsoft Certified Trainer]
- Re: [WARNING] Failed to query SPN registration on DC
- From: Andrew Story
- Re: [WARNING] Failed to query SPN registration on DC
- From: Andrew Story
- [WARNING] Failed to query SPN registration on DC
- Prev by Date: Re: ADAM - Classes & Attributes
- Next by Date: Re: Group membership in sub-domains
- Previous by thread: Re: [WARNING] Failed to query SPN registration on DC
- Next by thread: Re: [WARNING] Failed to query SPN registration on DC
- Index(es):
Relevant Pages
|
Loading