MN-730 DHCP failing

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Dear Tim,

A couple questions:

(1) does the "strange IP" begin 169.x.x.x? This is an IP
internally assigned by Windows when it cannot reach an
outside network. Or, is it stranger?
(2) do you know the DNS servers of your ISP?
If this worked previously without desginating them, this
shouldn't matter, but it doens't hurt to specify them.

My quick thought is to assign the PCI a static IP within
the IP range of your router. This WILL work, although it
is not using the DHCP server of the router.


>-----Original Message-----
>I'm trying to setup a Microsoft 802.11g PCI wireless
>network card (model MN-730) at home but it seems to be
>stuck on a strange IP address.
>
>I got the card installed and running on an older XP
>machine and connected to my Buffalo 54g router. I did a
>Windows Update (the machine hadn't been on the internet
>for a while, so it was really behind in updates) and
>installed eTrust anti-virus. After which, I couldn't
>connect to the internet anymore. The machine can see my
>home network, but gets a DNS error when trying to go
>outside.
>
>It looks like the adapter does not want to pick up the
>DHCP address. Ipconfig lists an IP address out of my
>network range and a different subnet mask. Under the
>properties of the network card, it is set to DHCP. I
>cannot find in any of the settings a reference to this
>different IP address. There is no network bridge
>installed either. My other machine can connect to the
>router wirelessly, so I know that's not the cause.
>
>Thinking that maybe eTrust screwed it up, I uninstalled
>it, the card and the MS software; then reinstalled and I
>still get the same problem.
>
>I have also disabled WEP on the router (for the time
>being) to make sure that wasn't the problem. I can
still
>connect with my Buffalo card, so I know the router works
>fine without WEP.
>
>Thanks,
>tim
>
>
>
>.
>