Win2k3 DHCP Wireless Clients not getting address?

Hello everyone,

I have a very bizzare problem occuring with my wireless clients since
upgrading to Windows 2003. The scenario seems to be like so:

User A comes into the office from home, where he was using his own wireless
network. When booting and connecting to our WAP's here in the office, the
Win2k3 dhcp server gives him a NACK response, because his wireless device
tried to obtain the last address it used, which does not match the
subnet/address schema used in the office. Any attempts to /release or /renew
these adapters fail with the wireless connection saying Limited or no
connectivity. This happens for every wireless client we have in the office
(about 8 of them currently).

Now here's the weird part. If any one of these wireless clients plugs up
via ethernet to the network, the wireless client gets it's dhcp address just
fine. I've confirmed that the DHCP requests are being relayed by the WAP's
to the DHCP server, because it's giving back NACK responses which show the
last IP they used at home, or elsewhere. Once the wireless client has
obtained it's address, you can remove the ethernet cable, and /release and
/renew the wireless connection all day long.

Only one of the wireless clients is a member of the office domain, however
this seems to effect the domain wireless client as well. It shouldn't matter
because I'm just using standard WEP on the access points, and no IAS services
for authentication. Wide open except WEP, basically.

My scope setup is VERY simple. It's serving 192.168.0.2 -> 192.168.0.254
with your standard domain suffix, dns servers and a boot server address.

Has anyone else run into this before? It's driving me up the wall! At
first I thought it might just be the SP2 XP clients, however it's occuring on
3 Windows 2k Pro systems as well.

Any help or direction would be greatly appreciated, so thanks in advance,

Brian D'Arcy