upgrading Windows XP to Professional results in no network connection Realtek

[jan lettens]

Just to help some people out here, who might have the same problem.

After upgrading from Windows XP Home to Windows XP Professional, I
didn't have any network (ethernet) connection at all.

Since the card was working perfectly before the upgrade, I immediately
suspected Windows.
IPconfig always showed an IP starting with 169, which is of course not
valid.

I removed the device from the hardware list in the Device Manager,
make Windows plug and play re-detect it. I reinstalled the original
Windows XP compatible driver for the card. I reset the TCP/IP
configuration, WINS, DNS, DHCP settings etc , etc,
All to no avail.

Finally, I found that Windows XP Professional is setting the Ethernet
Card to automatically detect mode and speed and that this didn't work
(at least not on my card from the company Realtek).

When setting this manually to 10Mbps and Full Duplex, the card worked
immediately..

(this configuration can be found My Computer > Properties > Hardware >
DeviceManager > NetworkAdapters. Select your card by right clicking,
then Properties > Advanced > Link Speed and Duplex )

Best regards and hoping this is of help to others.

Jan

 

[Guest]

I've been battling this problem for a week now, although i had a bit
different situation. I have XP pro connected to LAN at work and after
installing SP 2 it started showing limited or no connectivity sign on that
network icon. It couldn't connect to our DHCP server and after trying to
connect for so many attempts it would assign private automatic address to
this connection. And of course with that i couldn't browse either LAN or web.
I read through all the posts here, tried all solutions (restore winsock,
tweaked net settings, removed SP2, clean installed win xp pro sp1, installed
sp2 again) nothing helped. And finally i read this post (i've got Realtek
NIC as well). Applied it and it helped - everything works again!

 

[Hans-Georg Michna]

Jan, Rustrans,

thanks for the reports! The real solution is to download a
corrected driver from the manufacturer. Another (longer-term)
solution could be not to buy the cheapest adapter available.

Hans-Georg