IPv6-enabled Utilities

The Windows .NET Server 2003 family includes the following IPv6-enabled command line utilities:

  • Ipconfig
  • Route
  • Ping
  • Tracert
  • Pathping
  • Netstat

Ipconfig

The Ipconfig utility is used to display all current TCP/IP network configuration values and to perform maintenance tasks such as refreshing DHCP and DNS settings. In the Windows .NET Server 2003 family, Ipconfig used without parameters displays IPv4 and IPv6 configuration for all physical adapters and tunnel interfaces that have addresses.

The following is an example display of the Ipconfig utility on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection:    Connection-specific DNS Suffix  . : example.microsoft.com    IP Address. . . . . . . . . . . . : 157.60.137.151    Subnet Mask . . . . . . . . . . . : 255.255.252.0    IP Address. . . . . . . . . . . . : fec0::f282:204:5aff:fe56:1006%1    IP Address. . . . . . . . . . . . : 3ffe:2900:d005:f282:b8df:3ec8:8a61:a06b    IP Address. . . . . . . . . . . . : 3ffe:2900:d005:f282:204:5aff:fe56:1006    IP Address. . . . . . . . . . . . : fe80::204:5aff:fe56:1006%3    Default Gateway . . . . . . . . . : 157.60.136.1                                        fe80::210:ffff:fed6:58c0%3 Tunnel adapter Automatic Tunneling Pseudo-Interface:    Connection-specific DNS Suffix  . : example.microsoft.com    IP Address. . . . . . . . . . . . : fe80::5efe:157.60.137.151%2    Default Gateway . . . . . . . . . : 

For more information about Ipconfig command line options, search for "ipconfig" in the Windows .NET Server Help and Support Center.

Route

The Route utility displays and modifies the entries in the local routing tables. The Route utility has been enhanced in the Windows .NET Server 2003 family to display both the IPv4 and IPv6 routing table when you execute the route print command.

The following is an example display of the route print command on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>route print IPv4 Route Table ===================================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x10003 ...00 04 5a 56 10 06 ...... Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4) ===================================================================================== ===================================================================================== Active Routes: Network Destination          Netmask            Gateway          Interface    Metric           0.0.0.0            0.0.0.0       157.60.136.1     157.60.137.151        20         127.0.0.0          255.0.0.0          127.0.0.1          127.0.0.1         1      157.60.136.0      255.255.252.0     157.60.137.151     157.60.137.151        20    157.60.137.151    255.255.255.255          127.0.0.1          127.0.0.1        20    157.60.255.255    255.255.255.255     157.60.137.151     157.60.137.151        20         224.0.0.0          240.0.0.0     157.60.137.151     157.60.137.151        20   255.255.255.255    255.255.255.255     157.60.137.151     157.60.137.151         1 Default Gateway:        157.60.136.1 ===================================================================================== Persistent Routes:   None IPv6 Route Table ===================================================================================== Interface List   3 ...00 04 5a 56 10 06 ...... Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)   2 ...9d 3b 89 97 ............ Automatic Tunneling Pseudo-Interface   1 ........................... Loopback Pseudo-Interface ===================================================================================== ===================================================================================== Active Routes:  If Metric Network Destination      Gateway   2      5 fe80::5efe:157.60.137.151/128                                     fe80::5efe:157.60.137.151   3      4 fec0::f282:204:5aff:fe56:1006/128                                     fec0::f282:204:5aff:fe56:1006   3      8 fec0:0:0:f282::/64       On-link   3      4 3ffe:2900:d005:f282:b8df:3ec8:8a61:a06b/128                                     3ffe:2900:d005:f282:b8df:3ec8:8a61:a06b   3      4 3ffe:2900:d005:f282:204:5aff:fe56:1006/128                                     3ffe:2900:d005:f282:204:5aff:fe56:1006   3      8 3ffe:2900:d005:f282::/64 On-link   3    256 ::/0                     fe80::210:ffff:fed6:58c0   3      8 ff00::/8                 On-link   3      4 fe80::204:5aff:fe56:1006/128                                     fe80::204:5aff:fe56:1006   1      4 ::1/128                  ::1   1      8 ff00::/8                 On-link   1      4 fe80::1/128              fe80::1 ===================================================================================== Persistent Routes:   None 

For more information about Route command line options, search for "route" in the Windows .NET Server Help and Support Center.

Ping

In previous versions of Windows, the Ping utility verified IPv4-level connectivity to another TCP/IP computer by sending Internet Control Message Protocol (ICMP) Echo messages. The receipt of corresponding Echo Reply messages is displayed, along with round-trip times. Ping is the primary TCP/IP utility used to troubleshoot reachability and name resolution.

The Ping utility in the Windows .NET Server 2003 family has been enhanced to support IPv6 in the following ways:

  • Ping uses either ICMPv4 Echo or ICMPv6 Echo Request messages to verify IP-connectivity.
  • Ping can parse both IPv4 and IPv6 address formats.
  • If you specify a target host by name, the addresses returned by using Windows name resolution techniques can contain both IPv4 and IPv6 addresses, in which case, by default, an IPv6 address is used first.

The following is an example display of the Ping utility on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>ping fec0::f282:2b0:d0ff:fee9:4143%1 Pinging fec0::f282:2b0:d0ff:fee9:4143%1 from fec0::f282:204:5aff:fe56:1006%1 with 32 bytes of data: Reply from fec0::f282:2b0:d0ff:fee9:4143: time<1ms Reply from fec0::f282:2b0:d0ff:fee9:4143: time<1ms Reply from fec0::f282:2b0:d0ff:fee9:4143: time<1ms Reply from fec0::f282:2b0:d0ff:fee9:4143: time<1ms Ping statistics for fec0::f282:2b0:d0ff:fee9:4143:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 0ms, Maximum = 0ms, Average = 0ms 

The following command line options support IPv6:

  • -i HopLimit

    Sets the value of the Hop Limit field in the IPv6 header. The default value is 128. The -i option is also used to set the value of the TTL field in the IPv4 header.

  • -R

    Forces Ping to trace the round-trip path by sending the ICMPv6 Echo Request message to the destination and include an IPv6 Routing extension header with the sending node as the next destination.

  • -S SourceAddr

    Forces Ping to use a specified IPv6 source address.

  • -4

    Forces Ping to use an IPv4 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

  • -6

    Forces Ping to use an IPv6 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

The Ping -f, -v TOS, -r count, -s count, -j host-list, and -k host-list command line options are not supported for IPv6.

When you specify a destination IPv6 address for a Ping, Tracert, or Pathping command, you might have to specify a zone ID as part of the address. The zone ID specifies the zone of the destination for Echo Request messages. The syntax for specifying a zone ID is: IPv6Address%ZoneID, in which ZoneID is an integer value. For typical link-local addresses, ZoneID is equal to the interface index, as displayed by the output of the netsh interface ipv6 show interface command. For site-local addresses, ZoneID is equal to the site number, as displayed in the output of the netsh interface ipv6 show interface level=verbose command (the "Zone ID for Site" property). If multiple sites are not being used, a zone ID for site-local addresses is not required. The ZoneID parameter is not required when the destination is a global address.

For more information about Ping command line options, search for "ping" in the Windows .NET Server Help and Support Center.

Tracert

The Tracert utility determines the path taken to a destination. For IPv4, Tracert sends ICMPv4 Echo messages to the destination with incrementally increasing Time-to-Live (TTL) field values. For IPv6, Tracert sends ICMPv6 Echo Request messages to the destination with incrementally increasing Hop Limit field values. The path displayed is the list of nearside router interfaces of the routers in the path between a source host and a destination node.

The Tracert utility in the Windows .NET Server 2003 family has been enhanced to support IPv6 in the following ways:

  • Tracert can parse both IPv4 and IPv6 address formats.
  • If you specify a target host by name, the addresses returned using Windows name resolution techniques can contain both IPv4 and IPv6 addresses, in which case, by default, an IPv6 address is used first.

The following is an example display of the Tracert utility on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>tracert fec0::f282:2b0:d0ff:fee9:4143%1 Tracing route to fec0::f282:2b0:d0ff:fee9:4143%1 over a maximum of 30 hops   1    <1 ms    <1 ms    <1 ms  fec0::f241:2b0:d0ff:fea4:243d   2    <1 ms    <1 ms    <1 ms  fec0::f2ac:2b0:d0ff:fea5:d347   3    <1 ms    <1 ms    <1 ms  fec0::f282:2b0:d0ff:fee9:4143 Trace complete. 

The following Tracert command line options support IPv6:

  • -R

    Forces Tracert to trace the round-trip path by sending the ICMPv6 Echo Request message to the destination, including an IPv6 Routing extension header with the sending node as the next destination.

  • -S SourceAddr

    Forces Tracert to use a specified IPv6 source address.

  • -4

    Forces Tracert to use an IPv4 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

  • -6

    Forces Tracert to use an IPv6 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

The Tracert -j host-list command line option is not supported for IPv6.

For more information about Tracert command line options, search for "tracert" in the Windows .NET Server Help and Support Center.

Pathping

The Pathping utility provides information about network latency and network loss at intermediate hops between a source and destination. For IPv4, Pathping sends multiple ICMPv4 Echo messages to each router between a source and destination over a period of time, and then computes results based on the packets returned from each router. For IPv6, Pathping sends ICMPv6 Echo Request messages. Because Pathping displays the degree of packet loss at any given router or link, you can determine which routers or subnets might be having network problems. Pathping performs the equivalent of the Tracert utility by identifying which routers are in the path, and then sends messages periodically to all of the routers over a specified time period and computes statistics based on the number returned from each.

The Pathping utility in the Windows .NET Server 2003 family has been enhanced to support IPv6 in the following ways:

  • Pathping can parse both IPv4 and IPv6 address formats.
  • If you specify a target host by name, the addresses returned using Windows name resolution techniques can contain both IPv4 and IPv6 addresses, in which case, by default, an IPv6 address is used first.

The following is an example display of the Pathping utility on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>pathping fec0::f282:2b0:d0ff:fee9:4143%1 Tracing route to fec0::f282:2b0:d0ff:fee9:4143%1 over a maximum of 30 hops   0  server1.example.microsoft.com [fec0::f282:204:5aff:fe56:1006%1]   1  fec0::f282:2b0:d0ff:fee9:4143 Computing statistics for 25 seconds...             Source to Here   This Node/Link Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address   0                                           server1.example.microsoft.co m [fec0::f282:204:5aff:fe56:1006%1]                                 0/ 100 =  0%   |   1    0ms     0/ 100 =  0%     0/ 100 =  0%  fec0::f282:2b0:d0ff:fee9:4143%1 Trace complete. 

The following Pathping command line options support IPv6:

  • -4

    Forces Pathping to use an IPv4 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

  • -6

    Forces Pathping to use an IPv6 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.

The Pathping -g host-list command line option is not supported for IPv6.

For more information about Pathping command line options, search for "pathping" in the Windows .NET Server Help and Support Center.

Netstat

The Netstat utility is used to display active TCP connections, ports on which the computer is listening, Ethernet statistics, the IPv4 routing table, IPv4 statistics (for the IP, ICMP, TCP, and UDP protocols), the IPv6 routing table, and IPv6 statistics (for the IPv6, ICMPv6, TCP over IPv6, and UDP over IPv6 protocols).

The following is an example display of the Netstat utility on a computer running a member of the Windows .NET Server 2003 family with the IPv6 protocol installed:

 F:\>netstat -s IPv4 Statistics   Packets Received                   = 187107   Received Header Errors             = 0   Received Address Errors            = 84248   Datagrams Forwarded                = 0   Unknown Protocols Received         = 0   Received Packets Discarded         = 0   Received Packets Delivered         = 186194   Output Requests                    = 27767   Routing Discards                   = 0   Discarded Output Packets           = 0   Output Packet No Route             = 0   Reassembly Required                = 0   Reassembly Successful              = 0   Reassembly Failures                = 0   Datagrams Successfully Fragmented  = 0   Datagrams Failing Fragmentation    = 0   Fragments Created                  = 0 IPv6 Statistics   Packets Received                   = 53118   Received Header Errors             = 0   Received Address Errors            = 0   Datagrams Forwarded                = 0   Unknown Protocols Received         = 0   Received Packets Discarded         = 0   Received Packets Delivered         = 0   Output Requests                    = 60695   Routing Discards                   = 0   Discarded Output Packets           = 0   Output Packet No Route             = 0   Reassembly Required                = 0   Reassembly Successful              = 0   Reassembly Failures                = 0   Datagrams Successfully Fragmented  = 0   Datagrams Failing Fragmentation    = 0   Fragments Created                  = 0 ICMPv4 Statistics                             Received    Sent   Messages                  682         881   Errors                    0           0   Destination Unreachable   2           201   Time Exceeded             0           0   Parameter Problems        0           0   Source Quenches           0           0   Redirects                 0           0   Echos                     340         340   Echo Replies              340         340   Timestamps                0           0   Timestamp Replies         0           0   Address Masks             0           0   Address Mask Replies      0           0 ICMPv6 Statistics                             Received    Sent   Messages                  309         80   Errors                    0           0   Destination Unreachable   193         0   Echos                     4           0   Echo Replies              0           4   MLD Reports               0           6   Router Solicitations      0           7   Router Advertisements     54          0   Neighbor Solicitations    31          32   Neighbor Advertisements   27          31 TCP Statistics for IPv4   Active Opens                        = 128   Passive Opens                       = 106   Failed Connection Attempts          = 0   Reset Connections                   = 3   Current Connections                 = 16   Segments Received                   = 22708   Segments Sent                       = 26255   Segments Retransmitted              = 37 TCP Statistics for IPv6   Active Opens                        = 74   Passive Opens                       = 72   Failed Connection Attempts          = 1   Reset Connections                   = 0   Current Connections                 = 14   Segments Received                   = 52809   Segments Sent                       = 59813   Segments Retransmitted              = 3 UDP Statistics for IPv4   Datagrams Received    = 160982   No Ports              = 2158   Receive Errors        = 2   Datagrams Sent        = 591 UDP Statistics for IPv6   Datagrams Received    = 0   No Ports              = 0   Receive Errors        = 0   Datagrams Sent        = 744 

For more information about Netstat command line options, search for "netstat" in the Windows .NET Server Help and Support Center.



Understanding IPv6
Understanding Ipv6
ISBN: 0735612455
EAN: 2147483647
Year: 2005
Pages: 124
Authors: Joseph Davies

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net