• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4659
  • Last Modified:

Login script not running on wireless clients

Not sure if this is the right channel or not.. please point me in a better direction if you please.

Had this issue for quite a while. Intermittently our login script isn't running on some of our wireless clients. We have 3 Cisco Aironet 1200 AP's. Random wireless clients seem to get affected at random times/days. They aren't moving from different locations, ususally this is at their desk. One day the script runs fine the next it doesn't and so on. It also doesn't seem to matter which AP they are associated with, etc. Nothing looks wrong or has changed client side. All are either Dell TruMobile or Intel PRO. The login scipt isn't a delievered via GPO just a bat file listed in the login script field of their account. Any ideas on what could be wrong would be appreciated. Thank you.
0
RPMTECHNOLOGY
Asked:
RPMTECHNOLOGY
  • 4
  • 4
  • 2
  • +2
1 Solution
 
RPMTECHNOLOGYAuthor Commented:
no one?

Forgot to add, connecting them wired this issue goes away. Something with wireless.
0
 
Adrian DobrotaNetworking EngineerCommented:
RPMTECHNOLOGY .... can you paste here the login script you're talkin' about?
My first impression is that this script should use the netwk. connection, but your wireless clients are taking longer to associate with the AP, and this cause for the script to be unable to access some resource on the LAN.   If that's the case, you can modify the script with an IF clause and check if the cleint is associated with the AP, in fact if you have reply to a ping request.

   But your wireless connection is working fine once the computer finished booting and loading Windows, isn't it?

KronosTM

0
 
RPMTECHNOLOGYAuthor Commented:
Hi Kronos,

I'm was thinking the same thing about the clients taking longer to associate, I can't why.  Upon boot, everything seems fine and working, just intermittently the login script won't fire. The script doesn't fail in the traditional sense but literally doesn't run.

The login script is a simple bat file that maps 4 drives nothing major at all.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Adrian DobrotaNetworking EngineerCommented:
That must be it. The disks are failing to map cause of wireless clients taking longer to associate.
Just place a 5 or 10 seconds delay in the script between first two drives and next two lines that are mapping drives. You'll see that the ones AFTER the delay will be mapped correctly as during that pause the client will manage to associate ...   eh ......  I hope  :)
0
 
Adrian DobrotaNetworking EngineerCommented:
well?  have you run the test?
0
 
RPMTECHNOLOGYAuthor Commented:
I put a delay in the script as suggested but it didn't seem to make a difference. I first tried 5 seconds, then moved to 10 and 20. Nothing helped. The WAP is connected to a Dell 3348 and just a couple days ago I saw some folks with similar issues but it was actually their Dell switch being the problem.

When I get a clear opportunity I am going to move one of my WAPs to a different (HP) switch and see what happens.

I inherited these Dell switches and let me tell you I'm not pleased with their performance or reliability. I heard somewhere that Dell switches are actually made by Foundry which I had always heard good things about in the past.
0
 
Adrian DobrotaNetworking EngineerCommented:
I'm sorry to hear that you still have those problems, unfortunately I have no other idea about how to solve this issue.

maybe disabling wireless zero configuration service and using their own application, never know, maybe Windows's service packs are not up to date, hmmm ... just shots in the dark .... anyway ... afterall, it never hurts to try
0
 
RPMTECHNOLOGYAuthor Commented:
Thanks for your help kronostm.
0
 
ataylor1953Commented:
The problem lies in the fact that the utility controling the WiFi card does not load until the GUI is initialized.  Therefore the network connection to the AP is not made in time to authenticate the user on the domain and run the login script correctly.  Once the utility loads (too late), then any static mappings you had would work, but again, they will also fail to connect after login until you click on them after the WiFi card has connected.
0
 
ataylor1953Commented:
Also, the delay in the server login script will not work, again because the connection is not there till too late.  The only way I can think of is to use a local login script that runs from the 'Programs - Startup' folder and use the Pause or IF statement, perhaps have a ping command to ping the server until a reply comes back, then map the drives.  Bit of a pain for network admins though.
0
 
junkmel50Commented:
Working on a similar problem, Ataylor1953 was correct, another option Around this is that if you are using Windows XP, do not use the proset utility but instead let Windows manage your wireless connection, this should bring up the network in time to prevent a cached login, which should allow your login script to run. However if you use Windows to manage your wireless connection, it  does not support LEAP, So you have to also be setup to do Mac filtering and WEP or PEAP.
0
 
jimmy1264Commented:
Just wanted to throw something in here.....Since deploying wired laptops to desks in my domain I too have this problem. It happends especially when the laptop has been out of the domain for a weekend.......It has to sit in the domain for awhile before it starts seeing the login script again......
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now