WinXP SP2 - Can ping DNS server but no web access

pooey · 3 Jun 2011 at 21:41

Hooking up machines in work to the wifi network there, this last machine is in use almost constantly as a controller for a load of embroydery machines so I don't really have a lot of time to mess about with it.

Basically it sees the network, can ping external IPs including DNS server but will not accept that it has an internet connection; browsers, win update etc will not connect.

Things I have tried in order to diagnose/resolve this -

uninstalled all unused/crappy/dodgy software
run anti-virus/spyware/malware progs
cleaned registry
reset tcp/ip stack through net shell
reset winsock catalog through net shell

I'm stuck for what to try next really, reformat is out of the question i'm affraid. Any advice would be marvelous!

Cheers

steven_belfast · 3 Jun 2011 at 23:17

If you are connection via any routers or hubs are you able to access them?
Also have you checked proxy settings?

oldbag · 3 Jun 2011 at 23:20

can you ping names or just IPs?

pooey · 3 Jun 2011 at 23:21

Yea can access the router, reset proxy settings to default.

steven_belfast · 3 Jun 2011 at 23:24

If you are able to access the router its not going to be a network issue,
Have you browsed by ip?

pooey · 3 Jun 2011 at 23:24

oldbag said:
can you ping names or just IPs?

Just IPs, obviously something is up with resolving from the DNS, I've tried a few different servers, all of them ping and all of them pass the DNS test using the netshell GUI.

oldbag · 3 Jun 2011 at 23:25

Try 158.43.240.3 - usually works. Other than that you could be blocking udp 53 outgoing.

pooey · 3 Jun 2011 at 23:26

Browsing by IP does not work, it's why I thought it was a protocol issue, reset tcp/IP brought no joy.

oldbag · 3 Jun 2011 at 23:27

Can you even go to a command prompt and telnet <public IP> 80 ?

steven_belfast · 3 Jun 2011 at 23:28

Can you do a DNS look up from the router?
If this fails its going to be a issue with the route or the line its self.

If its passes then the issue is within the network its self.

pooey · 3 Jun 2011 at 23:31

steven_belfast said:
Can you do a DNS look up from the router?
If this fails its going to be a issue with the route or the line its self.

If its passes then the issue is within the network its self.

Got 8 other machines on the network with no issues. It a local problem on the one machine.

pooey · 3 Jun 2011 at 23:33

oldbag said:
Can you even go to a command prompt and telnet <public IP> 80 ?

I assumed so since it passed all tests under the netshell diagnosis gui, but ill pop in tomorrow and give it a punt.

oldbag · 3 Jun 2011 at 23:35

If the screen clears you have a connection, if not, then you don't. Could be network drivers, could be a firewall/antivirus issue. Could be something in the host file.

pooey · 3 Jun 2011 at 23:57

oldbag said:
If the screen clears you have a connection, if not, then you don't. Could be network drivers, could be a firewall/antivirus issue. Could be something in the host file.

Network drivers are new and working on another machine, uninstalled AV, no firewall. Hosts file will have a gander at and probably wipe tomorrow. Will report back, cheers.

GaryH-21 · 4 Jun 2011 at 02:38

Can you do a traceroute to Google DNS for example:
Start -> Run -> CMD -> tracert 8.8.8.8
and see where it gets too before failing.

Try disabling the firewall temporarily and try browsing again,

pooey · 6 Jun 2011 at 12:56

Telnet on port 80 fails.

pooey · 6 Jun 2011 at 13:58

Should also add - no problems with trace routes and can't browse by IP.

Deleted member 77746 · 6 Jun 2011 at 14:12

Sounds like a hijack of some sort if that's the case. Format may only be the only option

GaryH-21 · 6 Jun 2011 at 15:34

Must be a firewall then

pooey · 6 Jun 2011 at 15:39

GaryH-21 said:
Must be a firewall then

There's no third party firewalls installed and the windows one is off.