mr_kev said:
I have one machine in our office that cannot browse the internet. I can ping
both ip's and domains so DNS seems good. Also I have tried both our DNS
server and our ISP's DNS server, same result. Mozilla will not connect
either. We recently switched from DSL to cable so I attached this PC to our
old DSL modem and it connects fine. A Netgear FVS114 router was put in with
the cable modem but, but 20 other users are not affected. I even reimaged
this machine and still no connection. Any help would be appreciated.
if you can ping domains, it looks like DNS is ok.
but I usually try browsing with IP addresses
So it looks like you can't connect out.
Can you access email?
you've obviosuly got an ip address. , you're clearly connected
I doubt this is the case if you reimaged. But
I had a similar problem once.
Turned out to be a broken software firewall. Sygate crashed and blocked
all outgoing. It didn't show an icon in the taskbar, but it was there
when I did ctrl-alt-delete
another time I couldn't browse after some broken spyware, I reinstalled
windows and was fine. I don't know if I could ping domains. But now, I
suspect it was perhaps because tcp/ip stack got corrupted.
Maybe try at the command prompt Meddle with netsh reset commands, like
c:\>netsh winsock reset <enter>
i'm not sure if those are dangerous. I think that one is ok. I don't
know exactly what they do. But as i'm sure you're aware, if the worst
comes to the worst, you do a repair or worse, a reinstall, and it's
fine.
besides that netsh command and other netsh commands. There's also
winsockxpfix(win xp only), and lspfix.
they receive a mention in this article here from MS. And they've been
mentioned on newsgroups frequently. So it's not just me -I don't know
how they work and haven't had to use them either.
http://www.microsoft.com/windows/ie/community/columns/ietopten.mspx
If all other users are unaffected, maybe your "router" is blocking you
, it's nto set up right. Or, your cable is faulty.
Or, this is ilkely. your ethernet card is damaged. I once had a prob
where I could access my router but not connect out. was a bad ethernet
card. (at least i think i could access my router). And I did get a
green light on my card.
it makes sens to check ip,dns,stack,sw fw, ethernet card,cable,'home
router',cable,isp
ir more-or-less that order. I guess. But in your case, if only you
are affected, and you reimaged and were fine. i'd say it's ethernet
card or cable between it and 'home router'.
ethernet card, ethernet port. whatever. doesn't make a diff here.
