john <(E-Mail Removed)> wrote in
news:(E-Mail Removed):
> Please Help me.
>
> A couple of weeks ago I bought a WPC11 network card, installed it,
> configured to my exsisting router and all worked fine. One day my son
> used my laptop to surf the net. fter that day I have not been able to
> link with the my network. I tried to reinstall the software and
> hardware and after setting up my configuration settings and pressing
> activate new settings, I get an error saying "Failed to change device
> configuration".
>
> Does anyone have any idea why my configurations cannot be changed?
>
> John
My machine use to be Win2k pro with WPC11 v3 network card and I upgraded
it to XP pro. And that's when all HELL broke loose. It stated with the
169.xxx IP number being assigned to the wired and wireless NIC's -- to
the DAMN utility program for the wireless is not worth 2 cents.
I got the WPC11 running on XP pro and there are somethings I would like
to share on how you get the DAMN thing to work, if anyone is interested.
One thing I'll tell you is forget the WPC11 Utility to setup the card.
One must go to the Device Manager off of Control Panel to install the
driver and configure the card.
For that 169.xxx IP, it means that the TCP/IP stack is hosed and for Win
9'x to Win 2k to rebuild the stack , one deletes Winsock and Winsock2
entries out of the registry, delete everything out the NIC's Property Box
and reboot the machine, which will rebuild the stack. Then one installs
everything back in the NIC's property box.
For an XP machine, you don't touch the Winsock and Winsock2 registry
entries. You can go to the NIC's Property Box and uninstall everything,
but you cannot uninstall TCP/IP. You should not reboot the machine on
each uninstall.
You must follow what's in the link below to reset TCP/IP on an XP
machine.
http://www.petri.co.il/reinstall_tcp_ip_xp.htm
And then one reboots the machine to get everything corrected. And then
you install stuff back again.
If one has deleted the Winsock out of the registry, the TPC\IP must be
reinstalled. I did that and I just took to path of reinstalling the O/S
to correct it. But twice after the install the TCP/IP stack became bad
and I could only get the 169.xxx IP. The method above corrected it each
time and the machine was able to get a valid IP from the router.
You should also be careful of using XP's wireless setup (another piece of
crap) with WEP and WAP. One wrong move and one can turn them on or off,
causing problems with the connection.
HTH
Duane