XP communication work's only when the PC isn't connected

[Guest]

Hi, my problem is as follows: I have a PC and a DSL connection (PPPoE, but the modem take's care of that, so I'm told that my connection acts a LAN-connection). When I run W98 or W2000 on my computer all communication work's fine. I don't have to do anything to make it work, I just open the Explorer and begin to surf. But when I install XP (Proffesional) I get problems, because I can't do any surfing at all. After a while I always get the message " The page can not be displayed"

This always happens when XP makes the whole configuration "by itself". XP never questions anything during the final installation when it tries to determine if and how my PC is connected to the Internet, it justs completes and nothing works
I can ping my own PC, my gateway and the sites I want to surf to, (and I get an answer if the site allows me to get it)
and if I do a tracert I can follow the route and I can see how the "call" goes through the Internet, but I can't see anything in the Explorer besides the error message. I have all the SP:s installed ( because I have them on a CD I have made)
I have tried to configure XP in all the different ways with the Network Configuration Wizard, but nothing works

BUT if i disconnect the network cable during the installation, XP asks at the final installation what kind of connection I have
and I answer LAN-connection with DHCP and dynamic DNS, plug in the network cable, reboot, AND EVERYTHING WORKS FINE AFTER THAT!

If I then, just for a test, use the Network Configuration Wizard (no matter what choice), then everything is spoiled and I have to install XP once again on an empty harddisk without the network cable connected to get the communication to work
I can't reinstall the XP and try too fool it by unplugging the network cable during reinstallation, it doesn't work
Furthermore, if i do a ghost of the PC when it works and then ghost it back again, it doesn't work anymore

In my opinion, it seems that XP makes some kind of missjudgement when it tries to configure my Internet connection
If I don't allow XP to configure it, then I can make it work. But that only lasts as long as XP doesn't make a configuration
If it does, no matter what kind, the communication stops, and I can't make it work unless I make a new installation

So my question is: Does anyone know what my problem depends on

Many, many thanks in advance for any help on this problem that drives me crazy !

 

[john]

Hi, my problem is as follows: I have a PC and a DSL connection (PPPoE,
but the modem take's care of that, so I'm told that my connection acts a
LAN-connection). When I run W98 or W2000 on my computer all
communication work's fine. I don't have to do anything to make it work,
I just open the Explorer and begin to surf. But when I install XP
(Proffesional) I get problems, because I can't do any surfing at all.
After a while I always get the message " The page can not be displayed".

This always happens when XP makes the whole configuration "by itself".
XP never questions anything during the final installation when it tries
to determine if and how my PC is connected to the Internet, it justs
completes and nothing works. I can ping my own PC, my gateway and the
sites I want to surf to, (and I get an answer if the site allows me to
get it), and if I do a tracert I can follow the route and I can see how
the "call" goes through the Internet, but I can't see anything in the
Explorer besides the error message. I have all the SP:s installed (
because I have them on a CD I have made). I have tried to configure XP
in all the different ways with the Network Configuration Wizard, but
nothing works.

BUT if i disconnect the network cable during the installation, XP asks
at the final installation what kind of connection I have, and I answer
LAN-connection with DHCP and dynamic DNS, plug in the network cable,
reboot, AND EVERYTHING WORKS FINE AFTER THAT!!

If I then, just for a test, use the Network Configuration Wizard (no
matter what choice), then everything is spoiled and I have to install XP
once again on an empty harddisk without the network cable connected to
get the communication to work. I can't reinstall the XP and try too fool
it by unplugging the network cable during reinstallation, it doesn't
work. Furthermore, if i do a ghost of the PC when it works and then
ghost it back again, it doesn't work anymore.

In my opinion, it seems that XP makes some kind of missjudgement when it
tries to configure my Internet connection. If I don't allow XP to
configure it, then I can make it work. But that only lasts as long as XP
doesn't make a configuration. If it does, no matter what kind, the
communication stops, and I can't make it work unless I make a new
installation.

So my question is: Does anyone know what my problem depends on?

Many, many thanks in advance for any help on this problem that drives me
crazy !!

Not really sure, other than to suggest that you forget about the wizards
and look at the end result: the connection in Network Connections. Have
you tried installing XP so that your connection works, then taking a note
of all the settings in the network connection, and then installing XP so
that it doesn't work, and then taking a note of all the settings in the
connection, and then playing a game of spot the difference?

 

[Guest]

-----Original Message-----


Not really sure, other than to suggest that you forget about the wizards
and look at the end result: the connection in Network Connections. Have
you tried installing XP so that your connection works, then taking a note
of all the settings in the network connection, and then installing XP so
that it doesn't work, and then taking a note of all the settings in the
connection, and then playing a game of spot the difference?

.

I have never had that problem but I either use the always
on connection (if I am using a router) or a PPoE
connection (needs password and User ID)selection. this
always works fine for me. The only time I have a problem
is if I have the router set to static IP and I have XP
set to DHCP (find IP automatically). I also had a similar
problem when I had my router set to Router instead of
Gateway.