MSBN update 2.2

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

I have a Linksys WRT54G Wireless Router with a MN-730
card.
After the update which installed driver 3.60.7.0 for the
MN-730, the wireless access would go down. I would have
to reset the router in order to get access until the next
time I enabled the MN-730 which of course brought down
the router again.

I rollback the driver to 3.20.26.0, and everything seems
to be working once again.

IBefore I rolled back the driver, I never did receive an
IP address from the DHCP server (client settings HCP
enables, Obtain IP add and DNS server automatically, and
gateway set ). I suspect the problem has something to do
with the DHCP client?

Anyone else have this problem?

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

"soggycyclist" <anonymous@discussions.microsoft.com> wrote in message
news:c4db01c47a35$0a575f10$a501280a@phx.gbl...
> I have a Linksys WRT54G Wireless Router with a MN-730
> card.
> After the update which installed driver 3.60.7.0 for the
> MN-730, the wireless access would go down. I would have
> to reset the router in order to get access until the next
> time I enabled the MN-730 which of course brought down
> the router again.
>
> I rollback the driver to 3.20.26.0, and everything seems
> to be working once again.
>
> IBefore I rolled back the driver, I never did receive an
> IP address from the DHCP server (client settings HCP
> enables, Obtain IP add and DNS server automatically, and
> gateway set ). I suspect the problem has something to do
> with the DHCP client?
>
> Anyone else have this problem?

In addition to what Ms. Bowman suggested...... there may be a problem with
that version of the driver. Several of us including myself have had a
signal loss or drop in signal when using the 3.60.70 version of the driver.
Rolling back the driver to the 3.20.26.0 version restores signal strength.

For now, I suggest using the older driver until this is resolved.