I used this tweaking an Exchange configuration that used Server 2008, which shares a networking stack with Windows 7 and Vista.
By default, Windows Server 2008 R2, Windows 7, Windows Server 2008 and Windows Vista enable and use IPv6 as the default protocol. These versions of Windows will normally use IPv6 for all network communication and will step down to IPv4 as necessary.
You may decide to disable Windows IPv6 for several reasons. Perhaps your IPv4 network doesn't support it, and you want to disable unnecessary protocols. You may have also read that IPv6 breaks Outlook Anywhere on Exchange 2007 Client Access servers.
Most people think that you disable IPv6 by simply unchecking the Internet Protocol Version 6 (TCP/IPv6) checkbox, as shown above. This method disables IPv6 on the particular LAN interface and connection. For other network adapters or connections, users have to repeat the steps to disable IPv6. However, disabling IPv6 this way does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface. It also must be done manually and cannot be instrumented or enforced using Group Policy.
In order to truly disable IPv6, you must disable it in the registry in the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
Normally, the DisabledComponents value does not exist. If the value does not exist or the value data is 0, IPv6 is enabled on all interfaces.
In the right-pane, right-click, select New – DWORD Value. Enter the name as “DisabledComponent” and set its value as “FF” as shown below. Once done, restart the machine for the changes to take effect. If at a later time, you want to revert the changes simply delete the key and reboot the server.
----
Jack Kramer
Computer Systems Specialist
University Relations, Michigan State University
517-884-1231
From: "Aldrich, Dak" <[log in to unmask]">[log in to unmask]>
Reply-To: "Aldrich, Dak" <[log in to unmask]">[log in to unmask]>
Date: Mon, 10 Aug 2009 13:24:35 -0400
To: <[log in to unmask]">[log in to unmask]>
Subject: [MSUNAG] Captains Log Supplimental (Windows 7 issues)
Thank you Nick for some of your information.
I have figured out some form of making it work.
After noting that the Subnet Mask of the VPN connection was 255.255.255.255, i though... well... what the hell. I set my machine to a static IP address with a subnet mask of 255.255.255.255. After it warned me that it didn't match the local netowrk settings, and continuing to save the settings, EVERYTHING WORKED!
I was able to connect to my mail server, via all protocols, without connecting to the VPN. Does that flip any switches as to what MIGHT be causing it? I'm TOTALLY expecting it's something funky in the way i have the server set up... but maybe not? I don't know. Maybe a switch issue in the building? I'm still grasping at straws.
Thanks for the info i've gotten from a few individuals.
-dak
********************
* dak aldrich
* network admin
* college of music, msu
* [log in to unmask]">[log in to unmask]
* 517.432.5045
* comit.music.msu.edu