windows not automatically connecting to wifi network?
in [Wireless Internet]
|
From: mookytc on 22 Feb 2006 22:23 Hi all... I helped a friend hook up his wireless connection. HP pavilion laptop. Linksys WRT54G router. broadcom 802.11 b/g WLAN adapter . xp home sp2 loaded. No problem getting the wireless connection up and running. Here is the dilemma. Upon a cold boot or reboot windows cannot automatically hook up to the network. The wireless icon in the right corner says it is not connected. So I went into services, clicked on WZCSVC wireless zero config. The service status is always at stopped. I manually start the service and then close the window. I then click on the wireless network icon in the bottom right corner. It tells me windows cannot configure the wireless connection. At the bottom left of that window I choose advanced settings. Broadcom 802.11 b/g WLAN box appears. 2nd tab is wireless networks. I click on that tab and check use windows to configure my wireless network settings. Close out the box and windows finds the network and all is perfect after that. Strong signal, great reception anywhere in the house. The problem is upon a cold boot, reboot, or coming off stand by the connection to the wireless network is lost (he must click on his name to get back into windows .NET framework is loaded). To reestablish connection I had to go back into services, WZCSVC was stopped. Needed to manually start and go through the process stated above. It is only then that windows can find the network and all works properly. So I guess what I am saying is that somehow the wireless zero config (WZCSVC) is being stopped and under his broadcom adapter the use windows to configure my wireless network is being unchecked. Again it happens after a cold boot, reboot, or coming back from stand by. What is causing this? Could it be the .NET framework? I don't have much experience with wi fi but from what I tinkered with these steps are not necessary to connect wirelessly. Hope I was clear in the post and any info would be appreciated. Thx... DC
From: Rico on 23 Feb 2006 10:28 In article <1140665024.057894.234290(a)g43g2000cwa.googlegroups.com>, mookytc(a)yahoo.com wrote: >Hi all... I helped a friend hook up his wireless connection. HP >pavilion laptop. Linksys WRT54G router. broadcom 802.11 b/g WLAN >adapter . xp home sp2 loaded. > >No problem getting the wireless connection up and running. Here is the >dilemma. Upon a cold boot or reboot windows cannot automatically hook >up to the network. The wireless icon in the right corner says it is not >connected. So I went into services, clicked on WZCSVC wireless zero >config. The service status is always at stopped. I manually start the >service and then close the window. I then click on the wireless network >icon in the bottom right corner. It tells me windows cannot configure >the wireless connection. At the bottom left of that window I choose >advanced settings. Broadcom 802.11 b/g WLAN box appears. 2nd tab is >wireless networks. I click on that tab and check use windows to >configure my wireless network settings. Close out the box and windows >finds the network and all is perfect after that. Strong signal, great >reception anywhere in the house. > >The problem is upon a cold boot, reboot, or coming off stand by the >connection to the wireless network is lost (he must click on his name >to get back into windows .NET framework is loaded). To reestablish >connection I had to go back into services, WZCSVC was stopped. Needed >to manually start and go through the process stated above. It is only >then that windows can find the network and all works properly. So I >guess what I am saying is that somehow the wireless zero config >(WZCSVC) is being stopped and under his broadcom adapter the use >windows to configure my wireless network is being unchecked. Again it >happens after a cold boot, reboot, or coming back from stand by. > >What is causing this? Could it be the .NET framework? NO. I have all three versions of dotnet on my laptop with a broadcom chipset (HP) and WZC starts just fine. I would look to see what the management software for the adapter might be doing. But to the point of your question nothing in stock dotnet would be shutting the service down. > I don't have much >experience with wi fi but from what I tinkered with these steps are not >necessary to connect wirelessly. > >Hope I was clear in the post and any info would be appreciated. > >Thx... > >DC > fundamentalism, fundamentally wrong.
From: John Navas on 23 Feb 2006 10:49 [POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE] In <1140665024.057894.234290(a)g43g2000cwa.googlegroups.com> on 22 Feb 2006 19:23:44 -0800, mookytc(a)yahoo.com wrote: >Hi all... I helped a friend hook up his wireless connection. HP >pavilion laptop. Linksys WRT54G router. broadcom 802.11 b/g WLAN >adapter . xp home sp2 loaded. > >No problem getting the wireless connection up and running. Here is the >dilemma. Upon a cold boot or reboot windows cannot automatically hook >up to the network. The wireless icon in the right corner says it is not >connected. So I went into services, clicked on WZCSVC wireless zero >config. The service status is always at stopped. I manually start the >service and then close the window. I then click on the wireless network >icon in the bottom right corner. It tells me windows cannot configure >the wireless connection. At the bottom left of that window I choose >advanced settings. Broadcom 802.11 b/g WLAN box appears. 2nd tab is >wireless networks. I click on that tab and check use windows to >configure my wireless network settings. Close out the box and windows >finds the network and all is perfect after that. Strong signal, great >reception anywhere in the house. > >The problem is upon a cold boot, reboot, or coming off stand by the >connection to the wireless network is lost (he must click on his name >to get back into windows .NET framework is loaded). To reestablish >connection I had to go back into services, WZCSVC was stopped. Needed >to manually start and go through the process stated above. It is only >then that windows can find the network and all works properly. So I >guess what I am saying is that somehow the wireless zero config >(WZCSVC) is being stopped and under his broadcom adapter the use >windows to configure my wireless network is being unchecked. Again it >happens after a cold boot, reboot, or coming back from stand by. > >What is causing this? Could it be the .NET framework? I don't have much >experience with wi fi but from what I tinkered with these steps are not >necessary to connect wirelessly. There's probably a Broadcom wireless utility interfering with Windows. If so, uninstall it. -- Best regards, SEE THE FAQ FOR ALT.INTERNET.WIRELESS AT John Navas <http://en.wikibooks.org/wiki/FAQ_for_alt.internet.wireless>
From: mookytc@yahoo.com on 23 Feb 2006 21:39 John Navas wrote: > [POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE] > > In <1140665024.057894.234290(a)g43g2000cwa.googlegroups.com> on 22 Feb 2006 > 19:23:44 -0800, mookytc(a)yahoo.com wrote: > > >Hi all... I helped a friend hook up his wireless connection. HP > >pavilion laptop. Linksys WRT54G router. broadcom 802.11 b/g WLAN > >adapter . xp home sp2 loaded. > > > >No problem getting the wireless connection up and running. Here is the > >dilemma. Upon a cold boot or reboot windows cannot automatically hook > >up to the network. The wireless icon in the right corner says it is not > >connected. So I went into services, clicked on WZCSVC wireless zero > >config. The service status is always at stopped. I manually start the > >service and then close the window. I then click on the wireless network > >icon in the bottom right corner. It tells me windows cannot configure > >the wireless connection. At the bottom left of that window I choose > >advanced settings. Broadcom 802.11 b/g WLAN box appears. 2nd tab is > >wireless networks. I click on that tab and check use windows to > >configure my wireless network settings. Close out the box and windows > >finds the network and all is perfect after that. Strong signal, great > >reception anywhere in the house. > > > >The problem is upon a cold boot, reboot, or coming off stand by the > >connection to the wireless network is lost (he must click on his name > >to get back into windows .NET framework is loaded). To reestablish > >connection I had to go back into services, WZCSVC was stopped. Needed > >to manually start and go through the process stated above. It is only > >then that windows can find the network and all works properly. So I > >guess what I am saying is that somehow the wireless zero config > >(WZCSVC) is being stopped and under his broadcom adapter the use > >windows to configure my wireless network is being unchecked. Again it > >happens after a cold boot, reboot, or coming back from stand by. > > > >What is causing this? Could it be the .NET framework? I don't have much > >experience with wi fi but from what I tinkered with these steps are not > >necessary to connect wirelessly. > > There's probably a Broadcom wireless utility interfering with Windows. > If so, uninstall it. > > -- > Best regards, SEE THE FAQ FOR ALT.INTERNET.WIRELESS AT > John Navas <http://en.wikibooks.org/wiki/FAQ_for_alt.internet.wireless> Thanks John..uninstalling the utility will not affect the performance of the adapter? DC
From: John Navas on 24 Feb 2006 15:22 [POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE] In <1140748788.044064.96660(a)z34g2000cwc.googlegroups.com> on 23 Feb 2006 18:39:48 -0800, "mookytc(a)yahoo.com" <mookytc(a)yahoo.com> wrote: >John Navas wrote: >> [POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE] >> >> In <1140665024.057894.234290(a)g43g2000cwa.googlegroups.com> on 22 Feb 2006 >> 19:23:44 -0800, mookytc(a)yahoo.com wrote: >> >> >Hi all... I helped a friend hook up his wireless connection. HP >> >pavilion laptop. Linksys WRT54G router. broadcom 802.11 b/g WLAN >> >adapter . xp home sp2 loaded. >> > >> >No problem getting the wireless connection up and running. Here is the >> >dilemma. Upon a cold boot or reboot windows cannot automatically hook >> >up to the network. The wireless icon in the right corner says it is not >> >connected. So I went into services, clicked on WZCSVC wireless zero >> >config. The service status is always at stopped. I manually start the >> >service and then close the window. I then click on the wireless network >> >icon in the bottom right corner. It tells me windows cannot configure >> >the wireless connection. At the bottom left of that window I choose >> >advanced settings. Broadcom 802.11 b/g WLAN box appears. 2nd tab is >> >wireless networks. I click on that tab and check use windows to >> >configure my wireless network settings. Close out the box and windows >> >finds the network and all is perfect after that. Strong signal, great >> >reception anywhere in the house. >> > >> >The problem is upon a cold boot, reboot, or coming off stand by the >> >connection to the wireless network is lost (he must click on his name >> >to get back into windows .NET framework is loaded). To reestablish >> >connection I had to go back into services, WZCSVC was stopped. Needed >> >to manually start and go through the process stated above. It is only >> >then that windows can find the network and all works properly. So I >> >guess what I am saying is that somehow the wireless zero config >> >(WZCSVC) is being stopped and under his broadcom adapter the use >> >windows to configure my wireless network is being unchecked. Again it >> >happens after a cold boot, reboot, or coming back from stand by. >> > >> >What is causing this? Could it be the .NET framework? I don't have much >> >experience with wi fi but from what I tinkered with these steps are not >> >necessary to connect wirelessly. >> >> There's probably a Broadcom wireless utility interfering with Windows. >> If so, uninstall it. >Thanks John..uninstalling the utility will not affect the performance >of the adapter? Not if the driver remains installed. You may have to uninstall everything, and then reinstall just the driver. -- Best regards, SEE THE FAQ FOR ALT.INTERNET.WIRELESS AT John Navas <http://en.wikibooks.org/wiki/FAQ_for_alt.internet.wireless>
|
Pages: 1 Prev: Use WiFi as an Ethernet bridge to the Internet? Next: Livebox problems |