netsh interface ipv6

Ipv6 Commands and Links

Cisco Ipv6 | IPv6 utilities | Netsh commands for ipv6 | Reference 2003

Install Ipv6 for Windows Server 2003

c:\>netsh interface ipv6 install

c:\>netsh interface ipv6 show interface level=verbose

Firewall shows: disabled

Verify the new TCP/IP Protocol in Local Area Connection Properties which now shows two TCP/IP Protocols including, Microsoft TCP/IP version 6. Do not uncheck Internet Protocol (TCP/IP).

Click the Advanced tab, place a check in "Protect my computer and network..." for the Internet Connection Firewall with Enterprise Edition only, (ICF) is not included in the 2003 Web Server Edition. With the Firewall on and with TCP/IP Version 6 installed, Windows Messenger continues to work for Video/Voice Chat. The Firewall, not TCP/IP Version 6, may need to be temporarily disabled for file or picture transfers.

c:\>netsh interface ipv6 show help

Router

c:\>netsh interface ipv6 isatap set router 192.168.x.x (Linksys 192.168.1.1)

Then to verify:

c:\>netsh interface ipv6 show state

Response: 6over4 State : default
V4-Compatible Addresses: default

Note: The IPv6 protocol for Windows XP (prior to Service Pack 1) does not support the netsh interface ipv6 isatap set router command. Use the ipv6 rlu command instead.

Too many acronyms? "isatap" is Intra-Site Automatic Tunnel Addressing Protocol.

DNS

By default, the Windows Server 2003 DNS Server service does not listen for DNS traffic sent over IPv6. To enable the DNS Server service to use DNS over IPv6, use the dnscmd /config /EnableIPv6 1 command, and then restart the DNS Server service. Dnscmd.exe is part of Windows Support Tools installed from the \Support\Tools folder on the Windows Server 2003 product CD.

How-To install Windows Support Tools from TechNet: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/tools_howto.asp

Microsoft IPv6 page offers more information on IPv6 technology and its support...
http://www.microsoft.com/windowsserver2003/technologies/ipv6/default.mspx

Privacy

Recommended maximum valid life time is one-day (default is seven-days)

c:\>netsh interface ipv6 set privacy maxvalidlifetime=1d

c:\>netsh interface ipv6 set privacy /? (for all Privacy options)

Conversion Table for changing from ipv6.exe to Windows Server 2003 ipv6 interface commands.

Network Connectivity Troubleshooting

Host names are resolved by using the Hosts file or by querying a DNS server. Problems in the Hosts file usually involve spelling errors and duplicate entries. Use the Nslookup utility or the Netdiag resource kit utility to diagnose host name resolution problems.

A misconfigured subnet mask can result in the system's inability to access any other system on the local subnet while still being able to communicate with remote systems. (DHCP could help to prevent data entry errors in large networks.)
Problems at this point are usually related to an invalid ARP cache (such as a duplicate address) or an invalid subnet mask. If the IP address is local, the Address Resolution Protocol (ARP) is used to identify the destination MAC address. The utilities Arp and Ipconfig can be used to solve local address resolution problems.

Pathping /? Examples: -4 Force using IPv4.
-6 Force using IPv6.

c:\>pathping -i -6 216.95.232.130 (localtech.us)
c:\>pathping -i -6 <your static IP>

Note: To determine why a remote host name cannot be resolved, first determine whether the remote computer is being addressed using NetBIOS or Sockets. If the application uses the Net commands or is an NT 4.0 version administrator tool, it is a NetBIOS problem. Try the net view command.

If the net view <hostname> command works, name resolution is not the source of the problem.

To confirm this, check the status of the temporary session that NetBIOS creates by entering the Net view command with the syntax shown: net view <ip_address> where ip_address is the IP address of the same computer used in the previous example. If this command fails, the problem is in establishing a session. If the Net View utility fails with both hostname and ip_address, a likely culprit is that the computer is not running the File and Printer Sharing for Microsoft Networks service.

If the application uses WinSock (like Telnet, FTP, and Web browsers) the problem will lie with DNS or the Hosts file. Microsoft Root Hints files (SRV files) are listed under the DNS Zone in Active Directory DNS, if the files are not there, DNS will not work.

Each of the following "subfolders" must be present in the Active Directory DNS zone. There will be DNS Service (SRV) records in these "subfolders".

_MSDCS
_SITES
_TCP
_UDP

Can you ping the static or dynamic IP of other computers in your Intranet? How-To allow incoming echo requests for Windows XP and Windows Server 2003 Enterprise Edition:

If you are using the built-in Firewall (ICF), Click Start --> Connect To --> Show All Connections --> Local Area Connection --> Properties --> choose the Advanced tab --> Settings --> the ICMP tab --> and "Allow incoming echo requests".

Ad Agency | Search | Home | Background | Frames Page

Veterans Here