Re: can't renew ip address after associating with AP
From: Niklas (niklaso_at_nospamhotmail.com)
Date: 05/07/04
- Next message: Bill McKenzie: "Re: WinXP and 1394 devices"
- Previous message: Alexey Tal: "Re: WHQL signability test error"
- In reply to: Niklas: "can't renew ip address after associating with AP"
- Next in thread: Pavel A.: "Re: can't renew ip address after associating with AP"
- Reply: Pavel A.: "Re: can't renew ip address after associating with AP"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 7 May 2004 17:12:07 +0200
I noticed that if I am connected to my WEP wireless network then run my
client to switch to the WPA network. I can't get a dhcp address. (I don't
get any answer when I broadcast, I can ping and get result)
but if I disable the adapter, enable it again and then run the client to
connect to the WPA network I do get an dhcp address.
So I guess I need to "flush" the adapter when switching from one network to
another?
I captured what the wzc did but couldn't find any oid that seem to do that.
anyone know if I'm on the right track, and what oid I should set?
/Niklas
"Niklas" <niklaso@nospamhotmail.com> wrote in message
news:uZzYho$MEHA.4036@TK2MSFTNGP12.phx.gbl...
> Hi,
> I have run into a strange issue.
> I have created a client that connect my adapter to an access point using
WPA
> (PSK/TKIP)
> After I run it and try to renew the ip address I get an error back "unable
> to contact dhcp"
> First I thought it was something wrong with the EAPOL communication
(either
> the 4-way handshake or the group key handshake), but if I use a static ip
> address I get network connection, so the authentication works.
> I was able to get an address from the DHCP server once, but all other
times
> ipconfig /renew returns "unable to contact your DHCP server. Request has
> timed out."
>
> I have got the same result sometimes, not very often, when connecting to
an
> open wlan and connecting to a wlan with WEP. But with WPA I get it all the
> time.
>
> I used the wzc to check and with that one I do get a dhcp address so I
there
> is nothing wrong with the DHCP server.
>
> these are the oids I set (in order)
> OID_802_11_INFRASTRUCTURE_MODE
> OID_802_11_AUTHENTICATION_MODE
> OID_802_11_WEP_STATUS
> OID_802_11_SSID
> OID_802_11_ADD_KEY
> OID_802_11_ADD_KEY
>
> one idea I have would be if there is any other oid I should run too.
> I captured what the wzc does and it set these oids too (after the last
> add_key):
>
> OID_GEN_NETWORK_LAYER_ADDRESSES
> OID_PNP_ADD_WAKE_UP_PATTERN
> OID_802_3_MULTICAST_LIST
> OID_PNP_ADD_WAKE_UP_PATTERN
>
> (I don't want to set those oids that wzc does without knowing what they
> actually do and if I really need to set them, this might not be an oid
issue
> at all...)
>
> any ideas?
>
> thanks
> /Niklas
>
>
- Next message: Bill McKenzie: "Re: WinXP and 1394 devices"
- Previous message: Alexey Tal: "Re: WHQL signability test error"
- In reply to: Niklas: "can't renew ip address after associating with AP"
- Next in thread: Pavel A.: "Re: can't renew ip address after associating with AP"
- Reply: Pavel A.: "Re: can't renew ip address after associating with AP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|