Computer logs on to different DC

Hi,

I have a computer who, when trying to log on to the network, instead of
using the local DC (in its own subnet), goes out and tries other servers from
our network (multiple locations in the country) network, thus taking a very
long time (compared to what's usual) to login, showing the "applying computer
settings" message.

Strange is that, while the network config is exactly the same as the other
computers in the same subnet, it's the only one with this behaviour. Both IP
and DNS are set to automatic.

I've tried a number of remedies, including a hotfix from MS (a new
kerberos.dll), disabling the WebClient service, removing and re-including the
machine in the domain and several others. Even setting the IP and DNS
manually and then creating a reserve in the correct DC didn't work.

Though it looks like a typical DNS problem, I'm having my doubts, from all
the resolution attempts made so far.

Any help would be appreciated, thanks.

Your AD should make use of "Sites". The right DC needs to be in the right
"AD Site". Clients will always use the DC in their own "Site".

If they can not find their own nearest DC then they are *supposed* to look
for other DCs.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Daniel" <(E-Mail Removed)> wrote in message
news:C61FB6C3-5878-48BC-BA6E-(E-Mail Removed)...
> Hi,
>
> I have a computer who, when trying to log on to the network, instead of
> using the local DC (in its own subnet), goes out and tries other servers
from
> our network (multiple locations in the country) network, thus taking a
very
> long time (compared to what's usual) to login, showing the "applying
computer
> settings" message.
>
> Strange is that, while the network config is exactly the same as the other
> computers in the same subnet, it's the only one with this behaviour. Both
IP
> and DNS are set to automatic.
>
> I've tried a number of remedies, including a hotfix from MS (a new
> kerberos.dll), disabling the WebClient service, removing and re-including
the
> machine in the domain and several others. Even setting the IP and DNS
> manually and then creating a reserve in the correct DC didn't work.
>
> Though it looks like a typical DNS problem, I'm having my doubts, from all
> the resolution attempts made so far.
>
> Any help would be appreciated, thanks.

Hi Phillip, thanks for the swift reply

Sorry that I wasn't specific, but our AD does use Sites and the DC is in the
correct site. The other machines in this Site have no problems, only this
one. And as mentioned before, the network configs are the same.

Thanks once again,
Daniel

"Phillip Windell" wrote:

> Your AD should make use of "Sites". The right DC needs to be in the right
> "AD Site". Clients will always use the DC in their own "Site".
>
> If they can not find their own nearest DC then they are *supposed* to look
> for other DCs.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

"Daniel" <(E-Mail Removed)> wrote in message
news:9F5EC539-C132-4E03-A0F2-(E-Mail Removed)...
> Sorry that I wasn't specific, but our AD does use Sites and the DC is in
the
> correct site. The other machines in this Site have no problems, only this
> one. And as mentioned before, the network configs are the same.

Ah,..Ok. Well you have me there,...I don't know what to think about that.
Hang around see if any others have ideas.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Phillip Windell" wrote:

>
> Ah,..Ok. Well you have me there,...I don't know what to think about that.
> Hang around see if any others have ideas.

Thanks again Phillip

Let's see who can give any ideas. Pretty much stumped here, I wouldn't be
surprised if it ended up being something sooo simple, I would want to bang
my head against the wall. But after so much trial and error...

Daniel

Hi Dan,

Does the DC on the local subnet host DNS/DHCP?
Could you post info from ipconfig /all command.

You could also check the SRV records in DNS to check that there is one for
the local DC, DHCP should provide this i think...


"Daniel" wrote:

> Hi,
>
> I have a computer who, when trying to log on to the network, instead of
> using the local DC (in its own subnet), goes out and tries other servers from
> our network (multiple locations in the country) network, thus taking a very
> long time (compared to what's usual) to login, showing the "applying computer
> settings" message.
>
> Strange is that, while the network config is exactly the same as the other
> computers in the same subnet, it's the only one with this behaviour. Both IP
> and DNS are set to automatic.
>
> I've tried a number of remedies, including a hotfix from MS (a new
> kerberos.dll), disabling the WebClient service, removing and re-including the
> machine in the domain and several others. Even setting the IP and DNS
> manually and then creating a reserve in the correct DC didn't work.
>
> Though it looks like a typical DNS problem, I'm having my doubts, from all
> the resolution attempts made so far.
>
> Any help would be appreciated, thanks.

http://support.microsoft.com/default...b;en-us;247811
How Domain Controllers Are Located in Windows