|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Private messages
Log in
|
|
| Author |
Message |
Guest
|
Posted: Wed May 17, 2006 5:12 pm Post subject: PC Authenticating to wrong DC - Sites & Services set properl |
|
|
Hello All,
I understand that this type of problem is hard to diagnose or solve
without a lot of detail, but I am hoping someone can at least offer
some suggestions or advice. I have a branch location with 3 PC's and a
DC that connects back to our main op center on a 64k frame relay (ugh,
I know) circuit and I have about 12 other such locations. At this
particular location I have just one PC that refuses to authenticate to
the local DC. The IP/Subnet are set properly and Sites and Services are
also properly configured including subnet. I also have the DNS on the
PC to look to the local DC first, and the PC's record is correct in
DNS. It doesn't even authenticate to our main op center DC which is
connected via T1, it is chosing another branch that is only on a 128k
frame relay circuit and not really geographically close.
My only thought at this time is to remove it from the domain and re-add
it tomorrow when I am at that location, but I was hoping for some other
help before I make the trip.
Thanks! |
|
| Back to top |
|
 |
|
|
Jorge de Almeida Pinto [M Guest
|
Posted: Fri May 19, 2006 12:51 am Post subject: Re: PC Authenticating to wrong DC - Sites & Services set pro |
|
|
does it always authenticate to the DCs in the same other site?
if yes, is it configured with the static site definition in the registry
try:
NLTEST /DSGETSITE
NLTEST /DSGETDC:<DOMAIN>
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<dominictiberio@gmail.com> wrote in message
news:1147871528.700936.12570@g10g2000cwb.googlegroups.com...
| Quote: | Hello All,
I understand that this type of problem is hard to diagnose or solve
without a lot of detail, but I am hoping someone can at least offer
some suggestions or advice. I have a branch location with 3 PC's and a
DC that connects back to our main op center on a 64k frame relay (ugh,
I know) circuit and I have about 12 other such locations. At this
particular location I have just one PC that refuses to authenticate to
the local DC. The IP/Subnet are set properly and Sites and Services are
also properly configured including subnet. I also have the DNS on the
PC to look to the local DC first, and the PC's record is correct in
DNS. It doesn't even authenticate to our main op center DC which is
connected via T1, it is chosing another branch that is only on a 128k
frame relay circuit and not really geographically close.
My only thought at this time is to remove it from the domain and re-add
it tomorrow when I am at that location, but I was hoping for some other
help before I make the trip.
Thanks!
|
|
|
| Back to top |
|
 |
Guest
|
Posted: Fri May 19, 2006 10:03 pm Post subject: Re: PC Authenticating to wrong DC - Sites & Services set pro |
|
|
Jorge de Almeida Pinto [MVP] wrote:
| Quote: | does it always authenticate to the DCs in the same other site?
if yes, is it configured with the static site definition in the registry
try:
NLTEST /DSGETSITE
NLTEST /DSGETDC:<DOMAIN
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
|
Thanks for the reply, I had removed it from the domain, and re-added it
and it instantly authenticated to the correct local DC. It was a
strange thing, it was correct in DNS, in Sites and Services, and
everything was pointing properly... had that not worked I would have
been completely stumped. |
|
| Back to top |
|
 |
|
|