Advanced Router Troubleshooting

Ensure you have used the correct cabling to connect the ADSL router to your network. Check your manufacturers handbook for details. Typically if your router has a single Ethernet port on the back, you would use a patch (straight-through) cable to connect it to a hub, or a cross-over cable to connect it to a single computer. If however, your ADSL router has a built-in hub on the back instead of a single Ethernet port, you would generally need the opposite type of cable for each of the above situations.
Ensure that any of your network devices (e.g. Hubs, PC's) that are connected directly to the ADSL router internally are set to communicate at the same speed as the ADSL router. Check your manufacturers handbook for details, in the most-case, computers will auto-detect the speed at which to communicate upon bootup but some hubs may ONLY operate at a specific speed (e.g. 100Mbps Half-Duplex), which may make them incompatible with the ADSL router you have purchased. Further instructions can usually be found on the documentation supplied with your equipment.
If your ADSL router has been configured to run NAT make sure you have correctly configured the TCP/IP settings on both the router and any computers you need to gain access through it. In a typical setup where the internal IP address of the NAT ADSL router would be 192.168.0.1 with a subnet mask of 255.255.255.0 you would typically configure your first computer with an IP address of 192.168.0.2 the second with 192.168.0.3 and so on. In this example, each computer would be given a subnet mask of 255.255.255.0, and a gateway address of 192.168.0.1 (i.e. the router). Specifying Demon's DNS servers on each computer would also be preferable. These have IP addresses 158.152.1.58 and 158.152.1.43.
Ensure your computers can communicate with the ADSL router internally. The easiest way to do this is to use the command "ping" (for Windows users, this is usable from the Command Prompt) followed by the internal IP address of the ADSL router. Ping can be found on most Operating Systems today.
Ensure you have configured the router with your connection details, and instructed it to connect, or disconnect and reconnect if already connected.
Reboot your ADSL router, by turning the power off for at least 30 seconds and then turning the power back on.
Ensure your computers do not have any unusual or incorrect proxy server settings contained within the Web Browser (e.g. Internet Explorer) configuration.
Ensure that if your network is using DHCP, that the DHCP server is configured to give out the correct information to your network. Your DHCP server may be a computer on your network, or your new ADSL router. In most versions of Windows, you can use either the command "winipcfg" or "ipconfig" from a Command Prompt, to check the current settings of your computer(s).
Try to find out how far outside your network (if at all) data is getting. There are a number of different ways of doing this, dependant on the Operating System you are using. Using Windows, the easiest way of doing this is by using the traceroute command "tracert". To run this, you will need to open a Command Prompt. This is usually located under the "Programs" menu when you click your start button.

Type "tracert 158.152.1.76" and press [Return].

Normally, you should see a list of addresses begin to appear, with response times listed next to them in milliseconds (ms) as your computer maps a route out onto the Internet to the destination address you specified above. Typically, the first line (or "hop") will be your router, and the second, third, fourth etc. will be the route your Internet traffic takes when leaving your network.

If however you see "timeouts" (asterisks) at any point along the trace, this would indicate a communication problem. If this occurs before the first "hop" outside your network, it would suggest an internal problem, which you would need to look into. If the "timeouts" begin outside your network, you may need to contact us if the problem persists when you retry it.

More Help