HI All We are running our wireless using FR to authenticate against LDAP. A user can login on a laptop, no problem, but when he then goes to a Dell laptop which uses a Dell Connection Manager program, it fails. The odd thing is is that in both cases there is an Access-Accept packet going out, except for the Dell, it does not assign a vlan (which is probably why it's failing). Since it's the same userID loggin in, I'm not sure why the vlan is not being passed. The only thing I can see is that the username field in the Access-Request is preceeded by "\\" in the case of the Dell, and not so in the case of the working laptop. Here's the Access-Request from the one that works: rad_recv: Access-Request packet from host 172.17.0.1:20001, id=166, length=144 NAS-Port-Id = "2049/1" Calling-Station-Id = "00-15-E9-D9-94-85" Called-Station-Id = "00-15-E8-E0-E6-00:Wireless@UNB" Service-Type = Framed-User EAP-Message = 0x02010008016d6461 User-Name = "mda" NAS-Port = 4596 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "nortel" NAS-IP-Address = 172.17.0.1 And here is the Access-Request from the one that does not work (notice the username field): rad_recv: Access-Request packet from host 172.17.0.1:20001, id=161, length=146 NAS-Port-Id = "2049/1" Calling-Station-Id = "00-13-02-77-97-CB" Called-Station-Id = "00-15-E8-E0-E6-00:Wireless@UNB" Service-Type = Framed-User EAP-Message = 0x02010009015c6d6461 User-Name = "\\mda" NAS-Port = 4593 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "nortel" NAS-IP-Address = 172.17.0.1 In both cases there is an access-accept, but vlan is only returned in the case of the first one. Any ideas on a workaround? Thanks for any advice. Cheers Matt Ashfield mda@unb.ca