Guest DiFFeReNT Posted October 24, 2007 Posted October 24, 2007 I've followed the instructions found all over the internet on how to change my remote desktop port via the registry, and it works great, over the network. All I have to do is ipaddress:3390. Unfortunately, this will not work over the internet. I have setup port forwarding for TCP (and UDP) port 3390 to forward to my computer, which has a static IP address, the same way that I have port 3389 successfully forwarded to another computer. I also manually opened the port 3390 on the Windows firewall. Remote desktop won't connect using the port 3390. When I run the port test at http://canyouseeme.org/, it says Error and Request Timed Out. Since my port forwarding settings are setup correctly, is there any setting on the computer (server 2003) that is preventing remote desktop on port 3390 over the internet? Thanks in advance.
Guest Robert L. \(MS-MVP\) Posted October 25, 2007 Posted October 25, 2007 Re: Change Remote Desktop Port Do a simple test. Can you telnet port 3390? -- Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "DiFFeReNT" <ChrisLampson@gmail.com> wrote in message news:1193266711.267062.54910@t8g2000prg.googlegroups.com... > I've followed the instructions found all over the internet on how to > change my remote desktop port via the registry, and it works great, > over the network. > > All I have to do is ipaddress:3390. > > Unfortunately, this will not work over the internet. > > I have setup port forwarding for TCP (and UDP) port 3390 to forward to > my computer, which has a static IP address, the same way that I have > port 3389 successfully forwarded to another computer. > I also manually opened the port 3390 on the Windows firewall. > > Remote desktop won't connect using the port 3390. > When I run the port test at http://canyouseeme.org/, it says Error and > Request Timed Out. > > Since my port forwarding settings are setup correctly, is there any > setting on the computer (server 2003) that is preventing remote > desktop on port 3390 over the internet? > > Thanks in advance. >
Guest Pegasus \(MVP\) Posted October 25, 2007 Posted October 25, 2007 Re: Change Remote Desktop Port "DiFFeReNT" <ChrisLampson@gmail.com> wrote in message news:1193266711.267062.54910@t8g2000prg.googlegroups.com... > I've followed the instructions found all over the internet on how to > change my remote desktop port via the registry, and it works great, > over the network. > > All I have to do is ipaddress:3390. > > Unfortunately, this will not work over the internet. > > I have setup port forwarding for TCP (and UDP) port 3390 to forward to > my computer, which has a static IP address, the same way that I have > port 3389 successfully forwarded to another computer. > I also manually opened the port 3390 on the Windows firewall. > > Remote desktop won't connect using the port 3390. > When I run the port test at http://canyouseeme.org/, it says Error and > Request Timed Out. > > Since my port forwarding settings are setup correctly, is there any > setting on the computer (server 2003) that is preventing remote > desktop on port 3390 over the internet? > > Thanks in advance. > Building on what Robert suggested: You should perform four tests: - Telnet internally to PC1 on port 3389 - Telnet internally to PC2 on port 3390 - Telnet externally on port 3389 - Telnet externally on port 3390 You should also run the command netstat -an to see which ports are open.
Guest Chris M Posted October 25, 2007 Posted October 25, 2007 Re: Change Remote Desktop Port DiFFeReNT wrote: > I've followed the instructions found all over the internet on how to > change my remote desktop port via the registry, and it works great, > over the network. > > All I have to do is ipaddress:3390. > > Unfortunately, this will not work over the internet. > > I have setup port forwarding for TCP (and UDP) port 3390 to forward to > my computer, which has a static IP address, the same way that I have > port 3389 successfully forwarded to another computer. > I also manually opened the port 3390 on the Windows firewall. > > Remote desktop won't connect using the port 3390. > When I run the port test at http://canyouseeme.org/, it says Error and > Request Timed Out. > > Since my port forwarding settings are setup correctly, is there any > setting on the computer (server 2003) that is preventing remote > desktop on port 3390 over the internet? The Windows Firewall exception - When you added it, what scope did you choose? By default I think the scope is set to the local network. If you didn't change it, you need to go back in and change the scope. -- Chris.
Guest DiFFeReNT Posted October 25, 2007 Posted October 25, 2007 Re: Change Remote Desktop Port PC1 = 192.168.1.98, 3389 PC2 = 192.168.1.99, 3390 > > Telnet internally to PC1 on port 3389 > Telnet internally to PC2 on port 3390 > Telnet externally on port 3389 > Telnet externally on port 3390 > I tried this using PuTTy, but was unsuccessful. I'm probably doing something wrong (use PuTTy for SSH to linux box). > > netstat -an > (on PC2) Proto Local Address Foreign Address State TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED (the second is me connected on the LAN; there is no monitor plugged into the PC) > > The Windows Firewall exception - When you added it, what scope did you > choose? By default I think the scope is set to the local network. If you > didn't change it, you need to go back in and change the scope. > Exceptions Tab: - 3390, TCP, Internet (scope) Advanced Tab > Advanced Settings > Service Settings: - ip on network: 192.168.1.99, 3390, TCP
Guest Pegasus \(MVP\) Posted October 25, 2007 Posted October 25, 2007 Re: Change Remote Desktop Port Looks like port 3390 is fine but there is no report about port 3389. See below. "DiFFeReNT" <ChrisLampson@gmail.com> wrote in message news:1193340632.129960.94770@57g2000hsv.googlegroups.com... > PC1 = 192.168.1.98, 3389 > PC2 = 192.168.1.99, 3390 > >> >> Telnet internally to PC1 on port 3389 >> Telnet internally to PC2 on port 3390 >> Telnet externally on port 3389 >> Telnet externally on port 3390 >> > > I tried this using PuTTy, but was unsuccessful. I'm probably doing > something wrong (use PuTTy for SSH to linux box). *** What's wrong with humble telnet.exe? *** telnet 192.168.1.98 3389 >> netstat -an >> > > (on PC2) > Proto Local Address Foreign Address State > TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING *** Your own PC is listening on port 3390. > TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED > (the second is me connected on the LAN; there is no monitor plugged > into the PC) *** Looks like an established RDP session. >> >> The Windows Firewall exception - When you added it, what scope did you >> choose? By default I think the scope is set to the local network. If you >> didn't change it, you need to go back in and change the scope. >> > > Exceptions Tab: > - 3390, TCP, Internet (scope) > > Advanced Tab > Advanced Settings > Service Settings: > - ip on network: 192.168.1.99, 3390, TCP > >
Guest DiFFeReNT Posted October 26, 2007 Posted October 26, 2007 Re: Change Remote Desktop Port On Oct 25, 4:29 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: > Looks like port 3390 is fine but there is no report about > port 3389. See below. > > "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message > > news:1193340632.129960.94770@57g2000hsv.googlegroups.com... > > > PC1 = 192.168.1.98, 3389 > > PC2 = 192.168.1.99, 3390 > > >> Telnet internally to PC1 on port 3389 > >> Telnet internally to PC2 on port 3390 > >> Telnet externally on port 3389 > >> Telnet externally on port 3390 > > > I tried this using PuTTy, but was unsuccessful. I'm probably doing > > something wrong (use PuTTy for SSH to linux box). > > *** What's wrong with humble telnet.exe? > *** telnet 192.168.1.98 3389 > > >> netstat -an > > > (on PC2) > > Proto Local Address Foreign Address State > > TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING > > *** Your own PC is listening on port 3390. > > > TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED > > (the second is me connected on the LAN; there is no monitor plugged > > into the PC) > > *** Looks like an established RDP session. > > > > >> The Windows Firewall exception - When you added it, what scope did you > >> choose? By default I think the scope is set to the local network. If you > >> didn't change it, you need to go back in and change the scope. > > > Exceptions Tab: > > - 3390, TCP, Internet (scope) > > > Advanced Tab > Advanced Settings > Service Settings: > > - ip on network: 192.168.1.99, 3390, TCP Connecting using remote desktop over the LAN (ip:3390) works great, but does not over the internet. The router log shows that a connection was made for port 3390 from the PC over the internet, but there is no sign in the firewall log on the PC that any connection attempt was made (except for connections over the LAN, and also logging on the router). Telnet is disabled, and I don't really know how to test it anyways. The port 3390 PC is setup exactly the same as the 3389 one, so I don't see why it's not working. I guess the simple solution to this is LogMeIn, even though I'd rather not...
Guest Pegasus \(MVP\) Posted October 26, 2007 Posted October 26, 2007 Re: Change Remote Desktop Port "DiFFeReNT" <ChrisLampson@gmail.com> wrote in message news:1193434741.317965.121880@o3g2000hsb.googlegroups.com... > On Oct 25, 4:29 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: >> Looks like port 3390 is fine but there is no report about >> port 3389. See below. >> >> "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message >> >> news:1193340632.129960.94770@57g2000hsv.googlegroups.com... >> >> > PC1 = 192.168.1.98, 3389 >> > PC2 = 192.168.1.99, 3390 >> >> >> Telnet internally to PC1 on port 3389 >> >> Telnet internally to PC2 on port 3390 >> >> Telnet externally on port 3389 >> >> Telnet externally on port 3390 >> >> > I tried this using PuTTy, but was unsuccessful. I'm probably doing >> > something wrong (use PuTTy for SSH to linux box). >> >> *** What's wrong with humble telnet.exe? >> *** telnet 192.168.1.98 3389 >> >> >> netstat -an >> >> > (on PC2) >> > Proto Local Address Foreign Address State >> > TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING >> >> *** Your own PC is listening on port 3390. >> >> > TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED >> > (the second is me connected on the LAN; there is no monitor plugged >> > into the PC) >> >> *** Looks like an established RDP session. >> >> >> >> >> The Windows Firewall exception - When you added it, what scope did >> >> you >> >> choose? By default I think the scope is set to the local network. If >> >> you >> >> didn't change it, you need to go back in and change the scope. >> >> > Exceptions Tab: >> > - 3390, TCP, Internet (scope) >> >> > Advanced Tab > Advanced Settings > Service Settings: >> > - ip on network: 192.168.1.99, 3390, TCP > > Connecting using remote desktop over the LAN (ip:3390) works great, > but does not over the internet. > The router log shows that a connection was made for port 3390 from the > PC over the internet, but there is no sign in the firewall log on the > PC that any connection attempt was made (except for connections over > the LAN, and also logging on the router). > Telnet is disabled, and I don't really know how to test it anyways. > The port 3390 PC is setup exactly the same as the 3389 one, so I don't > see why it's not working. > I guess the simple solution to this is LogMeIn, even though I'd rather > not... > Make sure that the Default Gateway of the RDP host points at your router/firewall.
Guest DiFFeReNT Posted November 2, 2007 Posted November 2, 2007 Re: Change Remote Desktop Port On Oct 26, 5:19 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: > "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message > > news:1193434741.317965.121880@o3g2000hsb.googlegroups.com... > > > > > On Oct 25, 4:29 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: > >> Looks like port 3390 is fine but there is no report about > >> port 3389. See below. > > >> "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message > > >>news:1193340632.129960.94770@57g2000hsv.googlegroups.com... > > >> > PC1 = 192.168.1.98, 3389 > >> > PC2 = 192.168.1.99, 3390 > > >> >> Telnet internally to PC1 on port 3389 > >> >> Telnet internally to PC2 on port 3390 > >> >> Telnet externally on port 3389 > >> >> Telnet externally on port 3390 > > >> > I tried this using PuTTy, but was unsuccessful. I'm probably doing > >> > something wrong (use PuTTy for SSH to linux box). > > >> *** What's wrong with humble telnet.exe? > >> *** telnet 192.168.1.98 3389 > > >> >> netstat -an > > >> > (on PC2) > >> > Proto Local Address Foreign Address State > >> > TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING > > >> *** Your own PC is listening on port 3390. > > >> > TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED > >> > (the second is me connected on the LAN; there is no monitor plugged > >> > into the PC) > > >> *** Looks like an established RDP session. > > >> >> The Windows Firewall exception - When you added it, what scope did > >> >> you > >> >> choose? By default I think the scope is set to the local network. If > >> >> you > >> >> didn't change it, you need to go back in and change the scope. > > >> > Exceptions Tab: > >> > - 3390, TCP, Internet (scope) > > >> > Advanced Tab > Advanced Settings > Service Settings: > >> > - ip on network: 192.168.1.99, 3390, TCP > > > Connecting using remote desktop over the LAN (ip:3390) works great, > > but does not over the internet. > > The router log shows that a connection was made for port 3390 from the > > PC over the internet, but there is no sign in the firewall log on the > > PC that any connection attempt was made (except for connections over > > the LAN, and also logging on the router). > > Telnet is disabled, and I don't really know how to test it anyways. > > The port 3390 PC is setup exactly the same as the 3389 one, so I don't > > see why it's not working. > > I guess the simple solution to this is LogMeIn, even though I'd rather > > not... > > Make sure that the Default Gateway of the RDP host points > at your router/firewall. After trying all of your suggestions, even double checking your last one when I could assure you it's set is in my sleep, it still didn't work.... So I reinstalled Windows. Still, it doesn't work over the internet, only over the LAN. The only explanation is that the Linksys router is jacked up with port 3390 - but not 3389. So I tried other ports: 3392, and then 3900, each time updating reg, firewall router and restarting. No va. This is very frustrating - every example I find on the internet works for whoever tries it, except me. A new router isn't in my budget, so I guess I'm going to have to use LogMeIn, which requires the user to be logged in. Thanks again for your help.
Guest DiFFeReNT Posted November 2, 2007 Posted November 2, 2007 Re: Change Remote Desktop Port On Nov 1, 9:13 pm, DiFFeReNT <ChrisLamp...@gmail.com> wrote: > On Oct 26, 5:19 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: > > > > > "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message > > >news:1193434741.317965.121880@o3g2000hsb.googlegroups.com... > > > > On Oct 25, 4:29 pm, "Pegasus \(MVP\)" <I....@fly.com> wrote: > > >> Looks like port 3390 is fine but there is no report about > > >> port 3389. See below. > > > >> "DiFFeReNT" <ChrisLamp...@gmail.com> wrote in message > > > >>news:1193340632.129960.94770@57g2000hsv.googlegroups.com... > > > >> > PC1 = 192.168.1.98, 3389 > > >> > PC2 = 192.168.1.99, 3390 > > > >> >> Telnet internally to PC1 on port 3389 > > >> >> Telnet internally to PC2 on port 3390 > > >> >> Telnet externally on port 3389 > > >> >> Telnet externally on port 3390 > > > >> > I tried this using PuTTy, but was unsuccessful. I'm probably doing > > >> > something wrong (use PuTTy for SSH to linux box). > > > >> *** What's wrong with humble telnet.exe? > > >> *** telnet 192.168.1.98 3389 > > > >> >> netstat -an > > > >> > (on PC2) > > >> > Proto Local Address Foreign Address State > > >> > TCP 0.0.0.0:3390 0.0.0.0:0 LISTENING > > > >> *** Your own PC is listening on port 3390. > > > >> > TCP 192.168.1.99:3390 192.168.1.106:4663 ESTABLISHED > > >> > (the second is me connected on the LAN; there is no monitor plugged > > >> > into the PC) > > > >> *** Looks like an established RDP session. > > > >> >> The Windows Firewall exception - When you added it, what scope did > > >> >> you > > >> >> choose? By default I think the scope is set to the local network. If > > >> >> you > > >> >> didn't change it, you need to go back in and change the scope. > > > >> > Exceptions Tab: > > >> > - 3390, TCP, Internet (scope) > > > >> > Advanced Tab > Advanced Settings > Service Settings: > > >> > - ip on network: 192.168.1.99, 3390, TCP > > > > Connecting using remote desktop over the LAN (ip:3390) works great, > > > but does not over the internet. > > > The router log shows that a connection was made for port 3390 from the > > > PC over the internet, but there is no sign in the firewall log on the > > > PC that any connection attempt was made (except for connections over > > > the LAN, and also logging on the router). > > > Telnet is disabled, and I don't really know how to test it anyways. > > > The port 3390 PC is setup exactly the same as the 3389 one, so I don't > > > see why it's not working. > > > I guess the simple solution to this is LogMeIn, even though I'd rather > > > not... > > > Make sure that the Default Gateway of the RDP host points > > at your router/firewall. > > After trying all of your suggestions, even double checking your last > one when I could assure you it's set is in my sleep, it still didn't > work.... > So I reinstalled Windows. > Still, it doesn't work over the internet, only over the LAN. The only > explanation is that the Linksys router is jacked up with port 3390 - > but not 3389. > So I tried other ports: 3392, and then 3900, each time updating reg, > firewall router and restarting. > No va. > > This is very frustrating - every example I find on the internet works > for whoever tries it, except me. > > A new router isn't in my budget, so I guess I'm going to have to use > LogMeIn, which requires the user to be logged in. > > Thanks again for your help. I take that back, LogMeIn runs as a service, which allows connecting to a PC if the user isn't logged in.
Recommended Posts