NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot get Remote Desktop to work on C7000-100NAS
OK, so I have switched from the Motorola SURFboard 6850 to the C7000. I cannot get Remote Desktop to work from my Android or WP device. The remote PC is listening on port 3389. I've had to manual...
I don't see anything wrong with your setup. Try looking at netstat -an on your computer. Confirm that RDP is listening on port 3389. You should also see a second entry for a TCP connection whenever you try to connect to your computer. If you don't see the second entry, then the connection is not being established. Are you sure that www.mydomain.com maps to your public IP address? Try using your actual public IP address in your RDP client.
Man, I can't figure this crap out...
So on my server, I ran netstat -an and saw that 80, 443, 3389 were all being listened to.
On my local PC, only 3390 (the port I added via Registry edit), was there; 80, 443, and 3389 were AWOL.
However, according to www.CanYouSeeMe.org, ports 80 and 443 are NOT visible on either machine, whereas 3389/3390 ARE.
I definitely have an issue with my domain not forwarding to my modem/router; using the IP address and port works while using the domain name and port doesn't.
I've been messing with settings for the last couple of hours, include messing with the Registry and rebooting each PC and the C7000, this is what is working thus far:
Service Name: Name of PC (PC1, PC2)
External Starting/Ending Ports: 3389 (PC1), 3390 (PC2)
Use the Same Port Range for Internal Port: Selected
Internal Starting/Ending Ports: 3389 (PC1), 3390 (PC2)
Internal IP Address: IP address of each PC; Each has an address reservation
External IP Address: Any
I swear I was trying these settings out from the very beginning, but now I am thinking that the issue I had was from the redirect not working. I am getting my IP address from Advanced Home ---> Internet Port ---> IP Address/Mask.
So, not sure if all is well or what, but I am going to bed (it's after 5am), and will try this out on some of the other machines.
HailSkate2k5 wrote:Man, I can't figure this crap out...
So on my server, I ran netstat -an and saw that 80, 443, 3389 were all being listened to.
On my local PC, only 3390 (the port I added via Registry edit), was there; 80, 443, and 3389 were AWOL.
Why would you expect your local PC to listen to 3389 when you explicitly overrode RDP to listen to 3390?
Are you running something that listens to ports 80 and 443?
However, according to www.CanYouSeeMe.org, ports 80 and 443 are NOT visible on either machine, whereas 3389/3390 ARE.
How are you forwarding ports 80 and 443 to multiple machines?
I definitely have an issue with my domain not forwarding to my modem/router; using the IP address and port works while using the domain name and port doesn't.
I had a hunch your domain was not working. If you nslookup your domain, do you get your public IP address back?
I've been messing with settings for the last couple of hours, include messing with the Registry and rebooting each PC and the C7000, this is what is working thus far:
Service Name: Name of PC (PC1, PC2)
External Starting/Ending Ports: 3389 (PC1), 3390 (PC2)
Use the Same Port Range for Internal Port: Selected
Internal Starting/Ending Ports: 3389 (PC1), 3390 (PC2)
Internal IP Address: IP address of each PC; Each has an address reservation
External IP Address: Any
Did you try my suggestion of keeping the internal port at 3389 for all PCs and just varying the external port? As I said, my method avoids the need to muck with the registry.
I swear I was trying these settings out from the very beginning, but now I am thinking that the issue I had was from the redirect not working. I am getting my IP address from Advanced Home ---> Internet Port ---> IP Address/Mask.Yeah, that's the right address. Besides, you already proved that using this IP address and port works while the domain name and port does not.
So, not sure if all is well or what, but I am going to bed (it's after 5am), and will try this out on some of the other machines.
It looks like you are pretty close. Port forwarding is working. You just need to fix your domain. Good luck.
Good lord...so much. :)
OK, so nslookup came back with the DNS server, as displayed by the modem on the start page.
The whole thing with using ports 3389, 3390, etc., was setup by a friend of mine who does setups like this. I don't know the "why", I just know that it worked, so I went with it. I didn't know that RDP listened at 3389. If I messed something up, how would I get RDP to go back to listening at 3389 and use different port numbers for each PC?
I did try the 4000/3389 suggestion you made, but because I didn't catch the part about the domain not properly forwarding, I don't remember if it worked. I 'think' it worked on one machine but not another...this whole thing is frustrating as heck- probably why I chose to raise my kids rather than work in the tech field, LOL.
HailSkate2k5 wrote:Good lord...so much. :)
OK, so nslookup came back with the DNS server, as displayed by the modem on the start page.
Hmm. An nslookup of your domain is supposed to return your public IP address, not your DNS server. You need to fix that.
The whole thing with using ports 3389, 3390, etc., was setup by a friend of mine who does setups like this. I don't know the "why", I just know that it worked, so I went with it. I didn't know that RDP listened at 3389. If I messed something up, how would I get RDP to go back to listening at 3389 and use different port numbers for each PC?
The registry entry that you have been modifying specifies the port number that RDP listens to. You can either modify it as your friend did or do it my way. It doesn't matter. You may as well stick with your friend's method if you are more comfortable with it.