WAN DC

[forumit]

We have multiple sites with some small sites without DC's. What is the best way to check which DC they are using to authenticate?
Also some computers with their on site DC takes about 30 mins to logon. Their DNS are pointing to the local DNS server.

 

[58sniper]

Look in AD Sites and Services. Computers will log into a DC in their site, or whichever site house their subnet (and has a DC).

You can go to a computer, open a command prompt, and type "set". Look for the logonserver parameter.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[forumit]

Thanks for set command. Another command can also be "systeminfo"
What will be the reason for such long login process as the computer is pointing to a local AD & DNS server?

 

[58sniper]

Generally, long login times point to a DNS problem, in my experience. If you search here, you'll find others with the same problem, caused by DNS.

I'd look at ping results from the workstation. Ping the domain, ping the DC, etc.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[itsp1965]

Besides possible DNS issues what kind of WAN links do you have to these smaller offices? If they are slow you may need to re-configure sites for slower links (SMTP link I think)

 

[forumit]

User with slow login have own DC at site. Can the user profile size be an issue? DNS entries are all correct.Takes about 30 mins to login.

 

[theravager]

set from a command prompt will show it in the varibles.

Logonserver is the one you are looking for off memory

 

[58sniper]

The user profile should only be an issue if it's a roaming profile stored on another server, and monster size. 30 minutes to login is a serious issue. That 30 minutes of lost productivity is expensive. Look through the event logs on the workstation.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[forumit]

Feedback: It seems removing the computer from domain and joining again solved the problem.