Re: Connecting to DC in wrong site
From: ptwilliams (ptw2001_at_hotmail.com)
Date: 11/22/04
- Next message: Herb Martin: "Re: Multiple Sites and Multiple DCs"
- Previous message: ptwilliams: "Re: Connecting to DC in wrong site"
- In reply to: Tim Kalligonis: "Re: Connecting to DC in wrong site"
- Next in thread: Jeff: "Re: Connecting to DC in wrong site"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 21:05:05 -0000
There's the usual things checked.
I guess it's time to get network monitor out and trace what's happening...
-- Paul Williams http://www.msresource.net http://forums.msresource.net "Tim Kalligonis" <tkalligonis@comcast.net> wrote in message news:Ou1CpY2wEHA.3668@tk2msftngp13.phx.gbl... Yes, this site contains 3 GCs. The Machines and DCs are looking at the same DNS servers.... QIP, not Microsoft. DNS servers are in the same physical location as the DCs and clients(the ones I have seen the problem on) No supernetting that I can find. Subnet def in this site is correct for the sunbet where I have seen the issue. Clients are all XP. I haven't see a case on 2000, but we really don't have anything older than XP. "ptwilliams" <ptw2001@hotmail.com> wrote in message news:uGv6lYrwEHA.3824@TK2MSFTNGP15.phx.gbl... > You've also not mentioned whether or not you have a GC at this site. I > trust that you have at least one GC at this site? > > You may also want to consider where these machines are looking for their DNS > resolution. > > Finally, although you've checked it once, and are looking again for > supernetting, re-check the subnet associations. Perhaps you've declared a > 24 bit net mask for a 23 bit mask?? We had these problems, and it was a > typo in one of the subnets... > > I also assume that these are non-legacy clients? You often see legacy > clients going off after the PDCe <g> > > -- > > Paul Williams > > http://www.msresource.net > http://forums.msresource.net > ______________________________________ > "Tim Kalligonis" <tkalligonis@comcast.net> wrote in message > news:%23rUe6anwEHA.2908@tk2msftngp13.phx.gbl... > As far as I know... No. But I'll have to look into it to verify. > > > "ptwilliams" <ptw2001@hotmail.com> wrote in message > news:uSz69RewEHA.3292@TK2MSFTNGP15.phx.gbl... > > Are you using supernetted sites? > > > > That is, are you using a single subnet definition to capture two or three > > subnets, e.g. 192.168.0.0/22 whereas the actual subnets are 192.168.0.0/24 > > and 192.168.1.0/24 > > > > > > -- > > > > Paul Williams > > > > http://www.msresource.net > > http://forums.msresource.net > > ______________________________________ > > "Tim Kalligonis" <tkalligonis@comcast.net> wrote in message > > news:eF1MNZawEHA.1404@TK2MSFTNGP11.phx.gbl... > > I check everything both of you have mentioned. > > SRV records look good. > > I check a few machines that I have seen authenticate to remote DCs and the > > registry key is set to this local site. > > I check the remote DCs for event 5778, however I am running Win 2003. > Event > > ID change? Not likely. > > > > Any other ideas? > > > > "gordonah" <gordonah@discussions.microsoft.com> wrote in message > > news:368CD184-1513-48AC-A425-D763E432CB44@microsoft.com... > > > Tim > > > > > > somewhere in the registry (under netlogon/parameters?) there is a key > > called > > > dynamicsitename. If this somehow picks up the wrong setting it may > remain > > in > > > the registry and the value may need to be deleted). > > > If the client is attaching to a 'random' DC as it has failed to identify > a > > > subnet, then a 5778 error will be logged in the system event log of the > > > authenticating DC (for W2K). This will allow you to determine if there > is > > > some confusion of in sites and servers (in particular AD SS only checks > > for > > > uniqueness in the IP address portion of the subnet, it is possible to > > inout > > > overlapping subnets). For W2K3 the 5778 errors are rolled up in to > another > > > error saying "there have been x occurences of error 5778", or similar, > the > > > actual listing of affect clients in a local log file somewhere. > > > Hope this helps. > > > > > > Gordon > > > > > > "Tim Kalligonis" wrote: > > > > > > > We've been having an issue where random client machines connect to > > Domain > > > > Controllers outside of their site. > > > > I've only see the issue in the site I am located in, there have not > been > > > > reports of this issue from other sites so I'm not sure if this occurs > in > > > > those other sites or not. > > > > > > > > I've checked the obvious - make sure all subnets that are suppose to > be > > > > associated to this site are defined in the site. Checked the remote > > sites > > > > were these clients are connecting to making sure that the subnet is > not > > also > > > > defined somewhere else. > > > > > > > > Issue: Occasionally client will take a little longer than usual to > log > > into > > > > their machine. If the %logonserver% is check it will show they were > > > > authenticated to a domain controller outside of their site. It is > > usually a > > > > domain controller is one of three remote sites. We have a total of 26 > > > > sites. Then when ADUC is opened it will also connect to this remote > DC. > > > > > > > > Another interest piece of information is the fact that the site I am > > seeing > > > > this occur in has the most DCs in it, it has four DCs for this > > particular > > > > domain plus the FSMO roles reside on 2 of the 4 DCs in this site. > > > > > > > > I haven't been able to find and KB articles describing this problem. > > Has > > > > anyone experienced this problem or know of KB articles describing this > > > > issue? > > > > > > > > Thanks, > > > > Tim > > > > > > > > > > > > > > > > > > > > >
- Next message: Herb Martin: "Re: Multiple Sites and Multiple DCs"
- Previous message: ptwilliams: "Re: Connecting to DC in wrong site"
- In reply to: Tim Kalligonis: "Re: Connecting to DC in wrong site"
- Next in thread: Jeff: "Re: Connecting to DC in wrong site"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
