http://en.wikipedia.org in the address bar. After about 25 seconds, I arrive at the proper page. I click the link for the reference desk, and the delay is another 20 seconds or so. I click the link for the computing section, and this time the delay is nearly 30 seconds. The commands had no effect. -- Sapph42 (talk) 01:03, 26 March 2008 (UTC)[reply]
- Tried packet sniffing using things like Wireshark? --antilivedT | C | G 04:22, 26 March 2008 (UTC)[reply]
- Yeah, that's bizzare. Though honestly, in the time you'll spend figuring out what the devil is going on, you could probably have it reimaged or the OS reinstalled and working (hopefully) normally. -- Consumed Crustacean (talk) 04:40, 26 March 2008 (UTC)[reply]
- Is it possible that, for whatever reason, either your router or your PC is configured/provisioned with "bad" DNS server addresses? The scenario I have in mind is that the primary DNS address points to an overloaded, down, or non-existent DNS server, and every DNS lookup has to fall back on the secondary DNS server — after a timeout. Another possibility to consider is that your router or your PC has been subverted to route DNS queries to a rogue DNS server. --71.162.242.38 (talk) 14:05, 26 March 2008 (UTC)[reply]
- No. As mentioned above, the PC gets DNS information from the router via DHCP. And, again, if it was a server-side problem, it would be affecting the other computers on my network. It is not. -- 69.255.155.141 (talk) 17:45, 26 March 2008 (UTC)[reply]
- If it's not affecting other computers on the network, the problem is probably with your PC. Although there's no indication that it's the case, but if your PC is subverted, you cannot be sure that it's using the DNS server it is supposed to, even if the info returned by ipconfig looks normal. For thoroughness, if not anything else, I'd suggest putting a packet sniffer on the network to see what's going on when the PC tries to resolve a name. --71.162.242.38 (talk) 18:09, 26 March 2008 (UTC)[reply]
Try configuring IPv4 on your computer to use OpenDNS. 208.67.222.222 and 208.67.220.200 (if you don't know how to do this comment back). If it's still not working try overwriting your TCP/IP stack- there are tools to do this for XP, don't know about vista. Or see if your %windir%\system32\drivers\etc\HOSTS is massive :D\=< (talk) 15:44, 26 March 2008 (UTC)[reply]
- As mentioned above, I already use OpenDNS. As mentioned above, I am perfectly aware how to change my networking settings. As mentioned above, I am not using Vista. My hosts file defines nothing other than localhost. As for resetting the TCP/IP stack, this is accomplished by the netsh int ip reset <logfile> command, as mentioned above. Negative results. -- 69.255.155.141 (talk) 17:45, 26 March 2008 (UTC)[reply]
- Oh ;_; :D\=< (talk) 01:21, 27 March 2008 (UTC)[reply]