• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

wierd inet issue.

Falloutboy

Diamond Member
My sister droped off her laptop today for me to fix (not unusual) but the problem is, atleast I can't figure it out.

the system will conect to a network fine and is able to browse the internal network fine but is not able to pull up any websites. I can ping websites though which was odd. I thought it was some wierd IE quirk and installed firefox and its having the same issue. anyone have any ideas before I just reinstall windows on it?

system is running vista basic
 
I thought DNS also but it resolves the ip when I ping. I ping google and it resolves what the IP is for google so I dunno
 
Originally posted by: Falloutboy
I thought DNS also but it resolves the ip when I ping. I ping google and it resolves what the IP is for google so I dunno

I meant acutally input some DNS server ips in there such as opendns

OpenDNS nameservers are 208.67.222.222 and 208.67.220.220.
 
Reset TCP and Winsock. If you google you'll find netsh.exe instrucitons to do so. Sounds like a messed up Winsock LSP
 
ok i'm able to fix the problem by doing a system restore to go back a few days. I've scanned the computer for virus's and malware found some but don't think they were the issue. after a few days the problem comes back though (fixed it 3 times and she just called again that it won't work). I turned off windows updates to see if that was the problem on a guess last time and it wasn't the problem and it came back again. now I've never used the computer when it happend and I can't reproduce the problem on my own and it always happens after I drop the computer off to my sister. anyone have any ideas?
 
the netsock fix can be found at major geek. you can also try to rebuild the tcp/ip using netshell by doing "netsh int ip reset c:\name_of_log.txt"

Glad you got it working though
 
Back
Top