wireless problem

at work we impletemented a new wireless network (aruba)

it is setup to automaticaly authenticate and connect which it does when you boot up a laptop that is not docked or not wired and then go to wireless. But if it is wired or docked (wired) then login, then undock and turn on wireless on it tries to authenticate but fails and locks out the AD account, it sends the netbios name to our wireless system and prevents it from authenticating.when you go from a turned off laptop not "wired" to wireless it sends the fqdn to our wireless system and permits the laptop to authenticate fine

any suggestions out there????


Submitted via EggHeadCafe - Software Developer Portal of Choice
Dr. Dotnetsky's Cool .NET Tips & Tricks #3
http://www.eggheadcafe.com/tutorials...-cool-net.aspx

Hi
From the perspective of the Client computer you can try to set the Metrics
of the Wireless card to be preferred over the wire.
http://www.ezlan.net/metrics.html
Otherwise, it a server/Aruba problem and has to be dealt with accordingly.
Jack (MS, MVP-Networking).

"Stephane Landry" wrote in message
news:(E-Mail Removed)...
> at work we impletemented a new wireless network (aruba)
>
> it is setup to automaticaly authenticate and connect which it does when
> you boot up a laptop that is not docked or not wired and then go to
> wireless. But if it is wired or docked (wired) then login, then undock and
> turn on wireless on it tries to authenticate but fails and locks out the
> AD account, it sends the netbios name to our wireless system and prevents
> it from authenticating.when you go from a turned off laptop not "wired" to
> wireless it sends the fqdn to our wireless system and permits the laptop
> to authenticate fine
>
> any suggestions out there????
>
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Dr. Dotnetsky's Cool .NET Tips & Tricks #3
> http://www.eggheadcafe.com/tutorials...-cool-net.aspx