Remote Desktop Connection to Server.

[jmair]

I had to rebuild my webserver and now I can't remote into it from home. I was able to prior to the rebuild using Remote Desktop Connection.

I can ping the server from home. There are no firewall ports in the way. I can remote into the server while on site, but not from outside the lan.

The website and OWA works fine.

Any ideas?

[Jay]

Assume your Natting, perhaps the rebuilt machine has a different LAN IP?

(Did you give it the same static address as the old one.)

Assuming there is no firewall in the way or on the local machine and RDP is turned on, thats all I can think of.


Edit: Just read the bit about OWA, so assuming the name for RDP is the same, NAT must be working unless your router requires you to specify port when Natting.

[jmair]

Assume your Natting, perhaps the rebuilt machine has a different LAN IP?

(Did you give it the same static address as the old one.)

Assuming there is no firewall in the way or on the local machine and RDP is turned on, thats all I can think of.


Edit: Just read the bit about OWA, so assuming the name for RDP is the same, NAT must be working unless your router requires you to specify port when Natting.

Fixed. For some reason, (I like to blame it most things on the other admin on campus) the port was blocked on the firewall.
Thanks for the help!

[User3204]

If you check "Control Panel" \ "Windows Firewall" is there a rule for "Remote Desktop", and if so check the scope isn't set as your local range.

On the school domain, we set this (via AD/GPO) so that only certain IPs can attach to Servers and (a different range to) clients.

Is there anything in the server eventlog to say why ?
I have had issues with remote access before, because the internal server didn't know the route back to my home machine, which required a lot of fiddling, I had to setup multiple static routes, as I was using a secondary ADSL connection, as our LA block certain ports, such as 3389.. grrr..