Can ping, but not browse on xp client pcs

Hello -
I have an internal adsl modem and a wifi router to two client
computers. All works fine except can't browse with either IEx or
Firefox on the clients. Ping works fine with dotted quads and URLS.

The really wierd part is that I can access one domain (Google.co.nz),
but others just go into a never-ending progress bar freeze. This is
only happening on the 2 clients with WiFi cards.

They worked OK with the old combo modem/router.
I can also ftp out with one client OK
I am using dhcp enabled on the router and auto IP address settings

"compac" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hello -
> I have an internal adsl modem and a wifi router to two client
> computers. All works fine except can't browse with either IEx or
> Firefox on the clients. Ping works fine with dotted quads and URLS.
>
> The really wierd part is that I can access one domain (Google.co.nz),
> but others just go into a never-ending progress bar freeze. This is
> only happening on the 2 clients with WiFi cards.
>
> They worked OK with the old combo modem/router.
> I can also ftp out with one client OK
> I am using dhcp enabled on the router and auto IP address settings
>

I had similar problems... try the IEx settings making sure you have nothing
selected on the Connection / LAN Settings... no "Automatic" and no "Proxy".

Jurie.

Tried that thanks Jurie, still not working...

compac wrote:
> Tried that thanks Jurie, still not working...

If you run LSP-Fix do you see any references to new.net? If so I'd
remove it, that fixed a similar problem I had on one computer.

http://www.cexx.org/lspfix.htm

http://www.spyany.com/program/articl...NewDotNet.html
http://www.cexx.org/newnet.htm

Mike

Hi Mike c- thanks for the idea.

ALL the clients are doing this, so it is setting problem somewhere I
think. I can't imagine that a bug (new.net?) would have bitten all the
computers simultaneously at the same time I fitted a new router setup?
Ran LSP-Fix on the Host, no results

OK Problem solved -
Ran WinsockxpFix.exe on the Host - looks like one of the WAP installs
wrecked the Host winsock registry settings - Huge relief!!