One of the first things you can do in terms of troubleshooting is to determine whether you have network connectivity between your hosts.
This recipe uses servers in the Reskit.Org domain (DC1, DC2, SRV1, and SRV2)that you have previously installed. Run this recipe on SRV1.
- Use
Test-Connectionto test the connection toDC1:Test-Connection -ComputerName DC1
- Redo the test with a simple true/false return:
Test-Connection -ComputerName DC1 -Quiet
- Test multiple systems at once:
Test-Connection -ComputerName 'DC1','DC2','SRV2' -Count 1
- Test the connectivity for
SMBtraffic withDC1:Test-NetConnection -ComputerName DC1 -CommonTCPPort SMB
- Get a detailed connectivity check by using
DC1with HTTP:$TNCHT = @{ ComputerName = 'DC1' CommonTCPPort = 'HTTP' InformationLevel = 'Detailed' } Test-NetConnection @TNCHT - Look for a particular port (that is,
SMBonDC1):Test-NetConnection -ComputerName DC1 -Port 445
- Look for a host that does not exist:
Test-NetConnection -ComputerName 10.10.10.123
- Look for a host that exists but a port/application that does not exist:
Test-NetConnection -ComputerName DC1 -PORT 9999
In step 1, you checked the network connectivity from SRV1 to DC1 using the Test-NetConnection cmdlet, which looks like this:
In step 2, you repeated this test using the -Quiet switch, which looks like this:
In step 3, you used Test-Connection to test connections from SRV1 to multiple remote servers, which looks like this:
The Test-NetConnection cmdlet provides additional parameters. In step 4, you tested whether SRV1 can reach the SMB server service on DC1. SRV1 uses this port to download group policy details. The output looks like this:
You can also get a more detailed report of attempted connectivity. You can use the -InformationLevel parameter set to detailed so that you receive more information on the attempt to connect. In step 5, you checked whether SRV1 can create a HTTP connection with DC1, as follows:
In step 6, you used Test-NetConnection to test the connectivity to a numbered port, port 389 on DC1. Port 389 is the LDAP port that an AD client uses to talk to a domain controller. The output of this step looks like this:
