Technical Discussion
  >> Home Networking, Internet Connection Sharing, etc.


Register (or login) on our website and you will not see this ad.


These posts have been archived and can no longer be replied to or modified.
  Print Thread
Standard User rentoxe
(newbie) Fri 04-May-07 22:35:29
Print Post

Remote Desktop outside LAN


[link to this post]
 
Hi all

I have a BT home hub with a Bt Broadband package and I have fowarded the RDC port to my machine but if I try to connect from work it des'nt function.

I have tested from other pc in the lan and it works. To access I eneter the router ip address but it doesnt ping. I have then done a traceroute from the internet and got those results:

Hop (ms) (ms) (ms) IP Address Host name
1 1 0 0 66.98.244.1 gphou-66-98-244-1.ev1servers.net
2 0 9 0 66.98.241.16 gphou-66-98-241-16.ev1servers.net
3 1 0 0 66.98.240.7 gphou-66-98-240-7.ev1servers.net
4 3 1 1 216.200.251.161 ge-6-0-1.mpr2.iah1.us.above.net
5 1 1 11 64.125.26.14 so0-0-0.mpr4.iah1.us.above.net
6 14 14 14 64.125.29.65 so-5-0-0.mpr1.atl6.us.above.net
7 14 14 14 64.125.27.50 so-0-0-0.mpr2.atl6.us.above.net
8 27 25 25 64.125.28.49 so-1-3-3.mpr1.dca2.us.above.net
9 97 99 97 64.125.27.58 so-0-1-0.mpr1.lhr2.uk.above.net
10 97 97 101 195.99.125.93 -
11 104 97 97 62.6.201.121 core2-pos9-0.ilford.ukcore.bt.net
12 98 98 98 62.6.204.245 core2-pos7-3.kingston.ukcore.bt.net
13 98 98 98 62.6.40.246 bar3-pos9-0.kingston2.broadband.bt.net
14 98 98 98 217.47.71.115 -
15 114 99 120 217.41.171.45 -
16 105 102 100 217.41.171.69 -
17 99 98 98 217.41.171.145 -
18 98 98 98 217.41.171.10 -
19 99 99 99 213.123.80.163 -
20 Timed out Timed out Timed out -
21 Timed out Timed out Timed out -
22 Timed out Timed out Timed out -
23 Timed out Timed out Timed out -

Trace aborted.

Is it because mine is not a business line? Have I missed something in the configuration? I am aware that other people can connect from work.. so I dismiss that chance.

Any help?

Thank you.
Standard User Rockh
(eat-sleep-adslguide) Sat 05-May-07 10:47:27
Print Post

Re: Remote Desktop outside LAN


[re: rentoxe] [link to this post]
 
No need to upgrade your account, unless your ISP specifically blocks the RDP port (unlikely). It is more likely that your employer blocks it.

Firstly you need to prove whether the port forwarding rule is actually working . You need to get someone else to try and connect via remote desktop to your pc.
You are on a dynamic IP product at a guess so it could be that your external ip has changed. Prolly better to use something like dyndns to track your routers external ip and translate that to a domain name.

Dave




Standard User rentoxe
(newbie) Sat 05-May-07 11:03:46
Print Post

Re: Remote Desktop outside LAN


[re: Rockh] [link to this post]
 
Hi Rockh, thanks for your reply

I use dydsn and I know that my employer bocks the RDC port, however I have set up some forwarding on my PC and modified the RDC connection port on the work computer.

What puzzles me is that I can't even ping my router or see my router on the dydsn address..

If I try any of the above from within my LAN it works. I am very confused but I think it may some router configuration issue?? Also does the traceroute look ok?

Thank you


Register (or login) on our website and you will not see this ad.

Standard User Rockh
(eat-sleep-adslguide) Sat 05-May-07 12:23:42
Print Post

Re: Remote Desktop outside LAN


[re: rentoxe] [link to this post]
 
The router will need to be told to reply to pings arriving at the wan (adsl) port. Quite a few of the soho type don't respond by default.

What you need to do to prove whether the port you have opened is actually open is to use a port scanner hosted on a server outside your network. There are a few about Netmonitor is one or www.grc.com (ignore most of the carp that this site spews at you as most of it is scaremongery).

Dave




Standard User RobertoS
(experienced) Sun 06-May-07 01:00:02
Print Post

Re: Remote Desktop outside LAN


[re: Rockh] [link to this post]
 
In reply to:

...at the wan (adsl) port. Quite a few of the soho type don't respond by default.


Won't that be a basic spam/intruder protection? If it doesn't reply to external pings, then the intruder doesn't know there is anything on that address.

If I'm right, then setting it to respond means you need to make sure your software firewall is effective.
Standard User Rockh
(eat-sleep-adslguide) Sun 06-May-07 18:59:29
Print Post

Re: Remote Desktop outside LAN


[re: RobertoS] [link to this post]
 
About as basic as it gets.
There are plenty of lines of thought as to whether you should or shouldn't set your hardware to respond to pings.

The fact the router responds will not necessary mean that it can be compromised. NAT provides a decent line of defense, plus most SOHO kit these days has some form of SPI firewall.

Dave




Standard User Deadbeat
(fountain of knowledge) Mon 07-May-07 13:42:43
Print Post

Re: Remote Desktop outside LAN


[re: Rockh] [link to this post]
 
"(ignore most of the carp that this site spews at you as most of it is scaremongery)."

I'll have you know that the venerable Steve was walking on water and satisfying the appetite of the whole Chinese populace with a single sardine whilst that charlatan Tony B Liar was still faffing over getting his loafers damp.
Standard User deleted
(deleted) Wed 09-May-07 10:18:58
Print Post

Re: Remote Desktop outside LAN


[re: rentoxe] [link to this post]
 
Why not have a look at LogMeIn?? Runs in a browser over an SSL connection and is available free.. I use it over a GPRS connection (no 3G where I work) and it works ok..

Edit: Forgot to mention that there is no requirement to forward ports or anything like that as the PC with LogMeIn installed connects to the LogMeIn server, so it knows the IP address..

Edited by deleted (Wed 09-May-07 10:21:38)

Anonymous
(Unregistered)Sun 13-May-07 09:58:14
Print Post

Re: Remote Desktop outside LAN


[re: deleted] [link to this post]
 
I cannot use Log Me in or similar, however I can use one port (21).
Iwas finally trying to configure this on my Hom Hub put the port fowarding on that port does not seem to have an effect. Also canyouseeme detection fails.
At ths point I think that BT might be blocking that port. Does anyone know if this is the case? And how to solve it?

Thank you
  Print Thread

Jump to