On Sun, 14 Dec 2003 23:02:40 -0500, Lewis G Rosenthal wrote:
 

Not sure exactly which interface we're discussing, here. If you are referring to establishing an association with an access point, then this is done as soon as the driver is loaded, even before a higher level protocol (TCP, UDP, NetBIOS, IPX, etc.) is bound to the card, AFAIK.
   

WSeB only makes a logon connection via NetBIOS, right?

 

A wireless connection is not usually established at computer user logon time but once the logon screen has passed. Does anyone have a way to get around this issue on XP?


     

Ah... I think I have a better idea here. The XP connection manager may block access until permissions are established. No matter. Don't use it. Use a connection manager for the card (i.e., the one provided by the manufacturer) or for ThinkPads (and probably others), try the IBM Access Connections utility. I've had nothing but problems dealing with the supposedly-more-user-friendly XP connection manager. As with most software from Redmond, they shipped it before they started thinking out-of-the-box (the shipping box, that is!).
   

Already done, but those are loaded AFTER the XP logon prompt....If I can get the wireless connection software loaded BEFORE the logon prompt appears then it should be ok. I'm proposing a system consisting of WSeB, OS2/eCS clients and XP clients all wireless (most of the wireless clients will be done with bridging hardware to make it platform neutral BUT there are some laptops out there (like mine and my bosses) which are XP.

Ideas?

 

Thanks Leon