Tips for using IPv6 in Windows 7

  
                  Just when people are busy discussing when IPv4 addresses are exhausted, when they migrate to the IPv6 protocol architecture, many people are already using IPv6 without knowing it. Although Windows 7 does not seem to have an integrated IPv6 protocol, in reality, IPv6 is used in two network applications of Win7: DirectAccess and HomeGroup. Direct access For this web application, there are a few points to note. First, DirectAccess is for business users. Compared with the VPN implemented by the combination of IPv6 and IPSec of Win server 2008 R2, the built-in VPN of DirectAccess in Win7 Enterprise and Ultimate can better prevent hackers from stealing network data through firesheep. In addition, DirectAccess can be combined with Network Access Protection (NAP). The NAP system automatically checks whether the software installed on the remote access terminal is the latest version and whether a matching security policy is applied. When necessary, the system administrator can set up NAP to automatically update the software version of the remote terminal and apply a new security policy. In other words, when DirectAccess and NAP are applied at the same time, you can not only prevent remote terminals that do not have security compatibility from accessing the local network, but also automatically patch them and install anti-virus software client programs approved by the local enterprise network. Modify the security policy settings before allowing the terminal to access the local system. The combination of the two can be said to be the great love of system administrators. It allows administrators to easily manage remote access terminals and maintain their system security by simply setting them up on the local system. With DirectAccess, administrators can also improve network performance in both client and data centers. This function is achieved by separating the intranet data and extranet data of the enterprise. In the DirectAccess environment, only enterprise network data is transmitted in the enterprise server, and employees access the Internet to watch non-business activities such as video, and the data flow is still taking the enterprise gateway. The resulting change is a significant increase in data flow between the Win7 client and the enterprise data center. Remote Win7 users will no longer wait for a while before they can see the results returned by the data center. Data center switches will no longer waste bandwidth processing other data. In the traditional VPN mode, all data flows through the enterprise gateway. When using DirectAccess, you don't have to think about whether IPv6 is already running. Because both Win7 and Server 2008 R2 support IP-HTTPS. This is a tunneling protocol that hides IPv6 packets in IPv4-based HTTPS threads. If you know that your network environment is IPv4, such as in a public network environment in a hotel, coffee shop, or conference center, you can log in to the system as an administrator. Follow these steps to ensure that all remote Win7 users are using IP-HTTPS. The Force Tunneling option is selected by default. First log in as an administrator and follow these steps: 1. Open the Group Policy Management console, click Start on the Domain Controller, click Control Panel, click Administrative Tools, and then click Group Policy Management. Create a Group Policy Object (GPO) for the DirectAccess client computer. 2. In the newly created DirectAccess client GPO, find Computer ConfigurationPoliciesAdministrative TemplatesNetworkNetwork ConnectionsRoute all traffic through the internal network. Then click Edit policy setting, click Enabled, then Click OK. 3. In order to allow DirectAccess clients to access IPv4-based network resources via IP-HTTPS, we also use a web proxy server. If the web proxy server does not support IPv6, we can use Microsoft's Forefront UAG DirectAccess server NAT64 feature. It can translate IPv6-based access requests on the Internet into IPv4 requests. Home Group HomeGroup is an application for very small network environments. Many small businesses do not require Active Directory (AD) services or management functions, in which case the family group becomes an alternative to the old domain and workgroup model. Before converting a small network to a HomeGroup, there are some potential issues that need our attention. First of all, the family group is a unique technology of Win7. If not set manually, each Win7 system is a mini server with its own independent permissions, while non-Win7 systems will not be able to access PC resources in the home group. Of course, we can also share the resources on the home group PC to Windows XP, vista, mac os x and linux through settings, but I do not recommend this. Because doing so will cause a lot of trouble for your small network. If you really need file sharing across operating systems, you might consider setting up a real server, such as Windows 2003, Windows Server 2008, running Samba on Linux, or using the easiest way to buy a network storage device (NAS). And connect it to your network. Also note that although we can join any Win7 version of the family group, whether it is Home, Professional, Enterprise or Ultimate Win7, only one family group can be created. In short, you can't simply replace the existing Windowsxp peer-to-peer workgroup network with a family group, allowing computers to share resources with each other. Users who have already used IPv4 may have some trouble starting the IPv6 protocol in the home group. Here's how: they open the control panel's network connection, right-click on the network adapter, and select Properties to try to enable the IPv6 protocol. Under "Local Area Connection Status" they will see: IPv4 Connectivity: Internet IPv6 Connectivity: No network access Even if IPv6 is turned on, it has no effect. If you are experiencing the same trouble, you can manually set up IPv6 by following the steps below: 1. Click the Start button, type regedit in the search box, and then click regedit.exe in the list of programs. In the User Account Control dialog window, click Next. 2. Locate the following key in the Registry Editor: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters 3. Double-click DisabledComponents to modify the DisabledComponents item. 4. Type 0 (number 0) to enable all IPv6 components, click OK 5. Restart your computer Once you are done, you can use the IPv6 protocol in your home group. Enjoy the Win7 system with IPv6.
Copyright © Windows knowledge All Rights Reserved