DHCP fails from MN-500 after SP2 install

After install of latest broadband update a week or more
later I installed SP2.

After post reboot of SP2 install the came up with an IP

Now If I suspend my laptops they will come back up with
an IP. If I shut them down they will fail to get an IP
from the basestation. Althought the wireless signal is
excellent.

I have turned off the firewall and the same is the result.

I uninstalled SP2 and everything works once again. I
reinstalled SP2 and the same lack of DHCP address is the
result. The basestation's log is pasted in below this
post. It looks like there are some strange IPs coming
from these laptops that are being filtered out and
NACKing the DHCP client req. Why has SP2 caused this
behavior?

If I cold boot the mn-500 basestation new DHCP address
will be issued when the basestation is active again.

I am running MAC filtering and SSID is required on a
cisco 340 pcmcia.

2004/09/14 11:28:17 172.16.2.23 logout
2004/09/14 11:30:53 Wireless client associations SUCCESS,
MAC:00409633F116
2004/09/14 11:32:13 Connection attempt to base station
from WAN blocked -- src:<66.36.247.64:3722>
dst:<67.171.38.196:1026>
2004/09/14 11:38:20 Connection attempt to base station
from WAN blocked -- src:<210.74.232.170:7100>
dst:<67.171.38.196:17725>

then after mn-500 cold boot, the address is handed to the
laptop which was nacked above "00409633F116".

1970/01/01 00:00:00 RF Reset...Pass
1970/01/01 00:00:00 Wireless client associations SUCCESS,
MAC:00409633F116
1970/01/01 00:00:03 Address 172.16.2.23 was assigned to
client 1:0x00409633f116
1970/01/01 00:00:09 DHCP Client : Send Discover
1970/01/01 00:00:09 DHCP Client : Receive Offer from
12.242.16.34
1970/01/01 00:00:13 172.16.2.9 login successful
1970/01/01 00:00:14 DHCP Client : Send Request, Request
IP = 67.171.38.196
1970/01/01 00:00:14 DHCP Client : Receive Ack from
12.242.16.34, Lease time = 345594
1970/01/01 00:00:22 172.16.2.9 login successful

For your basestation entries you need to read the following link to
understand what they are really saying (you idea is dead wrong as a FYI
from the little bit you posted).

http://www.microsoft.com/hardware/br..._log_file.mspx

Since it only happens with SP2 installed it is most likely either
Windows is misconfigured after the SP2 install or some software that is
installed on your computer that doesn't like SP2 connecting to the network.

notsoSwift wrote:

> After install of latest broadband update a week or more
> later I installed SP2.
>
> After post reboot of SP2 install the came up with an IP
>
> Now If I suspend my laptops they will come back up with
> an IP. If I shut them down they will fail to get an IP
> from the basestation. Althought the wireless signal is
> excellent.
>
> I have turned off the firewall and the same is the result.
>
> I uninstalled SP2 and everything works once again. I
> reinstalled SP2 and the same lack of DHCP address is the
> result. The basestation's log is pasted in below this
> post. It looks like there are some strange IPs coming
> from these laptops that are being filtered out and
> NACKing the DHCP client req. Why has SP2 caused this
> behavior?
>
> If I cold boot the mn-500 basestation new DHCP address
> will be issued when the basestation is active again.
>
> I am running MAC filtering and SSID is required on a
> cisco 340 pcmcia.
>
> 2004/09/14 11:28:17 172.16.2.23 logout
> 2004/09/14 11:30:53 Wireless client associations SUCCESS,
> MAC:00409633F116
> 2004/09/14 11:32:13 Connection attempt to base station
> from WAN blocked -- src:<66.36.247.64:3722>
> dst:<67.171.38.196:1026>
> 2004/09/14 11:38:20 Connection attempt to base station
> from WAN blocked -- src:<210.74.232.170:7100>
> dst:<67.171.38.196:17725>
>
> then after mn-500 cold boot, the address is handed to the
> laptop which was nacked above "00409633F116".
>
> 1970/01/01 00:00:00 RF Reset...Pass
> 1970/01/01 00:00:00 Wireless client associations SUCCESS,
> MAC:00409633F116
> 1970/01/01 00:00:03 Address 172.16.2.23 was assigned to
> client 1:0x00409633f116
> 1970/01/01 00:00:09 DHCP Client : Send Discover
> 1970/01/01 00:00:09 DHCP Client : Receive Offer from
> 12.242.16.34
> 1970/01/01 00:00:13 172.16.2.9 login successful
> 1970/01/01 00:00:14 DHCP Client : Send Request, Request
> IP = 67.171.38.196
> 1970/01/01 00:00:14 DHCP Client : Receive Ack from
> 12.242.16.34, Lease time = 345594
> 1970/01/01 00:00:22 172.16.2.9 login successful
>

I had similar problem after installing sp2. I spent a
couple of hours on landline with ms support to no avail.
Their final word was that this is a known issue and that
they were working on it.

>-----Original Message-----
>For your basestation entries you need to read the
following link to
>understand what they are really saying (you idea is dead
wrong as a FYI
>from the little bit you posted).
>
>http://www.microsoft.com/hardware/br...etworking/10_c
oncept_log_file.mspx
>
>Since it only happens with SP2 installed it is most
likely either
>Windows is misconfigured after the SP2 install or some
software that is
>installed on your computer that doesn't like SP2
connecting to the network.
>
>notsoSwift wrote:
>
>> After install of latest broadband update a week or more
>> later I installed SP2.
>>
>> After post reboot of SP2 install the came up with an IP
>>
>> Now If I suspend my laptops they will come back up with
>> an IP. If I shut them down they will fail to get an IP
>> from the basestation. Althought the wireless signal is
>> excellent.
>>
>> I have turned off the firewall and the same is the
result.
>>
>> I uninstalled SP2 and everything works once again. I
>> reinstalled SP2 and the same lack of DHCP address is
the
>> result. The basestation's log is pasted in below this
>> post. It looks like there are some strange IPs coming
>> from these laptops that are being filtered out and
>> NACKing the DHCP client req. Why has SP2 caused this
>> behavior?
>>
>> If I cold boot the mn-500 basestation new DHCP address
>> will be issued when the basestation is active again.
>>
>> I am running MAC filtering and SSID is required on a
>> cisco 340 pcmcia.
>>
>> 2004/09/14 11:28:17 172.16.2.23 logout
>> 2004/09/14 11:30:53 Wireless client associations
SUCCESS,
>> MAC:00409633F116
>> 2004/09/14 11:32:13 Connection attempt to base station
>> from WAN blocked -- src:<66.36.247.64:3722>
>> dst:<67.171.38.196:1026>
>> 2004/09/14 11:38:20 Connection attempt to base station
>> from WAN blocked -- src:<210.74.232.170:7100>
>> dst:<67.171.38.196:17725>
>>
>> then after mn-500 cold boot, the address is handed to
the
>> laptop which was nacked above "00409633F116".
>>
>> 1970/01/01 00:00:00 RF Reset...Pass
>> 1970/01/01 00:00:00 Wireless client associations
SUCCESS,
>> MAC:00409633F116
>> 1970/01/01 00:00:03 Address 172.16.2.23 was assigned to
>> client 1:0x00409633f116
>> 1970/01/01 00:00:09 DHCP Client : Send Discover
>> 1970/01/01 00:00:09 DHCP Client : Receive Offer from
>> 12.242.16.34
>> 1970/01/01 00:00:13 172.16.2.9 login successful
>> 1970/01/01 00:00:14 DHCP Client : Send Request, Request
>> IP = 67.171.38.196
>> 1970/01/01 00:00:14 DHCP Client : Receive Ack from
>> 12.242.16.34, Lease time = 345594
>> 1970/01/01 00:00:22 172.16.2.9 login successful
>>
>
>.
>