Hi
If all you need is access to files on your server, the simple way is to use dropbox - www.dropbox.com which will allow access to your synchronised files from anywhere.
I GOT IT WORKING!!!!! ;DD
I'm going to try dyndns next.
I will also try that dropbox out because it sounds simple.
Is there a way to add my server as a drive letter in XP? or will i have to install an ftp type program?
Last edited by dragonpimpsta; August 14th, 2010 at 09:36 PM.
Depends in part on how often you reboot. Each reboot may quite likely get a different IP address. The ISP can also change it at any time, though. The usual interval is daily.
Some years ago I was on DHCP from AT&T (then Southwestern Bell) and kept the same IP for months on end. They later switched from DHCP to PPPoE and now users may get a new IP at each login, no reboot required.
Using dyndns or one of its competitors is the best way to go. You install their client program on your server, and it will keep them informed of your current IP so that you can address it by name rather than by IP. The down side of this whole idea, though, is that anyone can get into your server unless you keep it locked down tightly. I've just gone through a 10-day reformat-and-reinstall nightmare because someone got into my system (due entirely to my own carelessness and violation of basic security principles) and had the opportunity to take total control of it, by grabbing my ssh key files!
--
Jim Kyle in Oklahoma, USA
Linux Counter #259718
Howto mark thread: https://wiki.ubuntu.com/UnansweredPo.../SolvedThreads
Connecting through my public ip worked on my home connection, but when i tried it at someone else house later today it didnt work. The connection timed out. Is there another router setting I should change or what? My dyndns account even works for connecting to the server while im at home already connecting through my router. It just doesnt work anywhere else for some reason.
The reason that security experts advise using a router even if you have only one machine behind it is that by their design, routers won't accept incoming traffic unless it's in response to outgoing traffic already sent. That prevents anyone, including yourself, from initiating a connection from outside. You want to keep this feature as intact as possible to prevent unwanted intrusion.
The port forwarding feature that stlsaint mentioned back in post #2 of this thread is how you "poke a hole" in the automatic protection to allow connection from outside through a single specific port. The exact commands for doing this will vary from one make of router to another, but the magic words to look for are "port forwarding."
Even using ssh to create your secure "tunnel" through the router can be risky. I'm still trying to recover from an intrusion that happened more than two weeks ago because a combination of events made my "secure" system insecure. I've had to reformat every machine on my local network, reinstall everything, and lost more than a week's worth of messages and reference material -- and the system still isn't back to full normal operation. Don't take any shortcuts with this, or you could find that your machine has become a "mule" for a child porn ring, or the newest member of a botnet pumping out spam at the rate of thousands of messages an hour!
--
Jim Kyle in Oklahoma, USA
Linux Counter #259718
Howto mark thread: https://wiki.ubuntu.com/UnansweredPo.../SolvedThreads
sounds scary. i'll research security and try a different port.
Bookmarks