campus.hartland.edu: Network: Campus Network Diagnostic Procedure

Verify your computer is physically attached to the network
- For wired networks: Ethernet cable is attached and link light is illuminated
- For wireless networks: Wireless network indicator indicates an active connection
Examine your computer’s IP configuration
1. Open a command terminal (cmd) and type ipconfig /all
2. Inspect the command output, and identify the relevant network connection.
  - Dhcp Enabled should be set to Yes. If this is not set to Yes, your computer is configured incorrectly. Stop.
  - Autoconfiguration Enabled should be set to Yes. If this is not set to Yes, your computer is configured incorrectly. Stop.
  - IP Address, Default Gateway, DHCP Server, and DNS Server should all begin with 10.
  - Subnet Mask should begin with 255.
3. If the above settings do not match, your computer is connected to the wrong network, malfunctioning, or a local network device is malfunctioning. Stop.
Ping the Core Router
1. Type ping 10.0.0.1
2. Request timed out indicates a problem with the local network link or Core Router. Stop.
Check DNS
1. Type ping ns.campus.hartland.edu
  - Request timed out indicates a problem with the Local DNS Server. Stop.
  - Ping request could not find host … indicates a problem with the Local DNS Server. Stop.
  - Reply from … indicates that the Local DNS Server is responding normally. Continue.

NetAccess Server

Sign in to NetAccess Client
- NetAccess Client should indicate SonicWall login successful in the status area at the bottom of the NetAccess Client window.
- If NetAccess Client displays message window, read the message and follow any instructions carefully. Contact Media Services if necessary.
- If NetAccess Client does not respond within 30 seconds, there may be a problem with NetAccess Server. Contact Media Services.
Type ping www.google.com
- You should see the text Pinging something.google.com [some ip address]
- Ping request could not find host … may indicate a problem with the remote network (internet connection). Continue.
- Request timed out is not relevant and should be ignored. Continue.
- Reply from … indicates a functioning connection to the remote network (internet connection). Stop.

Ping the Edge Router
1. Type ping 12.47.113.113
2. Request timed out indicates a problem with the Edge Router. Stop. Physically inspect the Edge Router in the (old) HLC IT room. Verify power, status indicators, and network link back to Core Router.
Ping the Upstream Router
1. Type ping 12.124.233.66
2. Request timed out indicates a problem with the Upstream Router. Stop. Make sure you have performed all previous diagnostic steps, then contact AT&T WorldNet technical support.
Ping the Remote DNS Servers
1. Type ping 12.127.16.68
2. Type ping 12.127.17.72
3. If both pings return Request timed out, there may be a problem with the External DNS Servers. Stop. Make sure you have performed all previous diagnostic steps, then contact AT&T WorldNet technical support.