From: "Glenn Meadows" 

Thees,

I've seen this before, on a friends XP machines. Someway, somehow, she had
gotten something downloaded to her machine that totally broke the TCPIP
side of things. The only thing that fixed it, was a total re-install.  I
believe that I was able to do an upgrade install, which kept all the
installed apps in place, but just reinstalled the OS.  That brought it all
back to working again.

I've seen somewhere on the internet, a program that is supposed to repair
broken TCPIP installs.  Might have to be a last resort at this point.

--
Glenn M.


"Thees Peereboom"  wrote in message
news:opsc3fhwkx2hvhrx{at}news.barkto.com...
> Geo,
>
> No dice - no connection with telnet.
>
> Today I changed the setup. Bought a new DSLmodem with router and switch
> built-in. Had to renumber all ws from 192.168.0 to 10.0.0. Everything
> worked right out of the box (well, had to fight the built-in DHCP-settings
> first...), except, right, WS1. In my little network I have two switches, a
> hub and a wireless switch. All four of them now have their own port at the
> ADSL modem/router/switch.
>
> So we can eliminate the firewall or proxy prossibilities, since they're no
> longer there. But the problem remains.
>
> (BTW - I have yet to figure out how put routes in there, so we can do the
> second part of the KISS experiment - will let you know.)
>
> - Thees Peereboom
>
> On Fri, 20 Aug 2004 21:31:47 -0400, Geo.  wrote:
>
> > "Thees Peereboom"  wrote in message
> > news:opsc1cihjt2hvhrx{at}news.barkto.com...
> >
> >>  I can't browse by IP instead of names.
> >
> > So you can ping the gateway but you can't browse by IP. That would
> > suggest some
> > setting on the gateway is not allowing WS1 to browse outbound or that
> > something
> > is wrong with the browser on WS1
> >
> > Next test, type the following from the command prompt on WS1
> >
> > telnet 216.144.1.8 80
> > get
> >
> > then see if you get a response (hit return after the first line, when
> > you type
> > "get" you will not see your typing)
> >
> > If you get a response, then it is likely a browser issue on WS1, if you
> > don't
> > get a response then it is likely something in the proxy server blocking
> > WS1.
> >
> > Geo.
> >
> >
>

--- BBBS/NT v4.01 Flag-5