Windows 2008 server Std 32 bit - Remote access through Dyndns is no longer available

Typically Dyndns will be handled by your firewall. You link your account to what ever the hostname of DYNDNS is. I use Dyndns, otherwise no-ip works to. Secondly you need to make sure port 3389 is forwarded to the server through the firewall. I do not recommend to do this since it is a security risk. A better way would be to use a VPN.

Use www.ipchicken.com to verify your WAN IP, then log into your Dyn account and verify that it matches.

- if you connect to server from a local computer (target = local IP of server, or DNS hostname), it may be the server has RDP protocol allowed for corporate identified network.

- if you connect to server from a remote location (target = router's and/or firewall's public IP), in which case you need to ensure RDP protocol is allowed and correctly forwarded to server's local IP. On server, check RDP Protocol is allowed on internal firewall for every network location (home/public/corporate)

Ok, I logged into the server with Logmein as the domain admin.

I launched IPchicken and verified the IP I tried was exact. I verified the dyndns IP matched.

I checked the RDP manager service and it is auto and running. I opened RDP manager and say the user who reported the problem had an active session from 70 days ago but was disconnected. I reset that session and it was auto deleted. i tried conencting from my off site office with rdp using the IP and then the dyndns name, and received the same message  "compuyer cannot connect".

They have a Sonicwall TZ185 firewall, found the RDP settings. they have the remote user's IP and it is correct. Mine is listed also and it's correct. The IP listed for the server and firwall in each line is correct.  

I maintain all changes and the firewall has not been logged into or changed in about a year. I logged into it today and found in the log where the client's connection was being rejected.

http://www.yougetsignal.com/tools/open-ports/

Type in 3389 and your IP. Verify it is open

Temporally disable firewall on the server and try again.

It says the firewall is not open, but I have rules in the firewall to only allow a connection from specific user addreses.

I'm going to see if the AV is blocking it. We installed a new version a month ago. I'll let you know.

I worked on this server yesterday. I discovered one user was originally setup to use a pptp-vpn from her home Pc. I logged into her pc and it's an XP box with the generic Windows PPTP-VPN client setup.

I've checked the Comcast modem and it's set to allow port forwarding for RDP on port 3390 and forward to the Sonicwall TZ180 firewall. We still cannot login through RDP. I'm waiting to hear frm Comcast to see if they added a port 3389 block.

Any other ideas?

While this user is logged into the server using a PPTP-VPN, does that stop anyone else from logging into the server using Windows RDP?

Since you said their IP changed, you might also want to make sure the firewall rules are not set to the old IP, either on the soncwall or the modem (since it sounds like it has some firewall capabilities itself).

To asnwer your other question, PPTP won't interfere with RDS since they are on separate ports.

Sorry, I didn;t mean their IP changed. From what I've checked it didn't change.

Youwill need to close the question yourself. If none of us helped, you can accept your own answer as the solution. However, if you did anything to fix the problem, please provide a brief description to help others who may be searching on a similar problem.

No solution I received worked.