Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

i have a Windows Server 2003 machine; with IPv6 enabled:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : newland.local
   IP Address. . . . . . . . . . . . : 192.168.1.244
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   IP Address. . . . . . . . . . . . : 2001:470:████:████:███:████:████:████
   IP Address. . . . . . . . . . . . : fe80::224:1dff:fe86:fdf2%4
   Default Gateway . . . . . . . . . : 192.168.1.1
                                       fe80::250:bfff:fe91:955f%4

i can connect to IIS server using IPv, remotely and locally, using IPv4 and IPv6:

> telnet 127.0.0.1 80                       (connects)
> telnet 192.168.1.244 80                   (connects)
> telnet ::1 80                             (connects)
> telnet fe80::224:1dff:fe86:fdf2 80        (connects)

And TCPView shows that the server is listening on port 80:

enter image description here

Note: This is useful to establish that Windows Server 2003 does have support for IPv6 services.

And i can connect to terminal services, locally and remotely, using IPv4:

> telnet 127.0.0.1 3389                     (connects)
> telnet 192.168.1.244 3389                 (connects)

But i cannot connect to RDP, locally or remotely, over IPv6:

> telnet ::1 3389                           (fails to connect)
> telnet fe80::224:1dff:fe86:fdf2 3389      (fails to connect)

We can see that the system is listening on 3389:

enter image description here

Except why won't it listen on port 3389 (ipv6)?


Unfortunately it's not the firewall. Aside from the fact that i'm connecting locally (in which case the firewall doesn't apply), the firewall doesn't apply:

enter image description here

share|improve this question
add comment

3 Answers

up vote 1 down vote accepted

RDP is limited to listening on 0.0.0.0, which is IPv4. Windows 2003's network stack is based on the Windows XP stack. That stack has IPv6 added as an afterthought and it shows. Windows 2008 has a 'real' IPv6 stack and will offer much better support.

share|improve this answer
add comment

This command will do the trick. netsh interface portproxy add v6tov4 listenport=3389 connectaddress=127.0.0.1 connectport=3389

After using it you'll be able to connect using a recent version of Remote Desktop Client over IPv6 to a WinXP/Win2k3 box.

Regards Viswanathan

share|improve this answer
add comment

Looks like it's a Windows 2003 limitation addressed in 2008.

http://serverfault.com/a/196639/35088

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.