Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Remotecontrol pc behind nat |
|---|---|
| Date: | Thu, 10 May 2007 19:57:27 -0300 |
The best FREE service for this purpose is LogMeIn - http://logmein.com
Optionally, if you want the harder way, you should use a ssh tunnel back to Linux box in the Internet (at home, university, ...). the dynamic IP addresses issue can be solved by http://www.dyndns.org or noip.com ...
ssh -R 3389:localhost:3389 <my_linux_box> (it will create a tunnel from TCP port 3389 of your Linux box to the port 3389 (RDP) of your Windows box. For SSH on Windows try Cygwin or PuTTY, you can do this even through proxy servers (suggestion: run your sshd on port 443)
Regards, Fabio Fagundes Rio de Janeiro - Brazil
One think I do, is went IPv6. If you have a IPv6 internet connection (or get a free connection via freenet6.org project) you just connection to your machine.
You can create IPv6-IPv4 NAT Traversing and now your home machine has a routed IPv6 address!
On Mon, 27 Nov 2006, Ralph Forsythe wrote:
> Why not just use remote desktop (aka terminal services), and have it listen > on a different port? This web article shows you how to change the port > setting: > http://support.microsoft.com/kb/187623 > > It defaults to 3389, but there is no reason you can't put it on 80, 443, or > 21 as long as there aren't other services already listening on them. > > Be smart about it though, don't get owned! Keep the box patched and user > accounts locked down with strong passwords, especially since you can't > restrict the source IP's that will connect from the firewall. Expect that > you will get scanned, and someone will try and break their way in. > > > Cheers, > - Ralph > > On Tue, 28 Nov 2006, Safe Packet wrote: > >> Hi list , >> >> I have a requirement where in I want to remotely control a windows machine >> from internet which is behind a firewall and has a natted ip. The firewall >> has a public ip configured on its untrusted interface and it has http, >> https >> and ftp ports open. The restriction here is that with out making any >> changes >> to the existing firewall and nat configuration this has to be achieved? Is >> this possible ?Any suggestions will be appreciated. >> >> I know a package from ultra vnc (NAT2NAT plug-in) which can do this but >> unfortunately vnc port is also blocked in my case. >> >> Thanks in advance >> >
-- Joseph Renda <Joseph@Renda.CA>
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Remotecontrol pc behind nat, Luis Lopez Sanchez |
|---|---|
| Next by Date: | Cisco PIX VPN question..., Dan Denton |
| Previous by Thread: | RE: Remotecontrol pc behind nat, Luis Lopez Sanchez |
| Next by Thread: | Cisco PIX VPN question..., Dan Denton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |