Microsoft wireless logins require access to local machines before domain logins.

[pashby]

I administer a school network using Windows 2000 Pro and a Windows 2000 server as the domain controller.

We have always used wired connections and have set up the network so that users MUST logon to the domain before they can access the local machine resources. In most cases these resources are very limited in any case since most of the SW is available through the network.

When I decided to increase the number of machines in our Library I decided to use wireless networking since we would need more hubs and wiring etc. All works well and the machines connect properly with all resources provided an administrator first logs onto the local machine so that the Belkin802.11g network adapter can be recognized/installed - no messages are produced during the logon sequence. The administrator logs off and the machine is now available for domain connection for other users.

This is a pain because after each restart of the machine an administrator must logon locally again.

Is there anyone who can help with the problem of having to login to a the local machine first to be able to make a wireless connection to the domain - I would be VERY grateful.

Regards Peter

[Greenstead]

I don't know Belkin. Is the wireless utility installed for all users ?

[pashby]

Hello

The Belkin card is a wireless pci card.

It runs perfectly with a local login.

Any user can login locally and then use the wireless interface.

But the domain is unavailable unless the user first logs in locally.

Peter
:confused:

[Greenstead]

I guess I am not familiar with the restrictions you have on the PC before a local login. I would expect that the PC as soon as booted would have the wireless connection enabled. For example I would expect to access the PC remotely via the wireless link without anyone logged in. Maybe you can revise your startup to allow that or make it the first part of the login script.

[pashby]

Hello again

Yes it would seem that things should be easy.

But the machines are not visible before logins and users cannot connect to the domain so that they can login!

Not being any authority with wireless networking I'm wondering whether this is 'feature' or whether it does have something to do with the AD configuration.

I've tried a run of the Belkin utility at startup through AD security profiles for the local machines in the Library group but it has the same problem in that the network is not connected until the initial login.

We are trying XP as the operating system rather than 2000 to see there is a difference but I doubt it because my laptop with XP will not logon to the network unless I first logon to the laptop.

Peter
:confused:

[Greenstead]

Maybe I am assuming too much. I can test it at home and see if the wireless connection is there before login.

Do you use a Belkin wireless utility? In XP you can use the Wireless zero configuration service. I don't know if that will help.

Two other possible ideas:
1. Don't power off, use standby.

2. Add to startup script to login and logout the guest account.

[BenOram]

>But the machines are not visible before logins and users cannot connect to the domain so that they can login!

This sounds more like an ActiveDirectory issue to me (soecifically, a configuration issue in the GPO). By default, the user should be able to logon to their workstation --without-- being connected to the domain as long as they have logged on to the domain previously. This is known as "cached credentials". I'm sure you can find plenty of resources on Microsoft's site, especially in technet regarding this. Also, this is assuming that each computer is joined to the domain.

I've used cached credentials against W2k servers and W2003 servers with great success.

[Greenstead]

I did some simple tests with a wireless XP Pro laptop.

I booted the laptop and did not login. The indicators on the wireless card showed it was powered and making some communication.

The laptop was not visible on the network by computername. It could not be accessed by computername by any means I tried. (Network places, VNC, RDP).

However it did respond to ping by IP address. And I could RDP to it by IP addres and then login.

All of which is interesting, but I think confirms what pashby has said.

I still suggest my previous ideas to try.

[pashby]

Hello Greenstead

Thanks for your testing - I'm pleased that you have had the same problems and it not just me.

Unfortunately I have experience a lot of negative pressure from both the heirachy and my technical staff regarding the introduction of wireless networks and this problem has added greatly to their ammunition.

I program extensively in Python and since all the machines have a Python installation it should be possible for me to write login batch scripts. Is it possible to automate the logoff as well once the initial login has been made?

Perhaps you can point me in the direction of example scripts that will give me ideas.

Thanks agin for your help.

Peter

:(

[Greenstead]

I am not experienced in scripting except a little in Kixstart which is a well known tool for windows.

You might find something useful here at this library:
http://kixhelp.com/udfs/

There is an 'Enableautologon' script there - I don't know if that might help you.