|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
WiFi Constant ConnectivityMy question is this: is there any way to keep XP connected to a WiFi network
even when there is no user logged in? The wireless network I've set up in my office works great, but I'm finding it a bit more difficult to maintain employees' laptops that use wireless to connect to the regular network. The first problem is Windows Remote Access, which requires the machine to be turned on but logged out of any user account. It seems that when the laptop users log out from Windows XP their wireless connection is severed, making it impossible for me to log into the laptops remotely. The second problem is a mere annoyance caused by Windows Automatic Updates. As laptop users seem to only be connected when they are logged in, it means that Automatic Updates cannot proceed automatically at night with all the other machines but must be performed by the user after they have logged in. If there is any solution to the above problems, I would be most appreciative to hear it. Thanks! Hi
I do not quite follow your notion about keep the connection On, but not being logged in. What is login? If you refer to the opening screen at boot up that ask a user to log in, it is "No Can Do" since the computer is not fully functional at this point of the bootup. You would have to set an administrative account to be logged to in order to be connected to the Network, and do the updates. Jack (MVP-Networking). Show quoteHide quote "Lindsay" <Lind***@discussions.microsoft.com> wrote in message news:9E474493-7794-475D-B118-866C5FD394E7@microsoft.com... > My question is this: is there any way to keep XP connected to a WiFi > network > even when there is no user logged in? > > The wireless network I've set up in my office works great, but I'm finding > it a bit more difficult to maintain employees' laptops that use wireless > to > connect to the regular network. The first problem is Windows Remote > Access, > which requires the machine to be turned on but logged out of any user > account. It seems that when the laptop users log out from Windows XP > their > wireless connection is severed, making it impossible for me to log into > the > laptops remotely. The second problem is a mere annoyance caused by > Windows > Automatic Updates. As laptop users seem to only be connected when they > are > logged in, it means that Automatic Updates cannot proceed automatically at > night with all the other machines but must be performed by the user after > they have logged in. If there is any solution to the above problems, I > would > be most appreciative to hear it. Thanks! > > Thanks for the quick reply, Jack!
This is exactly what I want, for a laptop user to be able to log out of Windows and be presented with the Windows Log In screen, but still be connected to the wireless network. For cabled connections this is automatic, as long as the cable is plugged in to the NIC and the computer is on, it is connected, regardless of whether a user is actually logged in or not. Are you sure this is impossible to accomplish with a wireless connection? Thanks again for taking the time to answer my questions. Lindsay Show quoteHide quote "Jack (MVP-Networking)." wrote: > Hi > I do not quite follow your notion about keep the connection On, but not > being logged in. > What is login? If you refer to the opening screen at boot up that ask a > user to log in, it is "No Can Do" since the computer is not fully functional > at this point of the bootup. > You would have to set an administrative account to be logged to in order to > be connected to the Network, and do the updates. > Jack (MVP-Networking). > > "Lindsay" <Lind***@discussions.microsoft.com> wrote in message > news:9E474493-7794-475D-B118-866C5FD394E7@microsoft.com... > > My question is this: is there any way to keep XP connected to a WiFi > > network > > even when there is no user logged in? > > > > The wireless network I've set up in my office works great, but I'm finding > > it a bit more difficult to maintain employees' laptops that use wireless > > to > > connect to the regular network. The first problem is Windows Remote > > Access, > > which requires the machine to be turned on but logged out of any user > > account. It seems that when the laptop users log out from Windows XP > > their > > wireless connection is severed, making it impossible for me to log into > > the > > laptops remotely. The second problem is a mere annoyance caused by > > Windows > > Automatic Updates. As laptop users seem to only be connected when they > > are > > logged in, it means that Automatic Updates cannot proceed automatically at > > night with all the other machines but must be performed by the user after > > they have logged in. If there is any solution to the above problems, I > > would > > be most appreciative to hear it. Thanks! > > > > > > > It will depend on the software and the computer, I believe. But having said
that if you are using Windows XP and you have gone to System Properties | Remote | and checked "Allow users to connect remotely to this computer" you should be able to use Remote Desktop to gain access to their computer while they are logged in. IIRC. -- Show quoteHide quoteDavid Hettel Microsoft MVP Mobile Devices Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional Program http://mvp.support.microsoft.com DISCLAIMER: This posting is provided "AS IS" with no warranties, and confers no rights "Lindsay" <Lind***@discussions.microsoft.com> wrote in message news:BDB9050E-F02E-46F1-B31D-4791733DF640@microsoft.com... > Thanks for the quick reply, Jack! > > This is exactly what I want, for a laptop user to be able to log out of > Windows and be presented with the Windows Log In screen, but still be > connected to the wireless network. For cabled connections this is > automatic, > as long as the cable is plugged in to the NIC and the computer is on, it > is > connected, regardless of whether a user is actually logged in or not. Are > you sure this is impossible to accomplish with a wireless connection? > Thanks > again for taking the time to answer my questions. > > Lindsay > > "Jack (MVP-Networking)." wrote: > >> Hi >> I do not quite follow your notion about keep the connection On, but not >> being logged in. >> What is login? If you refer to the opening screen at boot up that ask a >> user to log in, it is "No Can Do" since the computer is not fully >> functional >> at this point of the bootup. >> You would have to set an administrative account to be logged to in order >> to >> be connected to the Network, and do the updates. >> Jack (MVP-Networking). >> >> "Lindsay" <Lind***@discussions.microsoft.com> wrote in message >> news:9E474493-7794-475D-B118-866C5FD394E7@microsoft.com... >> > My question is this: is there any way to keep XP connected to a WiFi >> > network >> > even when there is no user logged in? >> > >> > The wireless network I've set up in my office works great, but I'm >> > finding >> > it a bit more difficult to maintain employees' laptops that use >> > wireless >> > to >> > connect to the regular network. The first problem is Windows Remote >> > Access, >> > which requires the machine to be turned on but logged out of any user >> > account. It seems that when the laptop users log out from Windows XP >> > their >> > wireless connection is severed, making it impossible for me to log into >> > the >> > laptops remotely. The second problem is a mere annoyance caused by >> > Windows >> > Automatic Updates. As laptop users seem to only be connected when they >> > are >> > logged in, it means that Automatic Updates cannot proceed automatically >> > at >> > night with all the other machines but must be performed by the user >> > after >> > they have logged in. If there is any solution to the above problems, I >> > would >> > be most appreciative to hear it. Thanks! >> > >> > >> >> >> "Lindsay" <Lind***@discussions.microsoft.com> wrote in message news:9E474493-7794-475D-B118-866C5FD394E7@microsoft.com... What do you use to create profiles and connect: the Windows wireless> My question is this: is there any way to keep XP connected to a WiFi network > even when there is no user logged in? > configuration service (aka WZC) or other software (utility of the WLAN device manufacturer, or other) ? --PA Show quoteHide quote > The wireless network I've set up in my office works great, but I'm finding > it a bit more difficult to maintain employees' laptops that use wireless to > connect to the regular network. The first problem is Windows Remote Access, > which requires the machine to be turned on but logged out of any user > account. It seems that when the laptop users log out from Windows XP their > wireless connection is severed, making it impossible for me to log into the > laptops remotely. The second problem is a mere annoyance caused by Windows > Automatic Updates. As laptop users seem to only be connected when they are > logged in, it means that Automatic Updates cannot proceed automatically at > night with all the other machines but must be performed by the user after > they have logged in. If there is any solution to the above problems, I would > be most appreciative to hear it. Thanks! > > Thank you all for your help, I think I've got the situation sussed out.
David's pointer to the Remote / System Properties dialog was especially helpful, as the laptops in question were enabled for remote assistance but not remote desktop, which is what I am trying to use. As far as constant connectivity goes, I believe that if a user logs into the machine and allows it to connect to the WiFi network, the computer will remain connected even after the user has logged out. I'm not sure if the wireless connection is actually made before the user logs in, if someone could confirm this that would be great, but my issue has been resolved. Thanks for the help, people! Lindsay Show quoteHide quote "Lindsay" wrote: > My question is this: is there any way to keep XP connected to a WiFi network > even when there is no user logged in? > > The wireless network I've set up in my office works great, but I'm finding > it a bit more difficult to maintain employees' laptops that use wireless to > connect to the regular network. The first problem is Windows Remote Access, > which requires the machine to be turned on but logged out of any user > account. It seems that when the laptop users log out from Windows XP their > wireless connection is severed, making it impossible for me to log into the > laptops remotely. The second problem is a mere annoyance caused by Windows > Automatic Updates. As laptop users seem to only be connected when they are > logged in, it means that Automatic Updates cannot proceed automatically at > night with all the other machines but must be performed by the user after > they have logged in. If there is any solution to the above problems, I would > be most appreciative to hear it. Thanks! > > Lindsay,
you're asking the right questions... Assuming you have a domain controlled system, a wired machine will communicate with a domain controller at boot time using a "machine" credential. The default wireless behavior is to disconnect after user logout. To get an "always on" type behavior you have to enable machine authentication for your wireless connection. The only methods Microsoft supports are credential based. Either put a credential on your IAS server for PEAP. or assign credentials to your systems and use EAP-TLS. Then fiddle the registry variable HKLM\Software\Microsoft\EAPOL\Parameters\General\Global\AuthMode =1 I'm skipped a lot of details, but that should give you enough keywords to get you started. Dave. ------ Lindsay wrote: Show quoteHide quote > Thank you all for your help, I think I've got the situation sussed out. > David's pointer to the Remote / System Properties dialog was especially > helpful, as the laptops in question were enabled for remote assistance but > not remote desktop, which is what I am trying to use. > > As far as constant connectivity goes, I believe that if a user logs into the > machine and allows it to connect to the WiFi network, the computer will > remain connected even after the user has logged out. I'm not sure if the > wireless connection is actually made before the user logs in, if someone > could confirm this that would be great, but my issue has been resolved. > Thanks for the help, people! > > Lindsay > > "Lindsay" wrote: > > > My question is this: is there any way to keep XP connected to a WiFi network > > even when there is no user logged in? > > > > The wireless network I've set up in my office works great, but I'm finding > > it a bit more difficult to maintain employees' laptops that use wireless to > > connect to the regular network. The first problem is Windows Remote Access, > > which requires the machine to be turned on but logged out of any user > > account. It seems that when the laptop users log out from Windows XP their > > wireless connection is severed, making it impossible for me to log into the > > laptops remotely. The second problem is a mere annoyance caused by Windows > > Automatic Updates. As laptop users seem to only be connected when they are > > logged in, it means that Automatic Updates cannot proceed automatically at > > night with all the other machines but must be performed by the user after > > they have logged in. If there is any solution to the above problems, I would > > be most appreciative to hear it. Thanks! > > > > |
|||||||||||||||||||||||