If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Remote Desktop Question
I running three XP Pro computers on a LAN. Remote Desktop works great within
the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. PS - I'm not a network wiz |
Ads |
#2
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John |
#3
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John |
#4
|
|||
|
|||
Remote Desktop Question
Thanks John for your reply and yes, I will look into a VPN solution.
Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John |
#5
|
|||
|
|||
Remote Desktop Question
Thanks John for your reply and yes, I will look into a VPN solution. Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John |
#6
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John Thanks John for your reply and yes, I will look into a VPN solution. Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim The straightforward way is to connect to your router's configuration page with your web browser. Usually http://192.168.1.1 but depends on your router manufacturer and router configuration. The quickest way is to connect to: http://whatismyip.com which will report the address that the internet at large thinks you're coming from. In most cases, this is your router IP address. Your post headers indicate that you are coming from: 68.39.113.227 HTH, John |
#7
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John Thanks John for your reply and yes, I will look into a VPN solution. Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim The straightforward way is to connect to your router's configuration page with your web browser. Usually http://192.168.1.1 but depends on your router manufacturer and router configuration. The quickest way is to connect to: http://whatismyip.com which will report the address that the internet at large thinks you're coming from. In most cases, this is your router IP address. Your post headers indicate that you are coming from: 68.39.113.227 HTH, John |
#8
|
|||
|
|||
Remote Desktop Question
Yes John, that is the address I have been using in my_ip_address:3389 which
does not work. It appears port 3389 is blocked. Jim "John Wunderlich" wrote in message ... "Jim" wrote in : "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John Thanks John for your reply and yes, I will look into a VPN solution. Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim The straightforward way is to connect to your router's configuration page with your web browser. Usually http://192.168.1.1 but depends on your router manufacturer and router configuration. The quickest way is to connect to: http://whatismyip.com which will report the address that the internet at large thinks you're coming from. In most cases, this is your router IP address. Your post headers indicate that you are coming from: 68.39.113.227 HTH, John |
#9
|
|||
|
|||
Remote Desktop Question
Yes John, that is the address I have been using in my_ip_address:3389 which
does not work. It appears port 3389 is blocked. Jim "John Wunderlich" wrote in message ... "Jim" wrote in : "John Wunderlich" wrote in message 10... "Jim" wrote in : I running three XP Pro computers on a LAN. Remote Desktop works great within the LAN but not externally. Shouldn't I be able to access these computers using "My IP address":3389? Remote Desktop cannot find the address plus I cannot ping it. I am port forwarding 3389 in my router but since each PC has a different internal address do I have to forward 3389 to each address? I'm also checking Remote Desktop on in the Windows Firewall. Suggestions greatly appreciated. You will not be able to access it with "My IP adddress" externally if this address is a private IP address assigned by your router (typically 192.168.x.x). You must use "Router IP Address" when connecting externally. You are correct to port forward 3389. However, only one of your machines can receive this port forwarding. Pick one and live with it. Alternatively, you can allow your router configuration page to be modified externally -- then you can connect to your router from the internet, modify the port forwarding to the machine you want, and then connect. The better solution would be to replace your router with a router that supports VPN. Then, you can then VPN into the router, then connect to any machine in your local subnet just as if you were there. HTH, John Thanks John for your reply and yes, I will look into a VPN solution. Could you please explain how I find my Router IP address? Is it the address listed below DHCP? Jim The straightforward way is to connect to your router's configuration page with your web browser. Usually http://192.168.1.1 but depends on your router manufacturer and router configuration. The quickest way is to connect to: http://whatismyip.com which will report the address that the internet at large thinks you're coming from. In most cases, this is your router IP address. Your post headers indicate that you are coming from: 68.39.113.227 HTH, John |
#10
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: Yes John, that is the address I have been using in my_ip_address:3389 which does not work. It appears port 3389 is blocked. It very well could be. When I had Adelphia Cable, it was against the Terms of Service (TOS) to have *any* server on their network and to enforce this, they blocked a bunch of incoming ports. Remote desktop is technically a "service" at your end, so your provider might have blocked that port as well. IIRC, they did allow VPN, so a router that supports VPN may still be a viable option for you. Check with your ISP and/or read your TOS. HTH, John |
#11
|
|||
|
|||
Remote Desktop Question
"Jim" wrote in
: Yes John, that is the address I have been using in my_ip_address:3389 which does not work. It appears port 3389 is blocked. It very well could be. When I had Adelphia Cable, it was against the Terms of Service (TOS) to have *any* server on their network and to enforce this, they blocked a bunch of incoming ports. Remote desktop is technically a "service" at your end, so your provider might have blocked that port as well. IIRC, they did allow VPN, so a router that supports VPN may still be a viable option for you. Check with your ISP and/or read your TOS. HTH, John |
#12
|
|||
|
|||
Remote Desktop Question
Many thanks John, I think I will give VPN a try, if I can figure it out!
Jim "John Wunderlich" wrote in message 10... "Jim" wrote in : Yes John, that is the address I have been using in my_ip_address:3389 which does not work. It appears port 3389 is blocked. It very well could be. When I had Adelphia Cable, it was against the Terms of Service (TOS) to have *any* server on their network and to enforce this, they blocked a bunch of incoming ports. Remote desktop is technically a "service" at your end, so your provider might have blocked that port as well. IIRC, they did allow VPN, so a router that supports VPN may still be a viable option for you. Check with your ISP and/or read your TOS. HTH, John |
#13
|
|||
|
|||
Remote Desktop Question
Many thanks John, I think I will give VPN a try, if I can figure it out! Jim "John Wunderlich" wrote in message 10... "Jim" wrote in : Yes John, that is the address I have been using in my_ip_address:3389 which does not work. It appears port 3389 is blocked. It very well could be. When I had Adelphia Cable, it was against the Terms of Service (TOS) to have *any* server on their network and to enforce this, they blocked a bunch of incoming ports. Remote desktop is technically a "service" at your end, so your provider might have blocked that port as well. IIRC, they did allow VPN, so a router that supports VPN may still be a viable option for you. Check with your ISP and/or read your TOS. HTH, John |
Thread Tools | |
Display Modes | |
|
|