Machines logging on the Domain.

Is there something (a script, software (free) I can run to see exactly what's happening when my machines try to login to my network.  I'm looking to see what DC they hit specfically.  I can put the login in Verbose mode to see the policies but I'm looking to see if I can find out how the packets are flowing.  Is this possible?  I would need to run this from my own PC I don't have access to my DCs...
WellingtonISAsked:
Who is Participating?
 
eli_cookConnect With a Mentor Commented:
It shouldn't be contacting another site, using DNS your computer requests information about the KDC then contacts the KDC for authentication. Microsoft has a detailed break down of the interactive login process here. Like Brad had mentioned you would need to use some software like wireshark if you wanted to monitor everything that passes through your network cable.
0
 
eli_cookCommented:
You can check your logon server by entering the following in the command line
echo %logonserver%

Open in new window

From the command line you can run the following to see the applied group policy objects and which server the group policy is applied from.
GPRESULT /R

Open in new window



Could you elaborate a little more on packet flow? Is there specific problem or error you are receiving?
0
 
WellingtonISAuthor Commented:
Yes I'm looking to see how the machine actually connect to the DC's - We have issues logging in long wait times  and I'm trying to figure out the process the machine and the DC's use to connect.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Brad BouchardInformation Systems Security OfficerCommented:
You can check your logon server by entering the following in the command line




echo %logonserver%
1:



Select all

Open in new window
Another way to do this easily is at the command prompt typing   SET L
0
 
eli_cookCommented:
I would first check the System Event logs for errors in processing Group Policy. Long wait times during login can be attributed to timeouts for Group Policy resources that are not available. I would also look at any errors that occur during a logon on the workstation. To do this I would either set a mark time that you use as your restart and only look at errors after that time or clear the event log and then restart the machine for a login.

Does this affect all machines all the time on the network or is it intermittent or only with specific machines?
0
 
Brad BouchardConnect With a Mentor Information Systems Security OfficerCommented:
Yes I'm looking to see how the machine actually connect to the DC's - We have issues logging in long wait times  and I'm trying to figure out the process the machine and the DC's use to connect.
Try using Wireshark.  Guide here:  http://www.wireshark.org/download/docs/user-guide-a4.pdf
0
 
WellingtonISAuthor Commented:
not all machines just some.  But I think there's issues with the DC's because they are replicating to an office a few states away and I thing i'm logging in over the wan not locally
0
 
WellingtonISAuthor Commented:
echo %logonserver%
1:



Select all

Open in new window


Another way to do this easily is at the command prompt typing   SET L


Will this tell if it the machine attempted to login to some other DC before It logged into mine?  Or just where the machine landed (so to speak)
0
 
Brad BouchardInformation Systems Security OfficerCommented:
Just where it landed unfortunately.
0
 
WellingtonISAuthor Commented:
I'm looking to see before that when the machine goes out and requests service to the DC...
0
 
eli_cookCommented:
Run the following command:
nltest /dsgetsite

Open in new window

This should return the Active Directory Site your computer is associated with.

Then run the command with the name of the logon server:
nltest /server:servernamehere /dsgetsite

Open in new window

This will return the Active Directory Site that your logon server is associated with.

Are they the same?

If so we need to see if we can figure out if your logon server is indeed at your location or the other.
0
 
WellingtonISAuthor Commented:
yest the results are the same - the name of my site..  But is there a way to check to see if it went out to another DC first?? The structure is we are a large domain spread out over several states.  All DCs are connected.
0
 
WellingtonISAuthor Commented:
I totally agree with you but I still suspect that some how we are.  I'll try wireshare and see.  Thanks all -
0
 
WellingtonISAuthor Commented:
Thanks all
0
 
eli_cookCommented:
I would use Resultant Set of Policy (RSoP) to determine what your group policy looks like.
Type the following at the command line:  
rsop

Open in new window

to bring up the screen. You will need to analyze the areas here to determine if say a batch script is being run at logon that is meant for another site.

Logon scripts can be found Under User Configuration --> Windows Settings --> Scripts --> Logon

You will need to look at each of the scripts individually.
0
All Courses

From novice to tech pro — start learning today.