Logon server information

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

How do you see who your logon server is? I'm pretty sure there is a command
for this, but I can't remember. I need to see which of 2 DCs is logging
certain PCs on the network.
 
CD said:
How do you see who your logon server is? I'm pretty sure there is a command
for this, but I can't remember. I need to see which of 2 DCs is logging
certain PCs on the network.
Click to expand...

Open a command prompt:

set logonserver

(or probably just "set logon" or even "set log", or just "set" if you
don't mind looking through the environment variable list or forget
the name of the variable you need.)
 
webitect said:
Hello,

Is there a way I can change which server performs the logons?
Click to expand...

Generally no, and generally (in almost all cases) you
do not want to bother with such.

The idea is that the closest and most available
DC is the one which should be used, then it will
fall back to other DCs are needed.

In theory you can set up (artificial) sites but you
probably shouldn't be fooloing with such.
 
Hi again,

Thanks for the help. Now I think I have a problem, I have DC's side by side
one of them doesn't handle logons. The server that is handling logons is the
"backup one, where all the misc files and stuff are on. The App server
does not which I was hoping it would. I know this because the "backup"
server for some reason restarts every other night or soemthing like that and
nobody can log in, the following morning. So I have to tell them to either
turn it on or if it's on, I have to log into the server. I don't understand
why that might be. Any advice?

Thanks,

Ray
 
webitect said:
Hi again,

Thanks for the help. Now I think I have a problem, I have DC's side
by side one of them doesn't handle logons. The server that is
handling logons is the "backup one, where all the misc files and
stuff are on. The App server does not which I was hoping it would.
I know this because the "backup" server for some reason restarts
every other night or soemthing like that and nobody can log in, the
following morning. So I have to tell them to either turn it on or if
it's on, I have to log into the server. I don't understand why that
might be. Any advice?
Click to expand...

Check the event logs on the DC that isn't authenticating users. Also might
want to run netdiag and dcdiag (from the support tools) on that server.

Also, your other DC sounds like it has problems - check the event logs
there, too. Make sure you have good managed UPS devices connected to each
server.
 
webitect said:
Hi again,

Thanks for the help. Now I think I have a problem, I have DC's side by side
one of them doesn't handle logons.
Click to expand...

Then it is either BROKEN or not really a DC.

Fix it.
The server that is handling logons is the
"backup one, where all the misc files and stuff are on.
Click to expand...

In Win2000+ there are no backup domain controllers, only
DCs.
The App server
does not which I was hoping it would. I know this because the "backup"
server for some reason restarts every other night or soemthing like that and
nobody can log in,
Click to expand...

That's wrong too.
the following morning.
Click to expand...

And of course this.
So I have to tell them to either
turn it on or if it's on, I have to log into the server. I don't understand
why that might be. Any advice?
Click to expand...

Yes, almost all replication and authentication problems
in Win2000+ Domains are really DNS problems.

You should have DNS server running on both of these
machines.

Let's run DCDiag on every DC and send the output to
a text file, then search that file for FAIL, ERROR, WARN
and either fix or report the errors.

Double check your DNS against the followin if you still
have errors...


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:

nltest /dsregdns /server:DC-ServerNameGoesHere

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
 
I had the same problem like you. In our domain, there are many DCs and in
many site. When PCs in my site started, their logonserver may be not the one
in my site. Then I modified my DHCP server, add an item in the scope option,
the name server, config it as the ip address of the DC which is in our site.
And then, the problem was solved.
 
Back
Top