how-to block ads
|
|
Uniqs:
21650 |
Share Topic
 |
 |
|
|
|
| reply to funchords
Re: WPA-PSK Communications Lockout or DHCP Failure Tip
errors in event log | 
connection status |
then i went to administrative tools - services - and made Wireless Zero Configuration automatic.
then, in registry, i went to the key
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > PCI
and right-clicked for permissions, deleted an "everyone" entry, and added a "users" group giving the entry "Full" permission, (the system entry already had full permissions) after finding this post...
»www.deltatangobravo.com/archives···sscode10 - because i had a feeling about authentication being stopped by permissions. It may have made no difference at all, i don't know.
then i installed the wireless adapter, and opened the utility - and unticked " use this program to control..." and also unticked "show icon in systray".
i then opened network connections and right-clicked the wireless connection, and in properties - tcp/ip - added the ip address i wanted to use, and came out.
after a reboot(1), i went to administrative tools - services, verified Wireless Zero was still automatic, and noticed the entry directly below - WLTRYSVC - which is installed with the belkin drivers, and runs to configure the card. i changed it from automatic to disabled.
at that point, i opened the wireless properties, which was in the task-bar, showing available networks. i clicked on my chosen ssid which appeared there, and filled in the network key in the boxes below it, and clicked connect.
since the last step i have sat here for over 65 minutes without rebooting, as you will see from the pic, the wireless card has remained connected for as long, and not disconnected once.
however, at the time of install or reboot(1), a couple of errors appeared in the event log - which i have added as an attachment. they appear in the right order, pictured across, and seem to have been fixed as you can see - two errors, then four successes. i am now about to reboot my computer and see if the whole thing has worked. I'll let you know. -----thanks!!!----- | |
| --------------------SUCCESS--------------------
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
i unplugged the computer - and then also the router. left the router off for about 3 minutes. restarted. then started computer, hardwired. then, after some hesitation, unplugged the lan cable - waited about half a minute - then opened ie.. i saw google!
checked the event log, loads of entries regarding authentication - and including these events:
RASMAN
Advapi
LSASRV.dll : negotiate
kerberos.dll : Kerberos
msv1_0.dll : NTLM
schannel.dll : Microsoft Unified Security Protocol Provider
schannel.dll : Schannel
wdigest.dll : WDigest
msv1_0.dll : MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
KSecDD
Winlogon
Winlogon\MSGina
scecli
DCOMSCM
CHAP
RASMAN
there were a couple of errors but im on the internet now completely wireless.
thank you fun chords for spurring me on to do this - i didnt think it would be possible. i hope any information i provided will be helpful.
David | |
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | WOOHOO! I'll take a look it, but congrats!!!! | |
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | reply to blackcurtain
PS: I think I know what was causing the events in the snapshot. It has nothing to do with wireless, and Microsoft says to ignore it. I won't bother you with the details. In short, the user-friendly XP logon screen causes these to appear. There are no negative effects.
--
Robb Topolski  http://www.funchords.com/  Hillsboro, Oregon USA
... How much spam would a spam clan spam if the CAN-SPAM could can spam? ... | |
| reply to funchords
First of all thanks to funchords - I spent hours and hours trawling BBs and product support pages; this was the only sensible and comprehensive advice which actually told me WHY problem was happening!
For other readers following me not getting results I had this problem with a Netgear DG834G and Intel 2200BG chipset in a Toshiba (using PROset tool to config). When switched to WPA-PSK from WEP, no IP acquired, DHCP not found etc...
Thought I would post as problem solution was a bit different - I resorted to uninstalling the wireless network adaptor - rescanning for hardware, letting windows do its thing then - crucially as it turns out - NOT choosing to use PROset again (when asked) but using Windows to configure wireless connections. Was able to keep same SSID, key etc.
This worked where choosing PROset again failed. Don't know if reverse works - i.e. you are having this trouble with windows config and switch to product specific applet upon switching to WPA-PSK. Re-installing hardware & changing config tool at the same worth a try though.
Thanks,
M | | |
|
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5
1 edit | said by justthisonce2:First of all thanks to funchords - I spent hours and hours trawling BBs and product support pages; this was the only sensible and comprehensive advice which actually told me WHY problem was happening! You're welcome!
said by justthisonce2:For other readers following me not getting results I had this problem with a Netgear DG834G and Intel 2200BG chipset in a Toshiba (using PROset tool to config). When switched to WPA-PSK from WEP, no IP acquired, DHCP not found etc... Thought I would post as problem solution was a bit different - I resorted to uninstalling the wireless network adaptor - rescanning for hardware, letting windows do its thing then - crucially as it turns out - NOT choosing to use PROset again (when asked) but using Windows to configure wireless connections. Was able to keep same SSID, key etc. The reason this works is because when you uninstall/reinstall a driver, Windows re-enumerates the card, treating it as brand new hardware. It gets a new and unique GUID in the registry (you'll notice that your old TCP/IP and Wireless settings were gone and the adapter and network stack is set to the default settings). All of the WZCSVC (Wireless Zero Config) and EAPOL (Extensible Auth Protocol) settings are stored -under- the adapter's GUID. So, wallah, you have clean configs.
Same result, different method.
One additional step others might want to do is to unplug/restore power to the wireless router or Access Point. If the AP has put your wireless card on its twit list, power-cycling will clear it out.
PROset is flashy looking, but WZCSVC is easier and it works. PROset probably works too, I just am not used to it. Whenever I encounter it, I get a bit frustrated at its quirks and end up uninstalling it.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ | |
| Re: WPA-PSK Communications Lockout or DHCP Failure One more explanation to add, for the recordbooks....
Sygate personal firewall was the culprit in my case - no doubt about it (I can recreate it over and over). Maybe that UDP Packetsize thingie I read about somewhere?
However, in my case, I spent a day or two trying everything else in the book.... (Early on, very early on, I set the Sygate to "Allow all", thinking that was enough).. Finally, turned it off, and connected via WPA-PSK instantly.
All the other symptoms were identical... I was able to connect with WEP and without encryption, but not with WPA-PSK, over and over... Worked on one machine, not the other.. I was blaming strange compatibility problems and so forth.
In my case, it was a new Zyxel wireless router to replace an aging WEP-only D-Link that triggered this adventure. Here's an interesting tidbit from the Zyzel's log... Persistent log entries whenever trying to connect (with the sygate running), reading "A wireless client is associated - xx:xx:xx:xx:xx" followed 3 seconds later with "A STA is rejected by 802.1x daemon - xx:xx:xx:xx:xx" where xx-xx-xx is the Mac address. | |
|
