I have an AD environment with a main site and several remote sites.
Recently, I had a laptop user travel from our main site to a remote site and
he experienced some authentication issues. Even though he was at the remote
site, his PC tried to authenticate against the DCs at our main site. When
he came back to our main site, the PC authenticated against a DC at a remote
site.

Now I am preparing to deploy a desktop PC at our main site and it is
authenticating against one of the remote sites. If I run netdiag, the trust
relationship test fails because it cannot test the secure channel for our
domain and one of the DCs at our main site.

Where do I start troubleshooting this issue? The biggest problem is with
replication. Our remote sites only replicate at night to reduce bandwidth
consumption.

Please help. . . .

Thanks,

Jeff

Do you have your sites setup corectly in AD sites and services with
apropriate subnet objects ? If you setup sites right, then your client pc's
should authenticate in local site.

--

Regards

Matjaz Ladava, MCSA, MCSE, MCT, MVP
Microsoft MVP Windows Server - Active Directory
(E-Mail Removed), (E-Mail Removed)



"Jeff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have an AD environment with a main site and several remote sites.
> Recently, I had a laptop user travel from our main site to a remote site
> and
> he experienced some authentication issues. Even though he was at the
> remote
> site, his PC tried to authenticate against the DCs at our main site. When
> he came back to our main site, the PC authenticated against a DC at a
> remote
> site.
>
> Now I am preparing to deploy a desktop PC at our main site and it is
> authenticating against one of the remote sites. If I run netdiag, the
> trust
> relationship test fails because it cannot test the secure channel for our
> domain and one of the DCs at our main site.
>
> Where do I start troubleshooting this issue? The biggest problem is with
> replication. Our remote sites only replicate at night to reduce bandwidth
> consumption.
>
> Please help. . . .
>
> Thanks,
>
> Jeff
>
>

yup. sites are set up appropriately. I am running into some strange DNS
errors when I do a netdiag and dcdiag, though. Trying to determine what is
causing them.


"Matjaz Ladava [MVP]" <matjaz@_nospam_ladava.com> wrote in message
news:%(E-Mail Removed)...
> Do you have your sites setup corectly in AD sites and services with
> apropriate subnet objects ? If you setup sites right, then your client
pc's
> should authenticate in local site.
>
> --
>
> Regards
>
> Matjaz Ladava, MCSA, MCSE, MCT, MVP
> Microsoft MVP Windows Server - Active Directory
> (E-Mail Removed), (E-Mail Removed)
>
>
>
> "Jeff" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >I have an AD environment with a main site and several remote sites.
> > Recently, I had a laptop user travel from our main site to a remote site
> > and
> > he experienced some authentication issues. Even though he was at the
> > remote
> > site, his PC tried to authenticate against the DCs at our main site.
When
> > he came back to our main site, the PC authenticated against a DC at a
> > remote
> > site.
> >
> > Now I am preparing to deploy a desktop PC at our main site and it is
> > authenticating against one of the remote sites. If I run netdiag, the
> > trust
> > relationship test fails because it cannot test the secure channel for
our
> > domain and one of the DCs at our main site.
> >
> > Where do I start troubleshooting this issue? The biggest problem is with
> > replication. Our remote sites only replicate at night to reduce
bandwidth
> > consumption.
> >
> > Please help. . . .
> >
> > Thanks,
> >
> > Jeff
> >
> >
>
>