I've been working on my roommate's computer all damn day because I get this "Event ID 6100: Wireless association failed due to an unknown reason" crap when I try to connect to my own home network. I have an Dell Inspiron 1520 running the latest Windows Vista 32-bit, and I can connect sans problems to my wireless network at the house. But for some reason, his is just messing up, and I don't know why. I'm pretty resilient and resourseful, but not a tech geek. I'm wondering if anyone has any idea wt* is going on. Here's his PC's particulars:
--HP Pavillion dv2700 Notebook PC
--AMD Turion 64 X2 TL-60 processor @ 2 GHz
--4.00 GB RAM
--Windows Vista 64-bit SP2
--Broadcom 4321AG 802.11a/b/g/draft-n Wireless Adapter
and now the error particulars:
Helper Class (RNWF MSM Helper Class) Event:
Wireless Diagnostic Helper Class Event
For complete information about this session see the Wireless Diagnostic Informational Event.
Helper Class: Native WiFi MSM
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 1ede8f65-4e0e-49e6-922e-339c09842320
Interface name: Broadcom 4321AG 802.11a/b/g/draft-n Wi-Fi Adapter #2
Interface type: Native WiFi
Profile: Discovery connection
SSID: Man_Cave
SSID length: 8
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: Problem found
Root cause:
Windows cannot connect to "Man_Cave"
Wireless association failed due to an unknown reason.
Detailed root cause:
802.11 connection failed due to status code 1: unspecified failure
Repair option:
Try connecting to "Man_Cave" again
If the problem continues, contact your network administrator or hardware manufacturer for further assistance.
Event Verbosity:0
Log Name: System
Source: Microsoft-Windows-Diagnostics-Networking
Date: 1/30/2010 8:38:13 PM
Event ID: 6100
Task Category: (12)
Level: Information
Keywords: (2)
User: LOCAL SERVICE
Computer: Chrisman-PC
Description:
Helper Class (RNWF MSM Helper Class) Event:
Wireless Diagnostic Helper Class Event
For complete information about this session see the Wireless Diagnostic Informational Event.
Helper Class: Native WiFi MSM
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 1ede8f65-4e0e-49e6-922e-339c09842320
Interface name: Broadcom 4321AG 802.11a/b/g/draft-n Wi-Fi Adapter #2
Interface type: Native WiFi
Profile: Discovery connection
SSID: Man_Cave
SSID length: 8
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: Problem found
Root cause:
Windows cannot connect to "Man_Cave"
Wireless association failed due to an unknown reason.
Detailed root cause:
802.11 connection failed due to status code 1: unspecified failure
Repair option:
Try connecting to "Man_Cave" again
If the problem continues, contact your network administrator or hardware manufacturer for further assistance.
Event Verbosity:0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Networking" Guid="{36c23e18-0e66-11d9-bbeb-505054503030}" />
<EventID>6100</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>12</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000002</Keywords>
<TimeCreated SystemTime="2010-01-31T03:38:13.219Z" />
<EventRecordID>43557</EventRecordID>
<Correlation ActivityID="{38108C72-9CB7-49C0-821B-FA3F4404320E}" />
<Execution ProcessID="4540" ThreadID="3808" />
<Channel>System</Channel>
<Computer>Chrisman-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HelperClassName">RNWF MSM Helper Class</Data>
<Data Name="EventDescription">Wireless Diagnostic Helper Class Event
For complete information about this session see the Wireless Diagnostic Informational Event.
Helper Class: Native WiFi MSM
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 1ede8f65-4e0e-49e6-922e-339c09842320
Interface name: Broadcom 4321AG 802.11a/b/g/draft-n Wi-Fi Adapter #2
Interface type: Native WiFi
Profile: Discovery connection
SSID: Man_Cave
SSID length: 8
Connection mode: Infra
Security: Yes
Connect even if network is not broadcasting: No
Result of diagnosis: Problem found
Root cause:
Windows cannot connect to "Man_Cave"
Wireless association failed due to an unknown reason.
Detailed root cause:
802.11 connection failed due to status code 1: unspecified failure
Repair option:
Try connecting to "Man_Cave" again
If the problem continues, contact your network administrator or hardware manufacturer for further assistance.
</Data>
<Data Name="EventVerbosity">0</Data>
</EventData>
</Event>
I have been to some of the following URL's for help, but none of what they offered helped at all:
http://forums.techguy.org/networking...-troubles.html
http://support.microsoft.com/kb/928233/en-us
http://www.vistax64.com/vista-networ...y-problem.html
The one regarding the {GUID} parameters is a no-go, because in his registry there IS no {GUID} string, only {1ede8f65-4e0e-49e6-922e-339c09842320}, {c328fed4-6a85-11db-9fbd-806e6f6e6963}, and {f4db94a2-b556-4088-8ad0-29b7b7a0131f} strings. I'm going to include the contents of thise as well but have screenshots (I'm not about to copy down all of that information longhand).
Any ideas?? This problem JUST happened and it's got me bummed. Thanks ahead of time.
Rick wrote:
Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers
26-Apr-07
Change all of them it does not matter you are having the problem with all adapters as I am. This is a Vista problem that has no solution yet that I can find. Static IP is the only way for now.
Previous Posts In This Thread:
On Sunday, April 01, 2007 4:08 PM
Brian W wrote:
Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP
if you go to
http://support.microsoft.com/kb/928233/en-us
it tells you how to get round this problem by regedit to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{GUID}
and adding a key
my question is how do I work out what the GUID is of the network card
my mac of the usb wireless stick is
ZyXEL G-202 Wireless USB Adapter
00-13-49-71-32-C8
Yes
Yes
fe80::cd40:4c0a:95ec:e4dd%10(Preferred)
192.168.1.102(Preferred)
255.255.255.0
01 April 2007 20:56:15
08 April 2007 20:56:14
192.168.1.1
192.168.1.1
234885961
these are the guid's
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{0f694452-6a70-11db-8eb3-806e6f6e6963}HKEY_LOCAL_MACHINE\SYSTEM\CurrentCont rolSet\Services\Tcpip\Parameters\Interfaces\{2c40b 21f-b5c2-11db-a647-000c76bf5189}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{90D972AE-1725-4F4C-A89E-D8B3D5EC1E25}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{AD10F175-FCEB-4446-9011-2E8D200A5FE4}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{B1A58B1D-607D-4AD2-8976-79B2BC3EC94F}
nothing seems to correspond in the driver details
btw mine connects fine but I want to know for future reference I had to tie
down someone's wireless card to the router to get is to connect
On Sunday, April 01, 2007 5:08 PM
Pavel A. wrote:
This KB article mentions also another registry value,
This KB article mentions also another registry value, DhcpConnForceBroadcastFlag,
that is global. If you set it, does it help?
--PA
On Monday, April 02, 2007 4:23 AM
Brian W wrote:
you meanMORE INFORMATIONIf the router or the non-Microsoft DHCP server does
you mean
MORE INFORMATION
If the router or the non-Microsoft DHCP server does not support the DHCP
BROADCAST flag, you can set the following registry entry as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{GUID}
Value name: DhcpConnForceBroadcastFlag
Value type: REG_DWORD
Value data: 0
it still applies to a specific GUID
"Pavel A." <> wrote in message
news:...
On Monday, April 02, 2007 4:25 AM
Brian W wrote:
you meanMORE INFORMATIONIf the router or the non-Microsoft DHCP server does
you mean
MORE INFORMATION
If the router or the non-Microsoft DHCP server does not support the DHCP
BROADCAST flag, you can set the following registry entry as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\{GUID}
Value name: DhcpConnForceBroadcastFlag
Value type: REG_DWORD
Value data: 0
it still applies to a specific GUID
"Pavel A." <> wrote in message
news:...
On Saturday, April 07, 2007 1:12 PM
Pavel A. wrote:
Re: Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP
Yes. You're right.
--PA
On Wednesday, April 11, 2007 2:40 AM
Jens wrote:
The question regarding how to identify correct GUID...
The question regarding how to identify correct GUID...
If when connected you browse through the GUIDs in the registry (the list you suppplied), you can see which has a content that matches your adapter - You can find the IP for instance..
BTW. Setting DhcpConnForceBroadcastFlag to 0 worked for me.
Br/Jens
On Thursday, April 26, 2007 10:48 AM
Rick wrote:
Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers
Change all of them it does not matter you are having the problem with all adapters as I am. This is a Vista problem that has no solution yet that I can find. Static IP is the only way for now.
Submitted via EggHeadCafe - Software Developer Portal of Choice
How to detect and Automatically install MSXML
http://www.eggheadcafe.com/tutorials...d-automat.aspx
Similar Threads
