When to use "net stop[start] netlogon" command

  • Thread starter Thread starter Kevin
  • Start date Start date
K

Kevin

I have always wanted to know what is a proper situation to
use this command. What does is do exactly? Is this a
troubleshooting step? Is it used quite frequently for DNS
problems?


What about the command "ipconfig /flushdns"
and "ipconfig /registerdns"? When should I use it?

Thanks for the advice
 
Kevin said:
I have always wanted to know what is a proper situation to
use this command.
Click to expand...

Whenever you (the admin) need a service to be stopped or started.
What does is do exactly?
Click to expand...

Exactly what it says -- the same thing the services control panel does.
Stops the "logon" service: NetLogon -- the service on a DC that handles
logon and also is responsible for registering Win2000+ DCs with DNS.
Is this a troubleshooting step?
Is it used quite frequently for DNS problems?
Click to expand...

It is a common step for DCs AFTER fixing a DNS problem (not for DNS itself.)
What about the command "ipconfig /flushdns"
and "ipconfig /registerdns"? When should I use it?
Click to expand...

[Beginning to sound more and more like some student wanting us to do his
homework...<grin>]

/flushDNS and /registerDNS are almost completely unrelated to each other
in function (except they both have 'something' to do with DNS <grin>)

'Flush' clears the client side cache -- it's useful if you suspect the
client is caching
stale information after a DNS problem has been fixed.

'Register' (re)registers the clients OWN name/address with it's DNS server.

Note: Register is INSUFFICIENT for re-registering a DC after a problem with
Dynamic DNS or the DC is fixed -- for that you must use the net stop/start
on
the "NetLogon" service.

This IS a common troubleshooting step for DCs after fixing DNS problems.
 
Back
Top