Joe152
02-25-02, 02:02 PM
The basic problem, I can't get my WinXP machine to tell my router to connect to my DSL.
Setup: PPPoE Verizon ADSL connection to the Internet.
Linksys 1 port router connected to a 5 port 3-Com hub.
WinXP box, Win98 box and 2 Win95 boxes on my hub.
All four of these PC's can successfuly see the router and connect
out to the Internet. However, my XP PC has a frustrating
limitation of apparently not being able to initiate the Internet
connection. It will only reach the Net once another PC on the
LAN has already established the Internet connection.
If the XP box is the first PC on the LAN attempting to hit the
Internet it will not find a connection out. When I pull up
my router's config page from the XP PC I can see that, for some
reason, my XP PC is unable to coax the router into making the PPPoE
connection. All attempts at hitting a URL on the XP PC simply
come back with a "server not found" error and my router stays
in a disconnected state.
It can't be a setting on my router because all 3 of the other PC's
are able, upon pulling up a browser and hitting a URL, to get the
router to make the PPPoE connection and hit the Net. Once this
happens, then the XP machine has no problem connecting to the Net.
Also, if the XP PC is going to be the first PC attempting to connect
to the Net, I thought of just pulling up my routers config page and
manually making the DSL connection myself. I've done that and
the router reports that it is connected. However, the XP box still
won't see the Internet unless I then reboot it with the router in
the connected state.
On the XP machine I believe I've got all my network settings
set up correctly because the XP machine can communicate with the
router, the other PC's on the network, and the internet. It just
can't initiate the connection to the internet.
Since I'm on the XP machine most of the time I'd really like
to find a way to get this PC to connect to my DSL on the first
attempt instead of continually opening up my router's config page,
making the manual connection and then rebooting the PC.
Odd but true, when this PC (HP Pavilion 6736) was running Windows ME
it had the exact same problem.
Joe
Setup: PPPoE Verizon ADSL connection to the Internet.
Linksys 1 port router connected to a 5 port 3-Com hub.
WinXP box, Win98 box and 2 Win95 boxes on my hub.
All four of these PC's can successfuly see the router and connect
out to the Internet. However, my XP PC has a frustrating
limitation of apparently not being able to initiate the Internet
connection. It will only reach the Net once another PC on the
LAN has already established the Internet connection.
If the XP box is the first PC on the LAN attempting to hit the
Internet it will not find a connection out. When I pull up
my router's config page from the XP PC I can see that, for some
reason, my XP PC is unable to coax the router into making the PPPoE
connection. All attempts at hitting a URL on the XP PC simply
come back with a "server not found" error and my router stays
in a disconnected state.
It can't be a setting on my router because all 3 of the other PC's
are able, upon pulling up a browser and hitting a URL, to get the
router to make the PPPoE connection and hit the Net. Once this
happens, then the XP machine has no problem connecting to the Net.
Also, if the XP PC is going to be the first PC attempting to connect
to the Net, I thought of just pulling up my routers config page and
manually making the DSL connection myself. I've done that and
the router reports that it is connected. However, the XP box still
won't see the Internet unless I then reboot it with the router in
the connected state.
On the XP machine I believe I've got all my network settings
set up correctly because the XP machine can communicate with the
router, the other PC's on the network, and the internet. It just
can't initiate the connection to the internet.
Since I'm on the XP machine most of the time I'd really like
to find a way to get this PC to connect to my DSL on the first
attempt instead of continually opening up my router's config page,
making the manual connection and then rebooting the PC.
Odd but true, when this PC (HP Pavilion 6736) was running Windows ME
it had the exact same problem.
Joe