|
I have been running DynDNS for over a month now and have had no problems until this week. Starting yesterday I have not been able to remote desktop to my home PC. I've checked my ports on the system I'm trying to remote into and they are all OK. Forwarding on my router is properly set and when I run the open port tool for 3389 it comes back as open. I'm able to ftp files from that remote system just can't remote desktop to it. Any help would be much appreciated. |
|
Unfortunately it's hard to give any more specific guidance at this point. Have you been testing from outside your network? When you did, what kind of network did you test from? A home Internet connection or a corporate business network? When it worked at some point, did you connect from outside the network then as well? What Windows version were you running on the client computer (which you connected from)? Yes I'm able to remote in to the box from inside my local network. I turned off the firewall and tried to connect to the box using my hostname from inside my local network and that didnt work. I'm only using windows firewall(win7 OS btw) and I verified that remote desktop was allowed.
Oct 20 at 09:06 PM
pablob
The only test I've done outside of of my network is simply trying to connect using remote desktop. The test that I did inside of my network is using the "Open Port Tool" in the tools tab in the support page. Yes when it was working it was to connect to my home system from my corporate box.
Oct 21 at 01:22 PM
pablob
Sorry for the long delay for a response, was in an accident. Both boxes are running win7.
Oct 25 at 01:25 PM
pablob
|
|
if you have more than on terminal within your home network you should verify the ip assigned to the terminal you want to connect, run ipconfig and verify you got the right ip in your router port forwards, if you havent changed any settings and you suddenly lost connection, this is probably your answer. I run a script that every time my system boots I capture the IP address and I verify that it's the same IP address each time(plus I visually checked the IP address myself and it's still correct).
Oct 21 at 01:25 PM
pablob
|
|
I can see both the VNC and Remote Desktop ports are showing as open, this means something is responding (though I haven't tried connecting). Have you tested Remote Desktop from another home user connection You must do all testing (using a Remote Desktop Client, not the Open Port tool) from outside your network, tests from inside using the WAN IP or DynDNS hostname prove nothing. When you're at your friends use a Remote Desktop client to try to connect to your hostname (having ensured you've left your desktop switched on so you can connect to it). Testing from work computers can often give unpredictable results since those networks tend to be more restrictive. Testing from another home user connection is always the way to do it. I've tried the WAN IP as well but alas no connection.
Oct 20 at 09:02 PM
pablob
Interesting. I will try uninstalling and reinstalling remote desktop to see if that helps. Good suggestion, hadnt thought of that.
Oct 21 at 01:29 PM
pablob
I wasnt able to find a way to uninstall/reinstall only turn on/off. I installed tightvnc and that works fine. http://pablob.dyndns.info is my host name
Oct 21 at 01:53 PM
pablob
No I've only forwarded port 3389 to just the one system. I'm going to try connecting from a relatives house tonight to try to rule out any port blocking from my corporate router/firewall. Although that is exactly why I tested using my hostname from another computer inside my home network. I digress if I'm still not able to connect from my relatives house then I'll setup port forwarding to another of my systems at home and try that as well.
Oct 21 at 04:36 PM
pablob
I finally got to my friends house this weekend and I was able to connect fine from there. I tried reconnecting again today from my work computer and it's working again. Strange. I made no changes to my home setup.
Oct 25 at 01:27 PM
pablob
|
