My PC resolves the hostname to the correct IP but my ping and tracert return error "General Failure." (and tracert immediately gives the error, indicating an issue with my machine). I tried using a fix that I found through google, the command 'netsh winsock reset' but that was to no avail. I almost thought it worked as I could access the site after the restart, but this was while my applications were still loading. I refresh the page and I get the Firefox cannot connect error. This leads me to believe there may be some kind of fault on my configuration somewhere but I have no anti-virus nor firewall application running though I have however used Spybot's Search and Destroy immunizer tool, which includes modification to my HOSTS file. Other than that I don't believe I have any application that could be causing an issue with site access. I am running Windows 7 Ultimate x64 with SP1.

Hi, Firstly, please let me know which destination you tried to ping and tracert? Can you access this website using the IP address? Meanwhile, please try the following to test the issue: 1. Register DNS via command on Windows 7: ipconfig /flushdns ipconfig /registerdns 2. Reset hosts file 3. Test the issue in Clean Boot mode to check whether this is a third party tool issue. Hope this helps. Vincent Wang TechNet Community Support

Hi, Firstly, please let me know which destination you tried to ping and tracert? Can you access this website using the IP address? Meanwhile, please try the following to test the issue: 1. Register DNS via command on Windows 7: ipconfig /flushdns ipconfig /registerdns 2. Reset hosts file 3. Test the issue in Clean Boot mode to check whether this is a third party tool issue. Hope this helps. Vincent Wang TechNet Community Support

Hi there, The site I am trying to access is http://www.roxnet.co.uk/ though I also have had the same trouble with http://ast.ucoz.org/ and http://www.rootgaming.net/ I will try a Clean boot mode some time today and I will also try a hosts file reset now. I've already tried your first suggestion already before resorting to asking online.

Just thought I'd mention that resetting the HOSTS file had no effect.

Not *entirely* sure which step fixed it, I think it may have been something in my hosts file after all, not too sure. Either way, it's fixed now apparently.