Wireless Pre Logon

[JezR]

Has anybody had experiance with the new RM Mobile One and wireless??

 

I've been given* some brend new Mobile one's and cannot get wireless login to work at all.

They use the Intel 4965AGN wireless chipset.

 

As supplied by RM they use windows wireless config tool. This will not find any networks until after a refresh network list has been requested. ie after login.

 

I've tried installing the Intel Proset software, with Single Sign on and Pre Login, but that has exactly the same problem.

 

Once one person has logged in and out, both methods work fine.

 

*Our Federation partner school is closing on this summer, so they ordered these laptops from RM and asked for them to be delivered to us. I knew nothing about this until RM emailed asking when we wanted them delivered!

 

Jez

[PRicho]

Not had any experience with an RM network but this can be done via GPO - Computer config - Administrative Templates - System/Logon - "Always wait for network at computer startup and logon"

[JezR]

Hi,

 

I'm using a vanila Windows network.

 

I've set Wait for network, and increased the amount of time it will wait up to 60 seconds.

Still no Joy.

[mattx]

Turn OFF the proset management and let windows manage the wireless aspect - trust me.

[JezR]

Hi Mattx

 

I,ve tried the windows wireless zero config.

 

I've set the GPO for wait for network.

 

When the machine starts WIFI led comes on.

 

When I login locally it cannot find any wireless network, and when I open the wireless network connection dialogue there are no networks shown.

If I then Refresh the network list it immediatley finds the network and logs on.

 

When using the Proset pre logon I get the proset dialogue trying to access the network, but exactly the same problem.

 

I'm using the latest (12.4.0.21) Intel drivers.

 

Any (sensible) suggestions gratefully received, I've got 32 of these doorstops.

 

Jez

[alextreadwell]

don't know about this exact card but the intel pro set software has an extra bit if you reinstall the driver software and choose custom install theres a utility you can create custom wireless profiles and you can set it to make sure wireless is enabled renew ipadress and check for domain as it does the windows login I have not used it on the rm ones but I have used it on Dells using Intel chipsets and it works brill

[mattx]

I would un-install everything regarding the Proset mangement side - just keep the drivers - [ make sure you have the latest ] - then on the drivers I would turn up to max the Roaming setting and power setting.

Logon to the domain [ I take it you are logging on to a domain ] via a normal ethernet cable, join the wireless network. Then try again.

Just out of interest, what wireless APs are you using ?

[JezR]

Hi Mattx,

 

I'll give that a go.

 

I'm using Netgear WG102's that have been flashed to work with the Netgear WFS709TP managed controller.

 

It works fine with our Acer, Toshiba and Dell laptops, PDA's etc. It's just these RM laptops.

 

Jez

Edited May 21, 2009 by JezR
spelling

[JezR]

Hi Gibbo,

 

Yes, I tried that as well, changed it to decimal 60.

It just delayed the startup by 60 seconds, nothing else.

 

Jez

[spc-rocket]

Hi Gibbo,

 

Yes, I tried that as well, changed it to decimal 60.

It just delayed the startup by 60 seconds, nothing else.

 

Jez

 

Hi,

 

Try to disable the N standard on the advanced properties of the wireless NIC card and make sure that the Power Save mode is turned off. Also set it to CAM (Constant Awake Mode). Change the wireless mode to b and g.

 

Also worth (for testing at least) to turn of throughput enhancements as well Fat channel intorelant.

 

HTH,

 

Ash.

[JezR]

Right then,

 

Just unpacked another brand new one, NO Proset software installed.

 

 

Updated driver to the latest version,

N Mode disabled.

Power Max.

Roaming Max.

Throughput enhancment disabled.

Transmit Max.

Wireless Mode b&g.

 

Allow computer to turn off NO.

 

connect to the wireless network - OK

 

Join the domain (using LAN cable)

Gpupdate /force to ensure the wait for network GPO is applied.

 

regedit to apply network startup timeout set to 60 seconds.

 

remove LAN cable.

Reboot

 

Try to logon to the domain - not available.

logon locally - no network available.

wait approx 60 seconds and it finds and joins the wireless network.

 

When I look in the event log it shows that the wireless sevice starts after Netlogon has failed.

 

Suggestions

 

Jez

[alextreadwell]

Try as i posted above uninstall and reinstall driver choose custom add admin tools and pre logon bit make a profile on the laptop export it and imoprt it on to other laptops I have just downloaded the software and its all there in the drivers i had same problems took me a month to find why the wouldn't logon did above and havn't had a problem since logged on every day now for over a year

[JezR]

Hi Alex,

 

I've done as you suggested (on a different laptop), and have exactly the same problem. The event log shows netlogon failing before the wireless service starts.

[plexer]

All I can say is that in my experience domain logon using windows as is can be very hit and miss and drove me mad.

 

We use the odessey access client and domain logon of wireless laptops works a treat.

 

Ben

[spc-rocket]

All I can say is that in my experience domain logon using windows as is can be very hit and miss and drove me mad.

 

We use the odessey access client and domain logon of wireless laptops works a treat.

 

Ben

 

Yes this would work and odessey client is very flexible but its not free which is a pain. The normal windows wireless client had worked for us all most all the time.

 

Ash.

[User3204]

Do you hide the SSID on the Access Points ? There is a tick box to say "connect even if SSID is not being broadcast".

[plexer]

True but had I bought the odessey client back when we first had wireless laptops it would have paid for itself after all the time I've spent trying to get windows to work properly on its own.

 

Ben

[JezR]

No I'm not hiding the SSID.

 

I've been experimenting with BIOS and got some results.

 

The BIOS controlls the Wireless card, options as follows

Always on

Always off

Controlled by LAN cable

Controlled by button.

 

When set to Always on or Controlled by LAN cable, I have problems.

 

Using Controlled by button, and manually activating wireless as soon as the BIOS splashscreen goes, I can log on to the domain no probem. The event log shows that the wireless service is the first entry into the log at startup.

 

Jez