The Windows .NET Server 2003 family includes the following IPv6-enabled components and applications:
The new Windows Internet Extensions dynamic link library, Wininet.dll, enables Web browsers to access IPv6-enabled Web servers. For example, Wininet.dll is used by Microsoft Internet Explorer to make connections with a Web server to view Web pages. Internet Explorer uses IPv6 to download Web pages when the DNS query for the name of the Web server in the URL returns an IPv6 address.
URLs that use the format for literal IPv6 addresses described in RFC 2732, "Format for Literal IPv6 Addresses in URLs," are not supported by the version of Internet Explorer provided with the Windows .NET Server 2003 family.
The Telnet client, Telnet.exe, can be used to establish Telnet sessions with both IPv4 and IPv6 Telnet servers. There are no special command line options for IPv6 support. Telnet.exe attempts to connect to the Telnet server based on either the address specified on the Telnet.exe command line or an address obtained from DNS name resolution. If the address typed at the command line or the address returned from DNS name resolution is an IPv6 address, Telnet.exe attempts a session with an IPv6-enabled Telnet server.
The Windows .NET Server 2003 family does not include support for an IPv6-enabled Telnet server. However, PortProxy can be used to proxy IPv6 Telnet traffic from Telnet.exe to the IPv4-only Telnet server component provided with the Windows .NET Server 2003 family. For more information about PortProxy, see the section entitled "PortProxy" in Chapter 11, "Coexistence and Migration."
The FTP client, Ftp.exe, can be used to establish FTP sessions with IPv4 and IPv6 FTP servers. Like the Telnet client, there are no special Ftp.exe command line options for IPv6 support. Ftp.exe attempts to connect to the FTP server based on either the address specified on the Ftp.exe command line or an address obtained from DNS name resolution. If the address typed at the command line or the address returned from DNS name resolution is an IPv6 address, Ftp.exe attempts an FTP session with an IPv6-enabled FTP server.
The Windows .NET Server 2003 family does not include an IPv6-enabled FTP server, and because the FTP protocol uses embedded IPv4 addresses within FTP messages, the PortProxy component cannot be used to proxy IPv6 FTP traffic from Ftp.exe to the IPv4-only FTP server component of Internet Information Services (IIS) provided with the Windows .NET Server 2003 family.
IIS provided with the Windows .NET Server 2003 family includes an IPv6-enabled HTTP server, also known as a Web server. IIS in the Windows .NET Server 2003 family will accept HTTP-based Web requests sent over IPv6 from any IPv6-enabled HTTP client, such as Microsoft Internet Explorer.
The Windows .NET Server 2003 family includes support for file and print sharing using the Microsoft Common Internet File System (CIFS), also known as the Server Message Block (SMB) protocol. File- and printer-sharing connections made from the Windows Explorer, Printers within Control Panel, or from the command line by using the Net.exe utility use IPv6 when the server name within the Universal Naming Convention (UNC) name of the file or printer share is resolved to an IPv6 address. All file- and printer-sharing connections over IPv6 use TCP port 445.
To provide security for file and print resources, file- and-printer-sharing resources are available only within the site.
Windows Media Services is a digital media platform that allows you to deliver Advanced Streaming Format (ASF) content in a variety of different ways, based on your own needs and the capabilities or limitations of your network. Content can be delivered either live or pre-recorded, and either multicast or unicast. Windows Media Services in the Windows .NET Server 2003 family is IPv6-enabled, allowing you to stream ASF content over IPv6.
The versions of Network Monitor provided with the Windows .NET Server 2003 family, Systems Management Server 2.0, and Windows 2000 support the parsing of IPv6 traffic.
The Windows .NET Server 2003 family includes Simple Network Management Protocol (SNMP) support for the following IPv6 management information bases (MIBs):
Although the MIBs included in the Windows .NET Server 2003 family support IPv6 elements, SNMP traffic is supported only over IPv4.