Disable wireless on shutdown - T40

Message

paulct · #1 Post by **paulct** » Mon Dec 12, 2005 1:58 pm

OK, sorry if this is long winded. I'll start with the question first, and the reason second (in case you get bored, or know the answer!)

Is there a way to programatically turn off the wireless card in a T40? (cisco 350 mini). What I am looking to do is have the wireless card be disabled when the machine boots, and then let the user Fn+F5 when they want to do wireless.

I've read a bunch of the posts about slow boot up. Here is our problem, I think. When XP sees a network connection, a lot of things try to kick in to do the normal domain related stuff. When you are at home, or at a hotel, your inside network at work is of course not visible, since you have not VPN'd in yet. Thus many of these things seem to wait, then time out.

I have confirmed this many times, by booting both with and without a network connection (does not matter if wired or wireless), but at least with wired, you can just not plug in the cable until after boot, and you are ready to connect. If no connection, boot up is lightening fast (or as fast as XP can be!). With a network detected, it can range from 2 to 7 minutes after entering your windows credentials.

So, the ideal solution for me would be a way for the laptop to always turn on with wireless disabled, even if it was enabled the last time you shut down.

We have a tool that lets us execute a script at shutdown (Desktop Authority), so if there was a command to turn it off, that would be great.

We do not run access connections and wireless zero config is on, XP SP2

Thanks,

Paul

#2 Post by **jdhurst** » Mon Dec 12, 2005 2:29 pm

My answer won't suit you, but here goes anyway.

With Access Connections, I have a Default Wired Profile that is alway active and my Home Wireless Profile that is always active. All other profiles are unchecked and do not get in the way.

If I plug in a wire and then start, it will look for an existing MAC address and connect to that, or create a new MAC address and connect to that. Wireless does not try to start (because of my settings).

If I do not plug in a wire and then start, it will look for my home network and it takes 30 seconds or so to time out but I don't find that too bad.

I also keep my machine off domain. Even for clients I have done that, and provided a script to connect resources when in the office. Access Connections performs well on those machines also.
... JD Hurst

paulct · #3 Post by **paulct** » Mon Dec 12, 2005 2:45 pm

Thanks JD, but you are right, its not the answer for me. We already have hundreds of these deployed (750+) and the idea of trying to reinstall access connections, make those settings etc just won't fly!

We don't let our users log in without domain credentials, as they get way too confused trying to understand "local" login. Also our auditors are pretty tough, so users only have a domain acct, and are not administrators of their machines.

But thanks for the tip, maybe I'll try it on mine, and then consider it for our next roll out..

Paul

#4 Post by **GomJabbar** » Mon Dec 12, 2005 6:01 pm

One thing that seems to work for me regarding boot times and wireless.

While I am at home, I am using Access Connections and have a home wireless profile set up. I have the wireless adapter on all the time.

While I am away from home (for some weeks) I keep the wireless radio turned off, since I almost never use it. I found this was causing the boot up to be delayed somewhat. What I did was set the Wireless Zero Configuration service to Automatic and Started. Now even though the wireless radio is still left off, the boot up time is not delayed as before.

I think there is a bug in Access Connections where some part of the program can't tell that the wireless radio is off, and it keeps trying to make a connection until it times out. Wireless Zero Configuration doesn't seem to have this bug.

BTW, I still have Access Connections installed and running. Although I still use Access Connections I can't close the latest version like I could the previous ones.

#5 Post by **jdhurst** » Mon Dec 12, 2005 6:07 pm

@paulct - Just a point of clarification - The client where I do not have the laptops on the domain are also not administrative users. I connect them with a local batch file that does not compromise security. As normal users, they cannot enable / disable the wireless connectoid. I am busy doing another rollout which is Access Connections works in my case. The problem with leaving both NIC actives is that I have seen the laptop get confused over which signal to obey. ... JD Hurst

paulct · #6 Post by **paulct** » Mon Dec 12, 2005 6:29 pm

Thanks JD.

Interestingly, which confirms part of my theory:

We have some users that use something called Checkpoint Secure Domain Logon, which allows you to both authenticate to windows and set up your VPN tunnel at the same time (it pops up right after the GINA, eg windows login). If you have a valid wireless connection, then the boot up time is reasonable, as Windows can find all the "things" it is looking for.

The problem with secure domain login is that it does not work in most hotspots, even if they are free. Usually they force you to an internal home page, where you register, and then you get full net access. (we find this in many hotels that offer free wi-fi). Thus the secure login fails, as you have not been opened up to the full internet yet.

Works fine from home connections of course.

Paul

#7 Post by **jdhurst** » Mon Dec 12, 2005 8:59 pm

Paul,
I went a different way with the client I am talking about. We use Juniper Netscreen for the VPN access and security and the client software has been set for manual connection. The users are not domain connected as I noted. Then there is a batch file to connect domain resources.

The users have gotten used to the following tap-dance:
Start the machine and log on locally. If in the office, forget VPN and connect. Work normally. If remote, connect to VPN and work remotely. Only connect domain resources remotely over a very fast connection.

There are so many variables (especially remotely) that I made the steps manual and independent. The users have adjusted well.
... JD Hurst

paulct · #8 Post by **paulct** » Tue Dec 13, 2005 7:55 am

Sounds like you've got a good handle on it. I may fool around with some of the new drivers/app,ications on the new laptops we are getting now and see if things have changed.

For us, we have drank the Microsoft Kool Aid and we must be on the domain most of the time, we are using all the features of active directory to drive SMS installs, web site access, inheritance to SQL server, group policies, yada yada.

But thanks for your help!

Paul

beeblebrox · #9 Post by **beeblebrox** » Tue Dec 13, 2005 4:11 pm

There is the option "Close down all wireless connections when logging off" in Access Connection (V4.0)
That's what I use. Waiting 30 seconds for the laptop to decide on a network would drive me nuts after while.

Hope that helps...

Disable wireless on shutdown - T40

Disable wireless on shutdown - T40

Who is online