OT: Remote Access to your PC

Fyron · #1 August 8th, 2005, 08:14 PM

You do not need a costly static IP. Dynamic DNS is all you need. Does dyndns.org provide a program to automatically keep the IP associated with the domain current? I went with no-ip.com a while ago because they provided such a program and dyndns.org did not... But either service, or a host of others, will solve any dynamic IP woes.

Will · #2 August 8th, 2005, 08:55 PM

Hmm, I guess I should have clarified a bit. By static, I meant "IP does not change in the time you're away from your computer". As far as I've seen, even if you have a "dynamic IP address", it stays the same as long as the computer is up and running. When it's time to renew the lease, you just get the same one again.

So, static, as in it's the same one that the computer had when you left the house five hours ago.

Fyron · #3 August 8th, 2005, 09:05 PM

Ah, yes. But what if there is a connection glitch and your IP changes in the down time?

Suicide Junkie · #4 August 8th, 2005, 09:22 PM

Then you're down for a day, and you fix it when you get home?

Fyron · #5 August 8th, 2005, 09:32 PM

If it is a momentary glitch and the connection restores properly, I like having the domain update automatically and having no down time. For a couple KB of system resources, it is worth it to me.

Thermodyne · #6 August 8th, 2005, 09:57 PM

Quote:

Imperator Fyron said:
Ah, yes. But what if there is a connection glitch and your IP changes in the down time?

All you need to do is run a little script the checks the WAN address and emails the results to your web mail account. Then all you need to do is enter the new addy into VNC.

Thermodyne · #7 August 8th, 2005, 10:09 PM

I use TightVNC almost every day at work. And it is not all that. It beats driving 100's of miles, but it can be a pain. And this is arcoss a private WAN. Across the internet it is not as good, and very exploitable. Also, VPN will not support VNC, so everything you access is out in the open and subject to interception. Also, you must leave the system up, if it goes to sleep, VPN will not wake it unless wake on LAN is on, but this allows anyone to wake it. You also need to open the firewall for VNC, which gives any ole person the same access. They sniff your VPN password, and they are in your system.

IMHO, you should set up IIS and put the things yuo need into a private web site. Then use https: and password authentication. Better yet, you uni peeps should pick up a copy of Small Business Server on the cheap uni price. Put it on an old box and use the MS Share Point Site that comes pre-installed. Also, you can log into SBS remotely with the VPN and a cert, and drive it from a true remote desk top.

Fyron · #8 August 8th, 2005, 11:04 PM

So use a complex password. Good luck trying to sniff 16 random characters.

TurinTurambar · #9 August 9th, 2005, 12:04 AM

Thanks all, for the advice (and the warnings). I am looking thru the documentation on TightVNC right now, and it looks pretty well supported. I think I'll give it a go tomorrow from the field and see how it works.

As for file transfer: can't I just remote the server side into a web browser and email it to myself?

Thx,
[img]/threads/images/Graemlins/Dagger.gif[/img][img]/threads/images/Graemlins/icon42.gif[/img]

Thermodyne · #10 August 9th, 2005, 08:59 AM

Quote:

Imperator Fyron said:
So use a complex password. Good luck trying to sniff 16 random characters.

VNC password is plain text across the wire. All I need to do is capture packets to and scan till I find it.