Thursday, October 18, 2012

Questions about Remote Viewing

What is Remote Viewing?

Remote viewing is a structured, teachable discipline that enlists the unconscious mind to gain direct knowledge about inaccessible targets – about people, places, things, or events in the past, present, or future. A Remote Viewing session begins with a “cue” or question that defines the data you are seeking. These cues may consist of anything from the World’s next catastrophic event to locating your lost car keys. Remote Viewing was developed by the CIA and the United States military by studying how the human mind obtains data on an unconscious level. Through years of top secret scientific study, a protocol was developed that forces the mind to follow this unconscious process of data collection. This newly discovered skill, Remote Viewing; quickly produced high levels of accuracy far greater than the program originally expected; therefore, was utilized for real-life military operations. Though commonly defined as a “psychic” or “Psi” ability by many individuals; Remote Viewing is rather, a scientifically developed skill that is able to consistently obtain accuracy rates of 80% on data during an RV session. This is the first skill that truly unlocks the unconscious mind to consistently obtain accurate, reliable information about anything one would like to know. The individual responsible for refining Remote Viewing to what it is today is none other than Major Ed Dames; the most elite instructor in the RV industry. Major Dames is the only training instructor that provides the most effective and groundbreaking Remote Viewing program in the world! The new, built from the ground up, “Learn RV” course incorporates 17 years of evolved, post military operational knowledge. The training set utilizes the natural DVD menu system to provide a structured, comfortably paced training environment, with an effective mix of training targets, lectures, and feedback.  
  The history behind Remote Viewing

Remote Viewing techniques were pioneered by a group of scientists working with several highly gifted psychics, as part of a U.S. government-sponsored research program. Throughout 20 years of research and development, they developed a training methodology that enabled virtually anyone to be taught this powerful mind skill for information collection. In the mid-1970’s at the Stanford Research Institute, a team of scientists and psychics developed a protocol that allowed test subjects to describe distant locations. This protocol, dubbed "remote viewing," proved more reliable than earlier attempts to simply pick random numbers or guess selected cards. In fact, it turned out to be accurate enough to support sensitive intelligence operations. Equally remarkable, researchers found that these new and powerful mind skills could be taught to virtually anyone. A training model was developed and then refined by a military remote viewing unit. In 1995, this program came to light—and made headlines—when the CIA acknowledged its the existence of a clandestine program known as "Stargate." Under this program Military Intelligence personnel had undergone training to become psychic spies. Remote Viewing is now declassified to the public.  
How does Remote Viewing work?

The Remote Viewing protocol is what gradually trains the unconscious mind to provide information regarding a target in a specific sequence of data. As you write down the data obtained, you become more connected with the target thereby gradually providing increasingly detailed information. This information is then translated into sketches and drawings. In remote viewing theory, everything in the universe exists as a pattern of information within the collective unconscious, or what is sometimes referred to as the "Matrix." Remote viewing simply allows you to tap into this phenomenon and to transfer a particular pattern to your conscious awareness. Like much of modern quantum physics, this explanation challenges our common-sense notions of cause and effect. But the bottom line is that trained remote viewers hit their "targets" with at least 80-90% accuracy. It should be noted that within the Remote Viewing community, "viewing" is considered a metaphor instead of a literal description; what actually happens would more accurately be called "perceiving." Indeed, remote viewers must learn to bypass their rational thoughts in order to allow their unconscious to work. And though it makes use of the unconscious, Remote Viewing is the rigorous, repeatable, scientific collection of information.   Is meditation involved with Remote Viewing?

As with any skill or activity that requires attention, each individual has their own techniques for relaxing before they begin a Remote Viewing session; however, meditation does not have a direct involvement in the RV process. There are many misconceptions and misleading sources about Remote Viewing. Many sources that claim they teach Remote Viewing or a “related skill” in-fact have had no involvement with the original military funded program or even have an understanding of what REAL Remote Viewing is. It is important to utilize a source that teaches actual Remote Viewing and is not simply utilizing the name to sell false product or service. Be assured that Major Ed Dames and LearnRV.com is widely proclaimed as being the best source in the world for RV information and training! The Learn Remote Viewing training program has been PROVEN to work!   Are there different types of Remote Viewing?

Since Remote Viewing was derived strictly from several top secret U.S military and CIA research programs, a specific protocol was developed that one MUST follow in order to obtain accurate results during an RV session. No matter what acronyms are assign to a Remote Viewing program (coordinate, scientific, technical) there is only one true form of Remote Viewing Be assured that Major Ed Dames and LearnRV.com is widely proclaimed as being the best source in the world for RV information and training! The Learn Remote Viewing training program has been PROVEN to work with shocking results!   Can I Learn Remote Viewing through books or audio lectures?

Because of the nature of Remote Viewing and how it must be taught, it is crucial for interactive training lessons that provide detailed VISUAL examples to successfully understand the RV protocal. Utilizing a non visual training method would be the equivalent of learning how to paint through a book or an audio lecture. The lack of video would make the lessons and examples far too difficult to follow and greatly inhibit your training. After all, a picture is worth a thousand words. The Learn Remote Viewing DVD training program has been PROVEN to work and is widely considered the most effective course in the world!   Who can learn Remote Viewing? Virtually anyone can learn Remote Viewing but only students taught by a credited and effective training course or instructor can claim seeing real results in less than 24 hours of training!   Do I need to be “gifted” or have any previous experience?

You do not need to "gifted" or have any previous experience of any kind. The U.S. military and Major Ed Dames developed and refined the Remote Viewing protocol so that the average person, regardless of their background, is able to pick up and utilize Remote Viewing! Whether you are someone who is knowledgably in the realm of Remote Viewing or a skeptic, curious about this incredible military tool, Remote Viewing is equally as easy to learn.   Does age matter? Not at all! Students have been successfully trained in Remote Viewing ranging from 18 years of age to 70.   What can I use Remote Viewing for?

A Remote Viewing session begins with a “cue” which is a question that defines the data that you are seeking. These cues may consist of anything from the World’s next catastrophic event to locating your lost car keys. Only your imagination and desire limits the data you can obtain from Remote Viewing Just as an example, Remote Viewing cues can consist of anything including: Obtaining the truth regarding religion questions
Determining the outcome of political situations
Detailed information regarding upcoming catastrophic events
Finding missing objects and treasures
Locating missing persons
Finding Accurate medical treatments and or cures
Obtain information for assistance regarding your profession
Problem solving and research for work or at home
Information regarding event in the past, present or future
Person’s optimal health
Person’s optimal vocation
Person’s optimal mate
Person’s optimal location
Stock market and futures trading
And MORE! The list is endless; if there is anything that you want to know; it can be answered with Remote Viewing! You can count on your Remote Viewing data; your personal beliefs or previously conceived notions have absolutely no implications on the Remote Viewing process. An RV session will provide data that is absolutely truth.  

How to enable IPv6 in


Step-by-Step Guide for Setting Up IPv6 in a Test Lab

12 out of 17 rated this helpful - Rate this topic
Updated: July 27, 2006
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
This guide provides detailed information about how you can use five computers to create a test lab with which to configure and test IPv6 with the Microsoft® Windows® XP Professional with Service Pack 2 (SP2) operating system and the 32-bit versions of the Windows Server™ 2003 with Service Pack 1 (SP1) operating system. These step-by-step instructions take you through the configuration required for setting up IPv6 in the test lab.
noteNote
The following instructions are for configuring a test lab using a minimum number of computers. Individual computers are needed to separate the services provided on the network and to clearly show the desired functionality. This configuration is neither designed to reflect best practices nor is it designed to reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network.

Setting up the IPv6 infrastructure

The infrastructure for the IPv6 test lab network consists of five computers performing the following services:
  • A computer running Windows Server 2003 with SP1, Standard Edition, that is used as a Domain Name System (DNS) server. This computer is named DNS1.
  • A computer running Windows XP Professional with SP2 that is used as a client. This computer is named CLIENT1.
  • A computer running Windows Server 2003 with SP1, Standard Edition, that is used as a router. This computer is named ROUTER1.
  • A computer running Windows Server 2003 with SP1, Standard Edition, that is used as a router. This computer is named ROUTER2.
  • A computer running Windows XP Professional with SP2 that is used as a client. This computer is named CLIENT2.
The following figure shows the configuration of the IPv6 test lab.
IPv6 test lab configurationIn the preceding figure, there are three network segments:
  • Subnet 1 uses the private IP subnet prefix of 10.0.1.0/24 and global subnet prefix of 2001:DB8:0:1::/64.
  • Subnet 2 uses the private IP subnet prefix of 10.0.2.0/24 and global subnet prefix of 2001:DB8:0:2::/64.
  • Subnet 3 uses the private IP subnet prefix of 10.0.3.0/24 and global subnet prefix of 2001:DB8:0:3::/64.
All computers on each subnet are connected to a separate common hub or Layer 2 switch. The two router computers, ROUTER1 and ROUTER2, have two network adapters installed.
For the IPv4 configuration, each computer is manually configured with the appropriate IP address, subnet mask, default gateway, and DNS server IP address. For the IPv6 configuration, link-local addresses are used initially. Dynamic Host Configuration Protocol (DHCP) and Windows Internet Name Service (WINS) servers are not used.
The configuration of the lab routing infrastructure goes through three phases.
  1. IPv4 routing. This phase demonstrates IPv4 connectivity and the automatic configuration of IPv6 local-link addresses - similar to Automatic Private IP Addressing (APIPA).
  2. IPv6 routing. This phase demonstrates all test lab nodes can be reached by using IPv6 traffic.
  3. ISATAP routing. ISATAP is an address assignment and automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6/IPv4 hosts over an IPv4 intranet. This phase removes IPv6 connectivity for Subnet 2 and Subnet 3 and restores it using ISATAP.
The following sections describe how to configure each of the computers in the test lab with the basic IPv6 infrastructure. To create this test lab, configure the computers in the order presented.

Consider using Virtual PC or Virtual Server

Microsoft Virtual PC or Virtual Server allow you to create the computer lab used in this document using only one physical computer. After the virtual lab is configured, you can switch between the five virtual computers needed for this lab with the click of a button. For more information, see the following resources:

DNS1

DNS1 is a computer running Windows Server 2003 with SP1, Standard Edition. It is providing DNS Server services for the testlab.microsoft.com DNS domain. To configure DNS1 for this service, perform the following steps.
Configure DNS1 to provide DNS Services
  1. Install Windows Server 2003 with SP1, Standard Edition, as a standalone server. Set the Administrator password.
  2. After restarting, log on as Administrator.
  3. Configure the TCP/IP protocol with the IP address of 10.0.1.2, the subnet mask of 255.255.255.0, and the default gateway of 10.0.1.1.
Install the DNS Server service
  1. Open Windows Components Wizard. To open the Windows Components Wizard, click Start, click Control Panel, double-click Add or Remove Programs, and then click Add/Remove Windows Components.
  2. In Components, select the Networking Services check box, and then click Details.
  3. In Subcomponents of Networking Services, select the Domain Name System (DNS) check box, click OK, and then click Next.
  4. If prompted, in Copy files from, type the full path to the distribution files, and then click OK.
Define a forward lookup zone named testlab.microsoft.com that allows dynamic updates.
Define a forward lookup zone
  1. Open DNS. To open DNS, click Start, select Administrative Tools, and then click DNS.
  2. In the console tree, click and then right-click the DNS server DNS1, and then click New Zone to run the New Zone Wizard.
  3. On the Welcome to the New Zone Wizard page, click Next.
  4. On the Zone Type page, the option to create a primary zone is selected by default. Click Next.
  5. On the Forward or Reverse Lookup Zone page, the option to create a forward lookup zone is selected by default. Click Next.
  6. On the Zone Name page, type testlab.microsoft.com in Zone name. Click Next.
    noteNote
    The domain name testlab.microsoft.com is used here for example purposes only. You can use any domain name in your test lab configuration.

  7. On the Zone File page, the new zone file name, testlab.microsoft.com.dns, is automatically derived from the zone name entered on the previous page, as shown in the following figure. Click Next.
    New Zone Wizard: Zone File
  8. On the Dynamic Update page, select Allow both nonsecure and secure dynamic updates. Click Next.
  9. Click Next. On the Completing the New Zone Wizard page, click Finish.
Install IPv6
  • On DNS1, at the command prompt, type:
    netsh interface ipv6 install

CLIENT1

CLIENT1 is a computer that is being used as a client.
Configure CLIENT1 as a client computer
  1. Install Windows XP Professional with SP2 as a workgroup computer. Set the Administrator password.
  2. After restarting, log on as Administrator.
  3. At the command prompt, install the IPv6 protocol by typing:
    netsh interface ipv6 install
  4. Configure the TCP/IP protocol with the IP address of 10.0.1.3, the subnet mask of 255.255.255.0, a default gateway of 10.0.1.1, and the DNS server IP address of 10.0.1.2.
  5. Append the DNS suffix testlab.microsoft.com. Click Start, click Control Panel, click Network and Internet Connections, and then click Network Connections. Right-click the network connection that you want to configure, and then click Properties. On the General tab, click Internet Protocol (TCP/IP), and then click Properties. Click Advanced, and then click the DNS tab. Add testlab.microsoft.com to the list of DNS suffixes, as show in the following dialog box:
    b821bd3f-c58f-4da8-8e54-7eac43054883
Windows Firewall is automatically turned on in Windows XP Professional with SP2. You need to configure an exception to allow CLIENT2 to ping CLIENT1.
Configure Windows to allow communication between client computers
  1. Click Start, point to Control Panel, and then click Security Center.
  2. Click Windows Firewall, and then in the Windows Firewall dialog box, click the Advanced tab.
  3. Click Settings for ICMP, and then click Allow incoming echo request.
  4. Click OK twice to close Windows Firewall.

ROUTER1

ROUTER1 is a computer that is being used as a router between Subnet 1 and Subnet 2.
Configure ROUTER1 as a router
  1. Install Windows Server 2003 with SP1, Standard Edition, as a workgroup computer. Set the Administrator password.
  2. After restarting, log on as Administrator.
  3. At the command prompt, install the IPv6 protocol by typing:
    netsh interface ipv6 install
  4. In Control Panel-Network Connections, rename the LAN connection connected to Subnet 1 to Subnet 1 Connection and rename the LAN connection connected to Subnet 2 to Subnet 2 Connection.
  5. For Subnet 1 Connection, configure the TCP/IP protocol with the IP address of 10.0.1.1, the subnet mask of 255.255.255.0, and the DNS server IP address of 10.0.1.2.
  6. For Subnet 2 Connection, configure the TCP/IP protocol with the IP address of 10.0.2.1, the subnet mask of 255.255.255.0, and a default gateway of 10.0.2.2.
  7. Start the registry editor (Regedit.exe) and set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\Tcpip\Parameters\\IPEnableRouter to 1.
    This step enables IPv4 routing between Subnet 1 and Subnet 2.
  8. Restart the computer.

ROUTER2

ROUTER2 is a computer that is being used as a router between Subnet 2 and Subnet 3.
Configure ROUTER2 as a router
  1. Install Windows Server 2003 with SP1, Standard Edition, as a workgroup computer. Set the Administrator password.
  2. After restarting, log on as Administrator.
  3. At the command prompt, install the IPv6 protocol by typing:
    netsh interface ipv6 install
  4. Open Network Connections, and rename the LAN connection connected to Subnet 2 to Subnet 2 Connection, and rename the LAN connection connected to Subnet 3 to Subnet 3 Connection.
  5. For Subnet 2 Connection, configure the TCP/IP protocol with the IP address of 10.0.2.2, the subnet mask of 255.255.255.0, and a default gateway of 10.0.2.1.
  6. For Subnet 3 Connection, configure the TCP/IP protocol with the IP address of 10.0.3.1 and the subnet mask of 255.255.255.0.
  7. Start the registry editor (Regedit.exe) and set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\Tcpip\Parameters\IPEnableRouter to 1.
    This step enables IPv4 routing between Subnet 2 and Subnet 3.
  8. Restart the computer.

CLIENT2

CLIENT2 is a computer that is being used as a client.
Configure CLIENT2 as a client computer
  1. Install Windows XP Professional with SP2 as a workgroup computer. Set the Administrator password.
  2. After restarting, log on as Administrator.
  3. At the command prompt, install the IPv6 protocol by typing:
    netsh interface ipv6 install
  4. Configure the TCP/IP protocol with the IP address of 10.0.3.2, the subnet mask of 255.255.255.0, a default gateway of 10.0.3.1, and the DNS server IP address of 10.0.1.2, and append the DNS suffix testlab.microsoft.com.
  5. Verify the integrity of the IPv4 routing infrastructure by pinging 10.0.1.3 from the CLIENT2 computer. On CLIENT2, type the following command:
    ping 10.0.1.3
    You should be able to successfully ping CLIENT1.

Link-local addresses

Link-local addresses, identified by the beginning address block FE80, are equivalent to APIPA IPv4 addresses autoconfigured on computers running current Microsoft Windows operating systems using the 169.254.0.0/16 prefix. One of the most useful aspects of IPv6 is its ability to automatically configure itself without the use of a stateful configuration protocol, such as Dynamic Host Configuration Protocol for IPv6 (DHCPv6). By default, an IPv6 node configures a link-local address for each interface. Link-local addresses are used by nodes when communicating with neighboring nodes on the same link (a network segment bounded by routers). The scope of a link-local address is the local link. An IPv6 router never forwards link-local traffic beyond the link.

Link-local ping

At this point in the lab configuration, only IPv4 traffic across the subnets is routed through an IPv4 routing infrastructure. However, you should be able to successfully ping neighboring link-local addresses. After the lab is configured to route IPv6 traffic, you will be able to successfully ping using global addresses.
Determine and ping the link-local address of CLIENT1 from DNS1
  1. On CLIENT1, type the ipconfig command to obtain the link-local address and interface index of the interface named Local Area Connection.
    1f92c349-5f5f-4482-bb7a-e940cc87f921In this example, the link-local address is FE80::203:FFFF:FEE1:2A73 and the interface index is 5.
  2. On DNS1, type the ipconfig command to obtain the interface index of the interface named Local Area Connection.
    In this example, the interface index of Local Area Connection is 4.
    1a5a4a42-7cd7-4e12-b9f6-9b2b5982b0a4
  3. On DNS1, ping the IPv6 link-local address of CLIENT1. You must use the interface index of the sending interface, the Local Area Connection interface of DNS1. For example, using the example configuration in step 1:
    ping FE80::203:FFFF:FEE1:2A73%4
    A successful ping demonstrates that CLIENT1 and DNS1 are neighbors on the same link.

Creating a static IPv6 routing infrastructure

Configure a static IPv6 routing infrastructure so that all test lab nodes can be reached by using IPv6 traffic.
Create a static IPv6 routing infrastructure
  1. On ROUTER1, type the ipconfig command to obtain the link-local addresses of the interfaces connected to Subnet 1 Connection and Subnet 2 Connection.
    d7d3697e-7374-47a4-b7fe-cef568ab6b1eFor this example, the information is as follows:
    Subnet 1 Connection - FE80::203:FFFF:FEE1:FA74
    Subnet 2 Connection - FE80::203:FFFF:FEFC:FA75
  2. On ROUTER2, type the ipconfig command to obtain the link-local addresses of the interfaces connected to Subnet 2 Connection and Subnet 3 Connection.
    6a1b4300-5b8f-4cf8-82c7-1cc2d898cd92For this example, the information is as follows:
    Subnet 2 Connection - FE80::203:FFFF:FEE0:FA76
    Subnet 3 Connection - FE80::203:FFFF:FEFD:FA77
  3. On ROUTER1, type the following commands:
    1. netsh interface ipv6 set interface "Subnet 1 Connection" forwarding=enabled advertise=enabled
    2. netsh interface ipv6 set interface "Subnet 2 Connection" forwarding=enabled advertise=enabled

      Steps a. and b. configure the Subnet 1 and 2 Connection interfaces to route (forward IPv6 packets not addressed to them) and advertise subnet prefixes (for address autoconfiguration).
    3. netsh interface ipv6 add route 2001:db8:0:1::/64 "Subnet 1 Connection" publish=yes
    4. netsh interface ipv6 add route 2001:db8:0:2::/64 "Subnet 2 Connection" publish=yes

      Steps c. and d. add routes to the IPv6 routing table corresponding to the subnet prefix for Subnet 1 and 2 and configures the router to advertise these routes in Router Advertisement messages.
    5. netsh interface ipv6 add route ::/0 "Subnet 2 Connection" nexthop=ROUTER2AddressOnSubnet2 publish=yes

      Step e. adds the default route to the IPv6 routing table and configures the router to advertise itself as a default router in the Router Advertisement messages.
    In the preceding command, ROUTER2AddressOnSubnet2 represents the link-local address assigned to the Subnet 2 Connection interface on ROUTER2. For example, using the connection in this lab the command would be:
    netsh interface ipv6 add route ::/0 "Subnet 2 Connection" nexthop= FE80::203:FFFF:FEE0:FA76 publish=yes
  4. On ROUTER2, type the following commands:
    1. netsh interface ipv6 set interface "Subnet 2 Connection" forwarding=enabled advertise=enabled
    2. netsh interface ipv6 set interface "Subnet 3 Connection" forwarding=enabled advertise=enabled
    3. netsh interface ipv6 add route 2001:db8:0:2::/64 "Subnet 2 Connection" publish=yes
    4. netsh interface ipv6 add route 2001:db8:0:3::/64 "Subnet 3 Connection" publish=yes
    5. netsh interface ipv6 add route ::/0 "Subnet 2 Connection" nexthop=ROUTER1AddressOnSubnet2 publish=yes
    In the preceding command, ROUTER1AddressOnSubnet2 represents the link-local address assigned to the Subnet 2 Connection interface on ROUTER1. For example, using the connection in this lab the command would be:
    netsh interface ipv6 add route ::/0 "Subnet 2 Connection" nexthop= FE80::203:FFFF:FEFC:FA75 publish=yes

Global addresses

At this point, you have now created static IPv6 routes with global subnet prefixes. Global addresses are equivalent to the IPv4 public address space. Unlike link-local addresses, global addresses are not automatically configured and must be assigned either through stateless or stateful address configuration processes. You can determine which address is the global address by the "ff:fe" portion of the public address in the sixth and seventh blocks of the address, indicating an EUI-64-based interface ID. The Extended Unique Identifier (EUI)-64 address is a newer 64-bit MAC address.

Global ping

Verify the IPv6 routing structure
  1. On CLIENT1, type the ipconfig command to check for a new global IPv6 address.
    97235c90-4675-46b6-8a18-0c5e4aa02438In this example, the CLIENT1 global address is 2001:DB8:0:1:203:FFFF:FEE1:2A73.
  2. On CLIENT2, type the following commands:
    ping CLIENT1GlobalAddress
    tracert -d CLIENT1GlobalAddress
    In this example, the CLIENT1 global address is 2001:DB8:0:1:203:FFFF:FEE1:2A73.
    A successful ping and tracert demonstrates that IPv6 static routes have been created and are functioning.
  3. You can view the entries in the ROUTER1 neighbor cache for CLIENT1 and ROUTER2, by typing the following on ROUTER1:
    netsh interface ipv6 show neighbors

Using name resolution

To resolve host names to IPv6 addresses, you must first configure DNS. On DNS1, create an AAAA record for CLIENT2 with the DNS name client2.testlab.microsoft.com for its global IPv6 address using the IPv6 Host resource record type.
Configure DNS to resolve names to IPv6 addresses
  1. On DNS1, click Start, select Administrative Tools, and then click DNS.
  2. In the console tree, click and then right-click testlab.microsoft.com in the Forward Lookup Zones folder, and then click Other New Records.
  3. Click IPv6 Host (AAAA), and then click Create Record.
  4. In the Host text box type client1, and then in the IP version 6 host address text box, enter the IPv6 global address for CLIENT1.
    In this example, the CLIENT1 global address is 2001:DB8:0:1:203:FFFF:FEE1:2A73.
    e3c2d8a5-b7dd-4e57-aa31-dbdb6b65439c
  5. Click OK, and then click Done to add the new IPv6 host record to the zone.
  6. On CLIENT 2, type the following command:
    ping client1
    A successful ping demonstrates that host names can resolve to IPv6 addresses.

Configuring the test lab to use ISATAP

ISATAP is an address assignment and automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6/IPv4 hosts on an IPv4 intranet, which are also known as ISATAP hosts. ISATAP is described in RFC 4214. More information about ISATAP can be found in the IPv6 Transition Technologies white paper (http://go.microsoft.com/fwlink/?LinkId=67210). By default, the IPv6 protocol for Windows XP Professional with SP2 and Windows Server 2003 with SP1, Standard Edition, configures a link-local ISATAP address on the Automatic Tunneling Pseudo-Interface for each IPv4 address assigned to a computer.
To configure global ISATAP addresses, or to communicate beyond the logical subnet defined by the IPv4 intranet, you need an ISATAP router. An ISATAP router performs the following functions:
  • Advertises its presence and address prefixes, enabling global ISATAP addresses to be configured.
  • Optionally forwards IPv6 packets between ISATAP hosts on the IPv4 intranet and IPv6 hosts beyond it.
An ISATAP router is typically configured to perform both functions, but can perform either individually. Most often, an ISATAP router acts as the forwarder between ISATAP hosts on an IPv4 intranet and IPv6 hosts on an IPv6-enabled portion of an intranet.
To demonstrate the use of an ISATAP router between IPv6 and IPv4 intranets, the following steps first separate the lab into a portion that has IPv4 and IPv6 connectivity and another that has IPv4 connectivity only. Then, ROUTER1 is configured as an ISATAP router so that hosts on the IPv4-only portion of the intranet can communicate with hosts on the IPv6-enabled portion of the intranet.
To do this, we will disable IPv6 forwarding and advertising on the Subnet 2 Connection interface of ROUTER1 and both interfaces of ROUTER2. This emulates an intranet in which a portion is IPv6-enabled (Subnet 1) and a portion is not (Subnet 2 and Subnet 3).
Configure the test lab to use ISATAP
  1. Disable forwarding and advertising on the Subnet 2 Connection interface of ROUTER1 and ROUTER2.
    1. On ROUTER1, at the command prompt, type:

      netsh interface ipv6 set interface "Subnet 2 Connection" forwarding=disabled advertise=disabled
    2. On ROUTER2, at the command prompt, type:

      netsh interface ipv6 set interface "Subnet 2 Connection" forwarding=disabled advertise=disabled
  2. Disable forwarding and advertising on the Subnet 3 Connection interface. On ROUTER2, at the command prompt, type:
    netsh interface ipv6 set interface "Subnet 3 Connection" forwarding=disabled advertise=disabled
  3. Renew CLIENT2 configuration to remove the global address and route. On CLIENT2, type the following command:
    netsh interface ipv6 renew
  4. Ping CLIENT1 from CLIENT2. On CLIENT2, type the following command:
    ping CLIENT1GlobalAddress
    or
    ping client1
    In this example, the CLIENT1 global address is 2001:DB8:0:1:203:FFFF:FEE1:2A73.
    This Ping command fails because there is no longer IPv6 connectivity between CLIENT2 and CLIENT1.
  5. Configure ROUTER1 as an ISATAP router advertising the 2001:DB8:0:10::/64 route to the logical ISATAP subnet consisting of Subnet 2 and Subnet 3.
    1. On ROUTER1, enable forwarding and advertising on the Automatic Tunneling Pseudo-Interface, using the following commands:

      netsh interface ipv6 isatap set router 10.0.2.1

      netsh interface ipv6 set interface "Automatic Tunneling Pseudo-Interface" forwarding=enabled advertise=enabled
    2. On ROUTER1, add a route for the subnet prefix of the logical subnet of the IPv4 intranet to the Automatic Tunneling Pseudo-Interface and configure it to be published. Use the following command:

      netsh interface ipv6 add route 2001:db8:0:10::/64 "Automatic Tunneling Pseudo-Interface" publish=yes
  6. Add an ISATAP address (A) resource record to the DNS server for the IPv4 address of 10.0.2.1.
    1. On DNS1, click Start, select Administrative Tools, and then click DNS.
    2. In the console tree, click and then right-click testlab.microsoft.com in the Forward Lookup Zones folder, and then click New Host (A).
    3. In the Name text box, type ISATAP, and in the IP address text box, type 10.0.2.1, as shown in the following figure.

      Dnsmgmt dialog box
    4. Click Add Host, click OK, and then click Done to add the new host record to the zone.
  7. Renew the CLIENT2 configuration to recognize the ISATAP router IPv4 address of ROUTER1 and obtain an ISATAP address with the global prefix of 2001:DB8:0:10::/64. On CLIENT2, type the following command:
    netsh interface ipv6 renew
  8. Ping CLIENT1 from CLIENT2. On CLIENT2, type the following command:
    ping CLIENT1GlobalAddress
    or
    ping client1
    In this example, the CLIENT1 global address is 2001:DB8:0:1:203:FFFF:FEE1:2A73.
    This ping command succeeds because IPv6 connectivity using ISATAP now exists between CLIENT2 and CLIENT1. On the link between CLIENT1 and ROUTER1, the IPv6 traffic is encapsulated as IPv4 packets.
noteNote
It may take a few minutes for IPv6 connectivity between CLIENT2 and CLIENT1 to be established. You may need to restart CLIENT2 and run netsh interface ipv6 renew on CLIENT1.

Conclusion

This guide described the steps required to configure IPv6 in a test lab with five computers. It also described how to use ISATAP to provide IPv6 connectivity between IPv6/IPv4 hosts on an IPv4-only portion of an intranet and IPv6 hosts on an IPv6-enabled portion of an intranet.

Additional references

For more information, see the following resources:

IPv6hostswindows




 

IPv6 installation for Windows users


What is the status of IPv6 support in Microsoft Operating Systems?

IPv6 is officially supported in Windows XP after Service Pack 1 and Windows Server 2003 (any version) and in Windows Vista.
There is experimental support for IPv6 in Windows XP (without service pack).
There is a Microsoft Research implementation for Windows NT4.0 and Windows 2000 here: http://research.microsoft.com/msripv6/msripv6.htm
There is a Technology Preview implementation for Windows 2000 here: http://msdn.microsoft.com/downloads/sdks/platform/tpipv6.asp
Unlessthere is a reason for it, the Windows XP SP1 (or later) and/or Windows Server 2003 implementation should be used for IPv6.
There is no Microsoft implementation of IPv6 in the 95/98/ME line of Microsoft Windows, however there is an IPv6 protocol stack for Windows 95/98 and Windows NT at http://www.trumpet.com.au/winsock/winsoc5.html

How to enable IPv6 in Windows XP (service pack 1 and later) or in Windows Server 2003?

IPv6 is officially supported in XP from Service Pack 1 and later and in Windows Server 2003. Because there are other serious reasons to install service pack 1, the following applies to XP SP1, with the differences noted later.
IPv6 can be installed the same way, as any other network protocol. Go to Control Panel, networks, network connections. Right click on the network connection, choose properties! Then Add, Protocol, Microsoft TCP/IP version 6.
That's all! IPv6 should be up and running. Use the command line utility ipconfig to verify the IPv6 addresses and interfaces.

 

How to enable IPv6 in Windows XP (no service pack)?

On Windows XP, no service pack, IPv6 is not available in the Add protocols dialog, it can be installed by typing ipv6 install on the command line. The ipv6 command can be used to verify operation.
If IPv6 is installed on a machine without service pack, and later upgraded to SP1, ipv6 uninstall is necessary to have IPv6 installable from control panel.

What is new for IPv6 in Windows XP SP2?

Windows XP SP2 includes the updates to IPv6 that are also included in the Advanced Networking Pack for Windows XP plus some bug fixes for IPv6:
; IPv6 ICF : IPv6 Connection Firewall that allows filtering unsolicited incoming IPv6 traffic. ; Teredo : Teredo, also known as IPv6 NAT traversal, is an IPv6/IPv4 transition technology that provides unicast IPv6 connectivity across the IPv4 Internet when the communicating peers are separated by one or more NATs. This is kind of hack that can be avoided most of the cases with proper setup of NAT boxes (i.e.: providing NAT and IPv6 connectivity in the same time). ; Host specific relay : The portproxy is a tool that act as proxies between IPv4 and IPv6 networks and applications

How to enable IPv6 in Windows Vista?

IPv6 is enabled by default in Windows Vista. It can be disabled by uninstalling the IPv6, or different IPv6 features may be enabled or disabled individually by setting the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\DisabledComponents
The value can be the combination (logical or) of the follwoing values:

1
Disable tunnel interfaces

2
Disable 6to4

4
Disable ISATAP

8
Disable Teredo

16
Disable LAN and PPP interfaces

32
Set preference of IPv4 over IPv6

255
Disable IPv6 completely

How can I configure IPv6 on Windows systems

You should use netsh commands in interface ipv6 context to query and configure IPv6 interfaces, address, caches, and routes. As a backward compatibility interface you can use ipv6.exe command (' Note: ipv6.exe command is not available on Windows 2003 machines.').

How can change the address selection policy?

In Windows XP and Windows 2003 you can define address selection defined RFC 3484. For this purpose you can use netsh interface ipv6 command.
  • Adding policy rule

 netsh interface ipv6 set prefixpolicy    

  • Showing policy rules:

 netsh interface ipv6 show prefixpolicy

  • Clearing policy rule table

 netsh interface ipv6 clear prefixpolicy

See some examples in FreeBSD configuration section.

 

What is different in Windows Vista?


Windows Vista supports IPv6 out of the box and it is enabled at installation. There is now graphical user interface for setting basic IPv6 parameters, available through the properties button on the properties panel for the network connection.

Setting IPv6 properties


Using the IPv6 properties pane, manual or automatic address configuration can be selected. Vista will use stateless autoconfiguration to obtain prefix and gateway information or DHCPv6 to obtain DNS server information. On the Advanced Settings pane, multiple addressess and gateway can be selected.
IPv6 parameters can also be set using the

netsh interface ipv6

command. For example to set IPv6 address, the

netsh interface ipv6 add address 5 2001:2000:4030::2

can be used. 4 is the interface index, which can be queried with

netsh interface ipv6 show interface

command. Instead of the interface index, the interface name (such as "Local Area Connection") may be given.

Vista applications


Internet Explorer 7 and Windows Mail (Outlook Express in Vista) supports IPv6, without further configuration. In IE7 it is possible to enter literal IPv6 addresses in the address bar. Windows Mail uses IPv6 if the domain name for the servers resolvs to IPv6






.





 

To install IPv6

1.Open Network Connections
2.Right-click any local area connection, and then click Properties.
3.Click Install.
4.In the Select Network Component Type dialog box, click Protocol, and then click Add.
5.In the Select Network Protocol dialog box, click Microsoft TCP/IP version 6, and then click OK.
6.Click Close to save changes to your network connection.

Note

To open Network Connections, click Start, click Control Panel, click Network and Internet Connections, and then click Network Connections.

How to install and configure IP version 6 in Windows Server 2003 Enterprise Server

This article describes how to install and configure IP version 6 (IPv6) in a Windows Server 2003 Enterprise Edition environment. The current version of IP (which is known as IP version 4 or IPv4) has not been substantially changed since RFC 791 was published in 1981. IPv4 has proven to be robust, easily implemented and interoperable, and has stood the test of scaling an inter-network to a global utility the size of today's Internet. This is a tribute to its initial design.

How to install and uninstall IPv6 in Windows XP

Article ID: 2478747 - View products that this article applies to.
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center

SUMMARY


Internet Protocol Version 6 (IPv6), is the full form of IPv6 which is the "next generation" protocol designed by the IETF to replace the current version Internet Protocol (IP Version 4 ("IPv4")). Windows XP includes IPv6 implementation, but IPv6 must be installed.

MORE INFORMATION


How to install and uninstall IPv6:

To install IPv6 on your Windows XP computer, follow these steps:

Click Start, click All Programs, click Accessories, and then click Command Prompt.

At the command prompt, type netsh int ipv6 install and press the Enter key on your keyboard.

Close the Command Prompt window.


To uninstall IPv6 on your Windows XP computer, follow these steps:

Click Start, click All Programs, click Accessories, and then click Command Prompt.

At the command prompt, type: netsh int ipv6 uninstall and press the Enter key on your keyboard.

Close the Command Prompt window and restart the computer.


For more information about IPv6 click the following links to view the article on the Microsoft website:


http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_ip_v6_pro_inst.mspx?mfr=true


http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_ip_v6_pro_inst.mspx?mfr=true


http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_ip_v6_pro_inst.mspx?mfr=true




IPv4 vs. IPv6

It has been over 90 days since the launch of World IPv6

The complete transition to IPv6 will happen over a period of years, on June 6, major ISPs, home networking equipment manufacturers, and companies around the world, including AT&T, came together to permanently enable IPv6 for their products and services.

IPv4 vs. IPv6

Every device and Web site on the Internet needs an address, known as an Internet Protocol (IP) address, in order to communicate.

* Today's Internet address scheme (IPv4) supports approximately 4 billion unique addresses.
* The new address scheme (IPv6) will provide a virtually unlimited number of IP addresses.
* The full transition to IPv6 will occur slowly.
* Web sites you visit will appear the same, whether hosted by IPv4 or IPv6 addresses.
* Existing devices and networks connected to the Internet will continue to work as they do now.

Preparing for IPv6

In the coming years, the entire Internet ecosystem will need to transition to IPv6. AT&T has already developed and implemented plans to enable IPv6 across their products, services, and network infrastructure for all of Their customers.

For  Residential and Small Business Internet Service Customers

Customers should not need to take any action to prepare for IPv6. Over time, new and replacement home modems, routers, and gateways, peripherals, applications, and operating systems will be enabled to be IPv6 compatible. However, some customer equipment may require upgrades or replacement to reach IPv6-exclusive web sites. AT&T Dial service will support web sites that utilize IPV4, but it will not support IPV6-only web sites. For more information about IPv6 and how it affects customers, visit <http://www.att.com/ipv6> att.com/ipv6<http://att.com/ipv6>.