[whitneysj]

I’m a relatively experienced Windows user with some administrative experience. I’ve setup, configured, and connected to many wireless networks in the past while using Windows XP. I recently purchased a Dell Latitude D830 laptop with a Windows Vista Ultimate operating system. I’m having problems connecting to various 802.11g unsecured wireless networks (i.e. airport/hotel/work/etc…) with this laptop and operating system. Often while trying to connect, the Windows Vista wireless icon on the toolbar will state that I have successfully connected to the given network but will state that only “local” access is available. When viewing the Network and Sharing Center window, the network icon between the computer and Internet icon will state “unidentified network”. When checking the IP address, it tells me that only an auto configuration IP address is present. While staying at a hotel in Ft Worth, Texas this past weekend, this scenario happened often while trying to connect to the hotel’s unsecured wireless network. Although it happened often, it did not happen each time I tried to connect to the hotel’s wireless network. Sometimes, the laptop would connect; grab an IP address, and state local and Internet access on the toolbar wireless icon. I had a Windows XP operating system Dell laptop present at one point in time when the Dell D830 would not successfully connect. At that same point in time, I was successfully able to connect with the Dell Windows XP operating system laptop. Based on this fact, I don’t believe that there was anything wrong with the hotel’s wireless network. Can anyone shed some light on this problem?

[JohnWill]

Vista can have issues connecting to some older network equipment.

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.




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.

[whitneysj]

Thanks JohnWill! I'll try your solutions the next time I have these same problems.

[TerryNet]

Given your symptoms I'd concentrate first on the third remedy: Disable the DHCP Broadcast Flag. If fact, I suggest that you do that now and don't wait for the problem again.

[whitneysj]

I tried to disable the DHCP broadcast flag and ran into a problem. When navigating to the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{GUID}, I get to the interfaces folder and do not find a {GUID} subkey. Does {GUID} represent something other than {GUID}? I only see the following underneath the interfaces subkey. Are each of the following a {GUID} subkey?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{0f694452-6a70-11db-8eb3-806e6f6e6963}

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{2767C850-4780-4478-B39B-738ECCF2B025}

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{98CBF209-7DDB-4E02-A7AC-84185B55BF04}

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{DE330243-9207-406D-9A35-4EF06AC00D1F}

[TerryNet]

I'm far from the expert here, but pretty sure that {GUID} somehow and for some reason means all those you listed.

[whitneysj]

I beleive that you are correct. I found a DhcpConnForceBroadcastFlag listing under each four of those subkeys and made the changes accordingly. Lets hope this solution works. Thanks for all the help!

[JohnWill]

You are correct, the {GUID} is repeated, and those funny long names are them.