This document is useful when troubleshooting connection problems for campus network users.
If a user is unable to connect to the network, first check for a valid IP address by doing the following:
Generally, UW-Madison IP addresses fall within 128.x.x.x, 146.x.x.x, or 144.x.x.x. An IP address of 169.254.x.x or 192.168.x.x is a private IP address automatically assigned by Windows when it is unable to locate a DHCP server on the network.
netsh int ip reset resetlog.txt
ipconfig /renew
and press enter. Does the machine come back with the same IP address as before or a different one? If the new IP address is valid, try going to a common website again.
If a user is unable to connect to the network, first check for a valid IP address by doing the following:
Generally, UW-Madison IP addresses fall within 128.x.x.x, 146.x.x.x, or 144.x.x.x. An IP address of 169.254.x.x or 192.168.x.x is a private IP address automatically assigned by Windows when it is unable to locate a DHCP server on the network.
netsh int ip reset resetlog.txt
ipconfig /renew
and press enter. Does the machine come back with the same IP address as before or a different one? If the new IP address is valid, try going to a common website again.
If a user is unable to connect to the network, first check for a valid IP address by doing the following:
Type "command" in the search bar, as shown below, and press enter:
When the command prompt appears, enter ipconfig and press enter. If the machine is properly configured, ipconfig should return a valid IP address, as shown below:
Generally, UW-Madison IP addresses fall within 128.x.x.x, 146.x.x.x, or 144.x.x.x. An IP address of 169.254.x.x or 192.168.x.x is a private IP address automatically assigned by Windows when it is unable to locate a DHCP server on the network.
If ipconfig returns an invalid or private IP address, the issue may be with the network connection configuration. If so, refer to Wireless UWNet - Unable to Connect for more information about properly configuring Windows to connect to the campus network. If the connection is properly configured, try the following steps:
Try accessing a common website, such as Google. If the page does not load, continue.
Click on Start, then select Control Panel.
Under Network and Internet, click View network status and tasks.
This will bring up the Network and Sharing Center. In the Connections: section, click Local Area Connection, as shown below.
Try pinging a common website like www.wisc.edu or www.google.com:
In the command prompt, type "ping www.wisc.edu" or "ping www.google.com" and press enter. If the connection is working correctly, it should appear roughly as shown below. Otherwise, you may see an "unknown host" or "unable to resolve" error.
If unable to ping www.wisc.edu, try typing "ping 144.92.104.243" to test whether the issue is with the DNS servers or Winsock issue. If "ping 144.92.104.243" connects without error, type the following:
netsh int ip reset resetlog.txt
Try renewing the IP address.
ipconfig /renewand press enter. Does the machine come back with the same IP address as before or a different one? If the new IP address is valid, try going to a common website again.
If the connection still isn't working despite pulling down a valid IP address, you should try commands for Windows given in Windows - Quick Fix for Networking Problems.
If that fails, you should verify the network card is working properly by checking the Device Manager.
The System control panel will appear as below. Click on Device Manager.
If a user is unable to connect to the network, first check for a valid IP address by doing the following:
Type "command" in the search bar, as shown below, and press enter:
When the command prompt appears, enter ipconfig and press enter. If the machine is properly configured, ipconfig should return a valid IP address, as shown below:
Generally, UW-Madison IP addresses fall within 128.x.x.x, 146.x.x.x, or 144.x.x.x. Campus Network (Housing) IPs fall in the range of 10.x.x.x. (See [Link for document 76064 is unavailable at this time.].)An IP address of 169.254.x.x or 192.168.x.x is a private IP address automatically assigned by Windows when it is unable to locate a DHCP server on the network.
If ipconfig returns an invalid or private IP address, the issue may be with the network connection configuration. If so, refer to Wireless UWNet - Unable to Connect for more information about properly configuring Windows to connect to the campus network. If the connection is properly configured, try the following steps:
Try accessing a common website, such as Google. If the page does not load, continue.
This will bring up the Network and Sharing Center, as shown below
Try pinging a common website like www.wisc.edu or www.google.com:
In the command prompt, type "ping www.wisc.edu" or "ping www.google.com" and press enter. If the connection is working correctly, it should appear roughly as shown below. Otherwise, you may see an "unknown host" or "unable to resolve" error.
If unable to ping www.wisc.edu, try typing "ping 144.92.104.243" to test whether the issue is with the DNS servers or Winsock issue. If "ping 144.92.104.243" connects without error, type the following:
netsh int ip reset resetlog.txt
Try renewing the IP address.
ipconfig /renewand press enter. Does the machine come back with the same IP address as before or a different one? If the new IP address is valid, try going to a common website again.
If the connection still isn't working despite pulling down a valid IP address, you should try commands for Vista given in Windows - Quick Fix for Networking Problems.
If that fails, you should verify the network card is working properly by checking the Device Manager.
The System control panel will appear as below. Click on Device Manager.