"Brian" <(E-Mail Removed)> wrote in
news:1sZtb.114448$(E-Mail Removed):
> I have an SMC Barricade 802.11g wireless router and pcmcia card for my
> notebook. Something is wrong. It comes on and off. The desktop is hard
> wired in to the router and is perfect, so it's a wireless problem
> only.
>
> I use WinXP Pro. I am having DHCP / IP problems with the wireless on
> the notebook. For instance, windows says I have an EXCELLENT (54Mbps)
> signal, says I am CONNECTED. The network card LINK light is on SOLID.
> So the notebook is getting and seeing the wireless signal fine. It
> even identifies the wireless SSID, encryption status and channel. Yet,
> I can not get online. I am only getting a 169.*.*.* IP address.
Your machine is getting some kind of timeout on DHCP when trying to
obtain an IP. The MS O/S will assign a 169.xxx default IP to the TCP/IP
when it cannot get an IP from a DHCP server.
>
> I've done ipconfig /release and /renew, but when I try, it says DHCP
> server unavailable/unreachable/etc. I can get it to work sometimes if
> I uninstall the network card, reinstall it, it MIGHT fix it
> temporarily (Hour maybe) and get the proper 192.* ip.
It may be that you're having some kind of NIC configuration issue with
two drivers interfering with each other. Or possible problems with more
than one wireless network the card is seeing in your area.
For instance it
> was just working, I shut the notebook and put it in standby, and it is
> back to the 169 ip and wont go back. Reboots do nothing.
>
> There must be something key here that I am missing. I get this problem
> regardless if I use WEP or no encryption services, etc.
You should disable XP's Wireless Zero Configuration Service on the
machine.
You should not use XP's Network Wizard.
>
> Someone please help me out here! This is killing my new notebook fun
> (Dell)!
>
I just switched to XP Pro and wireless and made two posts within the last
two weeks or so on how to come around the 169.xxx on an XP machine
without reinstalling the driver in this NG.
It also could be the router's DHCP is defective too, but I lean towards
card mis-configuration or interference that is leading to the DHCP
timeout and the assigning of the 169.xxx IP to the NIC by the O/S.
HTH
Duane