Getting someone online troubleshooting network connections
Determine the fail point in the network ( this is to be done to determine the issue if it’s a
persistent problem) For the fix just see THE FIX at the end
start
run
cmd
type ipconfig and enter
if the address begins with 192 or 10 then the user has a DHCP server also known as a
router or server
if the address begins with 169 the computer cannot receive an address from the DHCP
server (router or modem)
if the address begins with anything else then the pc should be online
to test
type ping http://www.google.com
if this fails then the issue could be DNS (ping the ip of google to determine this) if it
succeeds then its online so verify IE settings or try an alternative browser.
If the user has a router ask them to go to
start
run
cmd
type ipconfig
ask the user the default gateway
this is they address of the DHCP server in this case the router
then ask them to type ping (input router address)
the address should be 192.168.1.1 or 192.168.0.1 depending on the brand
if this ping gets replies then the connection from the computer to the router is ok
next would be the connection from the router to the cable modem
to see if its connected login to the router
type its address into the address bar of internet explorer user names are generally blank
and the password is usually admin or password
once in the router see the status page to verify you have a connection with a public ip
address and dns servers. Most devices will have a release and renew button to try to re
obtain an ip address. Also most routers offer a command line to test connectivity with
commands from that point. In addition you can check for connectivity to the modem by pinging 192.168.100.1 then you
can use the same address to login to the modem an see its log.
THE FIX (if no router then skip the router steps)
80% of all connection issues can be resolved the same way but the troubleshooting will allow you to document the connection issue for a history.
power cycle the devices in the order the connection comes into the house:
turn off the computer
unplug the power from the router
unplug the power from the cable modem
wait 30 seconds
plug in the power to the cable modem and wait 25 seconds until the lights are all lit solid
plug in the power to the router and wait 20 seconds
power up the computer
test the connection
80% of the time this will fix the issue if not then ask to plug the computer direct into the
cable modem to test router failure.
MORE NOTES
If the computer is directly plugged into the modem and it has an ip address and dns
address and still will not display a web page. Or if the computer is connected to a router and
another computer plugged into the router is online see below:
Reset IE (search forum) and check the host file for bad entries or try an alternate browser. Ask if viruses have been an
issue. Often viruses will edit the TCP/IP stack in windows this can cause connection errors.
Rewriting the TCP/IP stack is different in every OS so search out the process of doing this.
Also ping (ip) –t can be used to test the reliability of the connection between devices
Also tracert can be used in larger networks
Also run ncpa.cpl on any windows system to get to network connections and verify TCP/IP settings of the interface in use, sometimes its just a bad static configuration.

Determine the fail point in the network ( this is to be done to determine the issue if it’s a
persistent problem) For the fix just see THE FIX at the end
start
run
cmd
type ipconfig and enter
if the address begins with 192 or 10 then the user has a DHCP server also known as a
router or server
if the address begins with 169 the computer cannot receive an address from the DHCP
server (router or modem)
if the address begins with anything else then the pc should be online
to test
type ping http://www.google.com
if this fails then the issue could be DNS (ping the ip of google to determine this) if it
succeeds then its online so verify IE settings or try an alternative browser.
If the user has a router ask them to go to
start
run
cmd
type ipconfig
ask the user the default gateway
this is they address of the DHCP server in this case the router
then ask them to type ping (input router address)
the address should be 192.168.1.1 or 192.168.0.1 depending on the brand
if this ping gets replies then the connection from the computer to the router is ok
next would be the connection from the router to the cable modem
to see if its connected login to the router
type its address into the address bar of internet explorer user names are generally blank
and the password is usually admin or password
once in the router see the status page to verify you have a connection with a public ip
address and dns servers. Most devices will have a release and renew button to try to re
obtain an ip address. Also most routers offer a command line to test connectivity with
commands from that point. In addition you can check for connectivity to the modem by pinging 192.168.100.1 then you
can use the same address to login to the modem an see its log.
THE FIX (if no router then skip the router steps)
80% of all connection issues can be resolved the same way but the troubleshooting will allow you to document the connection issue for a history.
power cycle the devices in the order the connection comes into the house:
turn off the computer
unplug the power from the router
unplug the power from the cable modem
wait 30 seconds
plug in the power to the cable modem and wait 25 seconds until the lights are all lit solid
plug in the power to the router and wait 20 seconds
power up the computer
test the connection
80% of the time this will fix the issue if not then ask to plug the computer direct into the
cable modem to test router failure.
MORE NOTES
If the computer is directly plugged into the modem and it has an ip address and dns
address and still will not display a web page. Or if the computer is connected to a router and
another computer plugged into the router is online see below:
Reset IE (search forum) and check the host file for bad entries or try an alternate browser. Ask if viruses have been an
issue. Often viruses will edit the TCP/IP stack in windows this can cause connection errors.
Rewriting the TCP/IP stack is different in every OS so search out the process of doing this.
Also ping (ip) –t can be used to test the reliability of the connection between devices
Also tracert can be used in larger networks
Also run ncpa.cpl on any windows system to get to network connections and verify TCP/IP settings of the interface in use, sometimes its just a bad static configuration.

Last edited: