HowTo connect: IPv4, IPv6, DNS, portnumber

The AADServer

In this example we use an AADServer running on Windows 7 x64. The AADServer is joined to the domain:

IP Addresses on the AADServer: the "83"

IPv4

IPv6

AADServer: ping yourself

Before we proceed, check, double check that the IP Addresses on the Server are working OK:

• Open a DOS-BOX on the Server, and let the server ping itself on IPv4 and IPv6.

AADServer: settings for IPv4, IPv6 and portnumber

On the AADServer: enable both IPv4 and IPv6 and enter the "correct" RDP portnumber

• In this example we will be using both IPv4 and IPv6.
• In this example we use a non-default port number 8933.

Client Windows 10: the "94"

We have a Windows 10 Client PC with the following IP Addresses:

IPv4

IPv6

Windows 10 Client: ping yourself

Before we proceed, check, double check that the IP Addresses on the Windows 10 Client are working OK:

• Open a DOS-BOX on the Windows 10 Client, and let the Windows 10 Client ping itself on IPv4 and IPv6.

Client LinuxLite: the "96"

We have a LinuxLite Client PC with the following IP Addresses:

IPv4

IPv6

LinuxLite Client: ping yourself

Before we proceed, check, double check that the IP Addresses on the LinuxLite Client are working OK:

• Open a TERMINAL on the LinuxLite Client, and let the LinuxLite Client ping itself on IPv4 and IPv6.

Test the connection from the Clients to the Server

Window 10 Client: ping the IPv4 and IPv6 address of the AADServer:

Window 10 Client: ping the DNS Name of the AADServer:

LinuxLite Client: ping the IPv4 and IPv6 address of the AADServer:

LinuxLite Client: ping the DNS Name of the AADServer:

AADS Client

Windows 10 Client

Window 10 Client, connect using IPv4:

Window 10 Client, connect using IPv6:

[FD00::1:53]:8933

Because a portnumber needs to be specified, the IPv6 address is enclosed in sqare brackets. See RFC 3986 , section 3.2.2 and section 3.2.3

Windows 10 Client, connect using DNS, using IPv4

Windows 10 Client, connect using DNS, using IPv6:

Windows 10 Client, connect using DNS, using "default":

Currently default equals to IPv4 (Sep 2018). In the future this might change to IPv6.

LinuxLite Client

LinuxLite Client, connect using IPv4:

LinuxLite Client, connect using IPv6:

[FD00::1:53]:8933

Because a portnumber needs to be specified, the IPv6 address is enclosed in sqare brackets. See RFC 3986 , section 3.2.2 and section 3.2.3

LinuxLite Client, connect using DNS, using IPv4

LinuxLite Client, connect using DNS, using IPv6:

LinuxLite Client, connect using DNS, using "default":

Currently default equals to IPv4 (Sep 2018). In the future this might change to IPv6.

AADServer: connection log

If all is well, the AADServer will show the connections in the logging:

If there are problems while attempting to connect, check, double check all steps in this FAQ, or see the Connection Problems FAQ.