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...
You cannot simultaneously share external ports, so what you have to do is have each PC mapped to unique external ports. You could set up the following rules:
PC1: external port 4000 to internal port 3389 at PC1's internal IP address
PC2: external port 4001 to internal port 3389 at PC2's internal IP address
...
PC5: external port 4004 to internal port 3389 at PC5's internal IP address
Then to connect to each PC, point the RDP client at the appropriate external port and public IP address.
OK, now we're getting somewhere.
The reason for the registry hack was to assign an unique address for each PC (3389, 3390, 3391, etc.). The way the 6850 was setup was that the Local Start/End Port and External Start/End Port were set to that number, and the Local IP was set to the PC IP (like 192.168.0.19). When I use Remote Desktop on my phone, I use mydomain.com:xxxx, where xxxx is 4-digit number I assigned each PC, so www.mydomain.com:3390 would connect me to the machine I setup to use that.
So, do I still need that registry hack? Do I need to do anything on the remote machines?
Update: OK, so I've setup address reservation on the C7000 so that the three main machines are given 'static' addresses. I went to the Port Forwarding setup page and have the following:
Service Name: Name of machine I am connecting to.
Service Type: TCP/UDP (I did try to use only TCP earlier but no joy)
External Starting/Ending Port: 4000
Use the Same Port Range for Internal Port: Unchecked
Internal Starting/Ending Port: 3389
Internal IP Address: Local IP address to the specific machine. Matches what I entered in the Address Reservation for the machine.
External IP Address: Any
I edited the settings in Remote desktop to www.mydomain.com:4000. I tried messing with that Registry setting to match (change 3389 to 4000), but again, nothing.
So at this time, I am either failing to open a needed port or there is a setting elsewhere on the C7000 that needs to be checked/unchecked. At this point, I have no other ports forwarded.
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.