Issues with RDP - Windows Server 2012 R2

[BondiBlue]

I got out a spare machine earlier to use with Windows Server 2012 R2. I installed the OS and other software, and everything went perfectly fine. As normal I enabled RDP access. It's enabled not only for the default admin account (Administrator) but also two other accounts I created. However, none of my other devices can connect to it through RDP. All the devices can see the new server, and it can see everything else, but RDP just won't work. Any ideas? 

 

Connecting to the server from itself (localhost) works fine, and I'm able to log into any available accounts. The server can also access other computers on the network through RDP just fine. This computer will be used remotely (it'll be headless), so RDP access is quite important for me. 

[Oshino Shinobu]

Most likely going to be the firewall. 

 

Disable all firewall profiles and test. If it works, you know it's the firewall. I'd check to see what profile it's using as it might be using the public profile. If so, you'd either need to switch to private or domain or add an inbound rule to allow TCP 3389 to the firewall profile it's using.

[BondiBlue]

2 minutes ago, Oshino Shinobu said:

Most likely going to be the firewall. 

 

Disable all firewall profiles and test. If it works, you know it's the firewall. I'd check to see what profile it's using as it might be using the public profile. If so, you'd either need to switch to private or domain or add an inbound rule to allow TCP 3389 to the firewall profile it's using.

There is no firewall in place. I've got other machines configured identically with no network configuration differences that work fine, so it's something with this one machine. 

[Oshino Shinobu]

1 minute ago, BondiBlue said:

There is no firewall in place. I've got other machines configured identically with no network configuration differences that work fine, so it's something with this one machine. 

Windows firewall

[BondiBlue]

1 minute ago, Oshino Shinobu said:

Windows firewall

Yeah, I haven't configured it. RDP should be working properly right now without having to touch the firewall. 

[Oshino Shinobu]

Just now, BondiBlue said:

Yeah, I haven't configured it. RDP should be working properly right now without having to touch the firewall. 

So it's disabled? If not, disable all the profiles and test. If it doesn't work still, fine, we'll try something else. 

[BondiBlue]

34 minutes ago, Oshino Shinobu said:

So it's disabled? If not, disable all the profiles and test. If it doesn't work still, fine, we'll try something else. 

Ok, it's working now. I didn't change anything, so I don't know what fixed it, but since it's working I'm just going to leave it. I think I'm good for now. 

[Oshino Shinobu]

2 minutes ago, BondiBlue said:

Ok, it's working now. I didn't change anything, so I don't know what fixed it, but since it's working I'm just going to leave it. I think I'm good for now. 

My expectation would be something along the lines of NLA picking up your connection as public and therefor applying the public firewall profile, which even if you have enabled RDP via control panel, it only applies the firewall rules to the private and domain profiles. NLA might have picked up and changed the network to private or domain, depending on if it's domain joined or not and then the firewall rules start working once it's auto switched to one of the profiles with it applied. I've had issues with NLA not detecting my domain before and breaking RDP by applying the public profile on my servers in the past.

 

Good that it's working now at least. 

[BondiBlue]

9 minutes ago, Oshino Shinobu said:

My expectation would be something along the lines of NLA picking up your connection as public and therefor applying the public firewall profile, which even if you have enabled RDP via control panel, it only applies the firewall rules to the private and domain profiles. NLA might have picked up and changed the network to private or domain, depending on if it's domain joined or not and then the firewall rules start working once it's auto switched to one of the profiles with it applied. I've had issues with NLA not detecting my domain before and breaking RDP by applying the public profile on my servers in the past.

 

Good that it's working now at least. 

Hmm, I'll look into it to see what might have happened. This isn't the first machine I've had do this, but this is the first time this Server 2012 R2 image has done it. Strange. Thanks for the help though!