RDP on Local Network Failure

[babcocca]

Hello all!

I have been experiencing a problem with RDP on port 3389.

I always connect by IP address and have zero trouble connecting to it using other routers.

I am using 192.168.1.x/24 for my network.

Can anyone help? What is different about the Almond+ in this scenario from other routers?

[LGNilsson]

I've passed this on to the software team to investigate if there's an issue on our side.

[eldaria]

I normally run Linux and Mac, but on my server I have some Windows guests that I use for various testing.

You don't give so much details to your network setup, so I will have to makes some assumptions along the way.

My setup is as following:


I tested on 3 images.
Windows 7 Ultimate
Windows 8.1
Windows Server 2003

Since the guests are normally NAT'ed at the server and do not normally get an external IP, I re-configured them with Bridge networking so that they will get an IP from the Almond+ instead.
Since the network changed, by default both Windows 7 and Windows 8 assumed the new network was insecure, so I had to also configure the firewall to trust the network.

However, after this, I was able to connect to all of them without any issues.

So I suspect that it is a firewall issue on your end.
One reason could be that many routers by default use the 192.168.1.0/24 range, and by default the Almond+ use 10.10.10.0/24 both are valid ranges for a local network, but perhaps Windows thinks that the new network is not secure and enables the firewall, and therefore you are not able to connect.
Check your network setting on the Windows computer under Network and Sharing.

[babcocca]

Thank you for the effort! My server is headless. I had forgotten about Windows doing a query about what type of network (Work, Home, Public) a network is when a new one is detected. Until you answer this question, most ports are automatically closed! Duh!

Once I connected a monitor to the server, I saw the problem right away.

Thank you all!