Windows Server 2003 RDP not listening on IPv6

Posted by Ian Boyd on Server Fault See other posts from Server Fault or by Ian Boyd
Published on 2012-03-29T23:15:41Z Indexed on 2012/03/30 5:32 UTC
Read the original article Hit count: 557

Filed under:

windows-server-2003

|

rdp

|

terminal-server

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

Developer IT