Stumped: desktop won't connect to Net via router / DSL while does via just DSL (but other PCs have

25 Nov 2006 12:05 AM

trippknightly

Well, I tried to make the subject line clear but this bears a little
explanation.

Have a WinXP desktop (HP Pavilion 8576C, kind of dated, and it's just
basic XP though SP2). It connects via DSL no problem. But when I
introduce a router, it fails.

Plus, what I think must be telling is that I'm able to use two
different models of laptop (a Toshiba & Dell) w/ XP Professional to
'net connect via the router (wired) w/o incident. They also work
wirelessly no sweat when I choose to do that too.

I've checked pretty much every parameter I can think of in TCP/IP
properties and LAN connection properties on the desktop to be alike to
those on the two laptops that work, but maybe I've overlooked something
not obvious.

Is this not uncommon? Could I just chalk it up to the vagaries of XP
(standard) or the particular 10/100 NIC I've got on the desktop?

Just seems weird that the desktop can connect to the net via ethernet &
DSL modem and yet introduce a router and it fails where others
succeed...

I realize it's probably not a wealth of info provided, but any
thoughts?

THANKS.

25 Nov 2006 4:00 AM

Jim

<trippknigh***@hotmail.com> wrote in message
Show quoteHide quote

news:1164413120.641224.294880@14g2000cws.googlegroups.com...
> Well, I tried to make the subject line clear but this bears a little
> explanation.
>
> Have a WinXP desktop (HP Pavilion 8576C, kind of dated, and it's just
> basic XP though SP2). It connects via DSL no problem. But when I
> introduce a router, it fails.
>
> Plus, what I think must be telling is that I'm able to use two
> different models of laptop (a Toshiba & Dell) w/ XP Professional to
> 'net connect via the router (wired) w/o incident. They also work
> wirelessly no sweat when I choose to do that too.
>
> I've checked pretty much every parameter I can think of in TCP/IP
> properties and LAN connection properties on the desktop to be alike to
> those on the two laptops that work, but maybe I've overlooked something
> not obvious.
>
> Is this not uncommon? Could I just chalk it up to the vagaries of XP
> (standard) or the particular 10/100 NIC I've got on the desktop?
>
> Just seems weird that the desktop can connect to the net via ethernet &
> DSL modem and yet introduce a router and it fails where others
> succeed...
>
> I realize it's probably not a wealth of info provided, but any
> thoughts?
>
> THANKS.
>

You don't have your router configured correctly (if at all).
Also, the firewalls need to pass ICMP packets.

Jim

25 Nov 2006 4:54 AM

trippknightly

Jim wrote:
Show quoteHide quote

> <trippknigh***@hotmail.com> wrote in message
> news:1164413120.641224.294880@14g2000cws.googlegroups.com...
> > Well, I tried to make the subject line clear but this bears a little
> > explanation.
> >
> > Have a WinXP desktop (HP Pavilion 8576C, kind of dated, and it's just
> > basic XP though SP2). It connects via DSL no problem. But when I
> > introduce a router, it fails.
> >
> > Plus, what I think must be telling is that I'm able to use two
> > different models of laptop (a Toshiba & Dell) w/ XP Professional to
> > 'net connect via the router (wired) w/o incident. They also work
> > wirelessly no sweat when I choose to do that too.
> >
> > I've checked pretty much every parameter I can think of in TCP/IP
> > properties and LAN connection properties on the desktop to be alike to
> > those on the two laptops that work, but maybe I've overlooked something
> > not obvious.
> >
> > Is this not uncommon? Could I just chalk it up to the vagaries of XP
> > (standard) or the particular 10/100 NIC I've got on the desktop?
> >
> > Just seems weird that the desktop can connect to the net via ethernet &
> > DSL modem and yet introduce a router and it fails where others
> > succeed...
> >
> > I realize it's probably not a wealth of info provided, but any
> > thoughts?
> >
> > THANKS.
> >
> You don't have your router configured correctly (if at all).
> Also, the firewalls need to pass ICMP packets.
>
> Jim

Thanks Jim. Your response both directly and indirectly caused a fix -
I spent hours on this yesterday and your brief $.02 led to a solve in
15 min! Here's an update for posterity. I don't doubt that it could
have been the router, but I *think* it turns out to be more general
networking configuration than router per se. For posterity, I did 3
things which together or some pieces comprised the fix. In order, I
turned off firewall, enabled RPC service and enabled DHCP Client
service. It was not until DHCP that I get IPCONFIG /RENEW command to
work correctly, so it seems like DHCP Client was necessary though
perhaps not sufficient...