Check the cable. Make sure the LEDs are blinking when there is activity.
Install telnet
via the instructions here. Alternatively, download nmap
. Your'e going to use that tool to try to connect to the web-server:
telnet 193.52.1.6 80
(or whatever the IP is, but keep the 80
). If it hangs, check the Windows Firewall and disable it completely. It will complain. Do it anyway. Try again. If it still hangs, it's not the firewall and you should re-enable it. Go to next step.
Next step: Get a packet-sniffer. The best option is to run it on the server if possible. The options for unix include tcpdump
, wireshark
. wireshark
also runs on Windows. Get them to listen for all packets coming from your IP address. If you can't run it on the server, put another host on your network -- the same LAN -- any PC with Windows or Linux will do, and run it there. Tell your PC to connect to this new host (using telnet, nmap, or the browser). If you're not getting anything at all, we have to go down to very basics -- it might be a bad port on the hub/router of your network. Check that connection to, change ports, cables.
If you get it to your LAN's host but not to the server, it's possibly a router or firewall problem. You'll need your packet sniffer further on down the line to know what's going on. Are the packets reaching their destination? Are they getting responses? Does the session start and then stall?
My bet is: bad port on the hub/switch/drop.
On desktop Chrome, deleting the last hour of browsing history works, so long as you've followed the redirect within the last hour.
On Android Chrome, visit chrome://net-internals
, click the downward arrow at the top right corner, and choose 'clear cache'. That is the only solution I found for Chrome on Android.
Best Answer
Browsers these days often times cache redirects. You need to clear your file cache from before your mistaken change. From Stackoverflow