As we have noted in a previous post all IPv6 Link-local Addresses (LLA) share the same network identifier (fe80::) hence, you can cannot determine which interface an LLA is bound to, if the computer has multiple network adapters connected to different network segments. In fact, it distinguishes the networks by using a numeric zone ID, following a percent sign after the IP address as shown below: Fe80::4432:34d6:e6e6:b122%1 Fe80::4d3d:3426:46e6:1457%2 The two characters after each address indicate that the preceding networks are connected to the zone IDs 1 and 2 respectively. Zone IDs can be used with other types of addresses but it is recommended to always use the zone ID when connecting to LLAs. An important fact to remember is that zone IDs are relative to the sending host. For instance, if you want to ping another computer's LLA you have to specify your computer's network adapter zone ID at the end of the target computer IP address. For example, in the command ping fe80::4d3d:3426:46e6:1457%2, the address is of the computer you want to ping while the zone ID (%2) corresponds to the network interface of your computer. In Windows Servers 2008 the zone ID for an LLA is assigned on the basis of a parameter called the interface index for that network interface. You can view a list of interface indexes on a computer by typing netsh interface ipv6 show interface at a command prompt.
Pv6 Link-Local Addresses (LLAs) are similar to APIPA (Automatic Private IP Addressing) addresses in Windows IPv4 based systems. APIPA addresses are self-configured, non-routable addresses in the range of 169.254.0.0/16. But unlike APIPA addresses, LLA addresses remain assigned to an interface as a secondary address even after a routable address is obtained for that interface. An LLA address always begins with the prefix "fe80" and is structured as follows: The first half of the address is written as fe80:: but can be also written as fe80:0000:0000:0000. The second half of the address represents the interface ID. Each computer tags an LLA with a zone ID in the form "%ID". This zone ID is not part of the address but changes relative to each computer. It specifies the network interface that is connected either locally or across the network, to the address. You can read more about IPv6 here.
IPv6 global addresses are equivalent to Public IP addresses in IPv4 and are globally reachable on the IPv6 portion of the Internet. The global IPv6 address structure is divided into three parts, the Public and Private routing part, and the host identification within a LAN. These parts add up to 128 bits which are structured as follows: The first 48 bits of the address are the global routing prefix specifying the organization's network with the first 3 bits of this prefix must be 001 in binary notation. These 48 bits represent the public topology portion of the address which represents the collection of large and small ISPs on the IPv6 Internet and which is controlled by these ISPs through assignment by the IANA (Internet Assigned Numbers Authority). The next 16 bits are the subnet ID. The organization can use this portion to specify up to 65,536 unique subnets for routing purposes inside the internal network. These 16 bits represent the internal network portion of the address which the organization has control over. The final 64 bits are the interface ID and specify a unique interface within each subnet. This interface ID is equivalent to a host IP in IPv4.
To deploy shared printers to multiple client computers in a domain environment, the fastest method is using a Group Policy. Follow these steps: In Server Manager, select Roles\Print and Document Services\Print Management\Print Servers\<Server Name>\Printers and in the details pane, right-click the printer, and then choose Deploy with Group Policy. - if the Print and Document Services node is not available, add the Print and Document Services by right clicking Roles, selecting Add Roles and follow the wizard using default settings. In the Deploy with Group Policy dialog box, click the browse button to select the Group Policy object (GPO) that you want to use. Then, click ok. To deploy the printer to all users who log on to a particular computer, select the The Computers That This GPO Applies To check box. To deploy the printer to specific users regardless of which computers they log on to, select the The Users That This GPO Applies To check box. You can select both check boxes to deploy the printer using both the Computer Configuration and User Configuration nodes in a GPO. Click the Add button to add the GPO to the list, as shown below: Repeat steps 2 and 3 to deploy the printer to additional GPOs Click ok. Click ok to conform that the printers were successfully added to the GPO, and then click ok again to close the Deploy With Group Policy dialog box.
Organizations are looking into the details of IPv6 and see if they are ready to shift from IPv4. For instance, IPv6 has a new header format, and hence, IPv4 routers that have not been designed to support IPv6 cannot parse the fields in the IPv6 header. On the other hand, Layer 2 protocols are not affected where internal switches and hubs don't need an upgrade or replacement. In these short posts I will be writing about some protocols that are often mentioned in the migration from IPv4 to IPv6 platforms. Teredo Teredo is a tunneling protocol that allows clients located behind an IPv4 NAT device to use IPv6 over the Internet. It is used when no other IPv6 transition technology is available. Teredo's infrastructure includes client, servers, relays and host-specific relays: Teredo Client: is a computer that is enabled with both IPv6 and Ipv4 and that is located behind a router performing IPv4 NAT. The client configures an IPv6 address with the help of a Teredo server and communications with other IPv6 clients through a Teredo relay. Teredo Server: is a public server connected both to the IPv4 and to the IPv6 Internet and helps clients get their IPv6 address configuration, and facilitates initial communication either between two Teredo clients or between a Teredo client and an IPv6 host. Microsoft has deployed Teredo servers on the IPv4 Internet. Teredo Relay: is a Teredo tunnel endpoint, which acts as IPv6/IPv4 router that can forward packets between Teredo clients on the IPv4 Internet and IPv6-only hosts. Teredo host-specific relay: is a host that is enabled with both IPv4 and IPv6 and that acts as its own Teredo relay. Windows Vista and Windows Server 2008 include Teredo host-specific relay functionality. This host tunnels Teredo clients with global IPv6 addresses through the IPv4 Internet.