[Valedic7orian]

Microsoft strikes again...

Newly built rig, running Windows Vista Ultimate 32, currently updated to KB953733 (as far as I was able to get before the net cut out)...

Network adapter is a PCI Device (D-Link DWL-G510 Wireless G Desktop Adapter), which has the latest model drivers correctly installed...

Router is a BT HomeHub 2, using WPA-Personal and TKIP settings...

Every other desktop/laptop in the house is able to connect to the router without problems.

However, my desktop either refuses to detect the router network, or when on occasion it does, declines to connect, detailing various error messages such as "Wireless association failed due to an unknown reason" or "Wireless association failed because Windows did not receive any response from the wireless router or access point". As mentioned above, the desktop will occasionaly detect and then connect to the router, but only for a period of about 15 seconds, whereupon it will lose signal and disconnect.

Wireless range is not an issue, as I am writing this on my laptop approximately 30 centimetres from my desktop, and am still able to connect perfectly (as are the other residents of my house).

I have taken a number of steps to attempt to ensure a connection, including setting up Static IPs for all household computers (including my desktop's), disabling DHCP on the router, performing the Windows registry hotfix, disabling IPv6, and disabling IPHelper (as recommended in an earlier thread).

However, the problem still persists... my last resort is placing an order for a long CAT-5 crossover cable to physically connect my desktop to the router...

However, any other suggestions/thoughts would be appreciated, as I am a student living on a rather tight budget!

[ShuggyX]

Are you connected as either Administrator as an admin equivalent user? I find that neither of those can connect to the network for long, and if they can they can't connect to the internet. 'Normal' users however have no problem at all.

I'm convinced it's a Vista oddity (I'm on SP1 btw) but have found no-one sharing the same symptoms in the year I've had the Vista PC.

Good luck.

[JohnWill]

Changes that may help to increase the compatibility of Vista with older networking devices:



Disable the IP Helper service:

1. Hold the Windows key and type R, enter "services.msc" (without the quotes) and press Enter
2. Scroll down to the IP Helper service, right click on it and select Properties
3. In the dropdown box that says "Automatic" or "Manual", set it to Disabled and then click on "Apply"
4. Then click on "Stop" to stop the service from running in the current session
5. Click OK to exit the dialog



Disable IPv6:

1. Hold the Windows key and type R, enter "ncpa.cpl" (without the quotes) and press Enter
2. Right click on each network connection and select "Properties"
3. Remove the checkmark from the box next to "Internet Protocol Version 6 (TCP/IPv6)
4. Click OK to exit the dialog

NOTE: You should do this for each network connection.



Disable the DHCP Broadcast Flag:

Link: http://support.microsoft.com/default.aspx/kb/928233

1. Hold the Windows key and type R, enter regedit and press Enter.
2. Locate and then click the following registry subkey:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{GUID}
4. In this registry path, click the (GUID) subkey to be updated.
5. If the key DhcpConnForceBroadcastFlag does not exist, use the Edit menu, point to New, and then click DWORD (32-bit) Value. In the New Value #1 box, type DhcpConnForceBroadcastFlag, and then press ENTER. If the key exists, skip this step.
6. Right-click DhcpConnForceBroadcastFlag, and then click Modify.
7. In the Value data box, type 0, and then click OK.
8. Close Registry Editor.

NOTE: You should do this for each and every GUID subkey.
NOTE2: (GUID) is a mnemonic for the individual subkeys, the actual text "GUID" does not appaer.




The only program I'm aware of that currently relies on IPv6 is the new Windows Meeting Space. The first 2 changes will cause that program not to work - but will leave all of your normal (IPv4) connections unaffected. If it causes problems that you can't overcome, simply revert back to the original settings.

[Valedic7orian]

JohnWill,

I've taken all the steps you've illustrated, but still no change

God I hate Vista...

[JohnWill]

I'd be interesting in seeing if a wired connection works. You can pack the computer closer to avoid using a long cable just for a test. Does this connect to any other wireless networks?

[Valedic7orian]

I moved the desktop downstairs and right next to the router... still unable to connect lol.

Searching for my short cable atm... Will try a physical connection when I find it.

[ShuggyX]

Hi again

I turned off security on the Airport, matched that in Vista and now even my Admin/Admin Equiv users can see the internet.

But obviously that's no good as a solution. Following advice here http://forum.notebookreview.com/showthread.php?t=118822 I then turned on WPA2 on the Airport using the Admin app I'd installed on the Vista machine (as opposed to my MacBook), but as soon as the Airport re-booted Vista could no longer see it.

As mentioned earlier all the non-admin users can see the internet even with WPA2 turned on, unless one of the admin users has been logged in first.

Anyone got any ideas?

ShuggyX

[JohnWill]

That makes no sense at all. I've had the reverse problem in the past with XP, limited users couldn't make wireless connections. I've never seen administrative accounts have a problem on a machine that connect in any mode.