Remote Login/File Share - Mac/Windows
I'm in need of a little advice.
I live in Portland, OR.
I have a buddy who lives in Eugene, OR.
What I would like is to set up a connection between our two computers, that would allow us access to one another's machines, so that we would be able to share the music that we've created.
Via TCP, SSH, VPN.
I've been working on this the past few days now, and am in need of assistance.
Any help would be greatly appreciated.
Why not use a feature like Drop Box?
Drop Box would be ideal.
Now I may be wrong... But isn't Drop Box more of an item for AFP?
More specifically for Mac to Mac sharing?
Also, I can't think of the Microsoft equivalent to Drop Box.
Even if my buddy in Eugene was able to to access my Drop Box - running Windows, he wouldn't have one.
That's what's led me to where I am now.
Creating a platform friendly server.
I believe FTP would be the way to go, regardless of security.
With that said, I'm having difficulties.
Dropbox is cross platform - it supports Windows, OS X, Linux, iOS and Android. No worries there.
In the past, I accessed a dropbox through a server at a school I was attending.
This is what it looked like -----------------> afp://63.231.290.43
-I could turn assignments in from home.
Now, if my buddy and I were both using DropBoxes...
Would I need to set up a server like the one above...? ^^^
Or would there be some kind of middle man to upload to, such as the DropBox website?
My first reply had the link in it it. Drop Box is a generic term that it sounds like you are familiar with, but also in this case is a service.
Dropbox - Simplify your life
I suggested this as an option since there are significant security concerns as well as configuration and maintenance involved with setting up your own sharing. From your OP I thought Drop Box to be a good fit.
Well, thank you.
Although... the first snag has already been hit demoing Dropbox.
In order to keep Dropbox as a free service, the total allotment of data capable of being stored at any given time... is only 2 gigs.
The first file I'd like to transfer is 5.27 gigs.
The next available plan is $9.99 a month/$99.99 a year, for 50 gigs.
I'll be honest though, I have no interest in paying $100.00 a year.
This leads me back to my questions regarding a home server.
I am aware of the security vulnerabilities generated through such a server.
Port forwarding has it's uses, and I believe it would be involved with what I'd like to do.
As far as configuration and maintenance, those are of no concern.
-In 1 1/2 years I'll be graduating with an associates in Computer Information Systems.
-So I suppose I'd better get used to configuration and maintenance.
Dropbox is checked off the list.
Someone, please enlighten me with the 101s of a personal server.
And thank you all for the advice that's been dealt thus far.
You could use SSH and then simply use sftp to transfer files. I suggest this over FTP since FTP is unencrypted. I'm away from my Mac right now but it might be as easy as simply enabling remote login on the server.
That's the thing...
I enabled remote login.
If I wanted to access the server on my computer, would I do so through a URL on a search engine - like an FTP server, or would I do so through something along the lines of "Connect to Server," under the "Go" tab?
When I enabled Remote Login, it told me I could access my computer remotely by typing "ssh ***********@192.168.1.5"
Where would I type that, in order to access my computer remotely?
For non-commercial use teamviewer is free
TeamViewer - Free Remote Access and Remote Desktop Sharing over the Internet
It allows remote access to desktops but another feature is file transfer with very little setup from the user.
Back to port forwarding,...
SSH uses port 22. You would need a static IP on your Mac and access to configure the firewall that connects you to the internet. Then forward port 22 to that IP in the firewall.
If your internet does not have a static IP then you may want to employee a free dynamic DNS service such as DynDNS.org so that you can use host name resolution.
Just know that ssh access to a computer will give the user that connects, full file system rights. Even though you say you are aware of the security concerns, open port 22 to the public should be done with caution. Some firewall will do port redirection. This can protect the identity of a port like 22.
Set the firewall to redirect port 10888 to 22 (or anything over 1024 and below 65000) This way a port scan will not show that 22 is open.
ssh -p 10888 firstname.lastname@example.org
or if you have a static public IP
ssh -p 10888 email@example.com
A simple way to do the transfer is with something like CyberDuck which has sftp support. You simply plug in the IP, user name and password and you're good to go.
Ivan, thank you. TeamViewer looks like a good piece of software.
As does CyberDuck, thank you vansmith.
Thank you both.
It appears as though I'd be able to use either, to perform the actions that I'd like to.
In the end, I probably will.
Now, port forwarding.
-I changed my router's settings from a Dynamic to a Static IP.
-I then opened port 22.
-Start 22/End 22.
-I wasn't able to adjust the router's firewall just yet, that can be done later.
-Or can it? Does the SSH port need to be redirected to my NetGear's embedded firewall... in order to function as a tunnel?
So let's say that what was needed to be done - in order for my computer to be accessed remotely, has been done.
How would "ssh -p 10888 firstname.lastname@example.org" be accessed from my buddy's Windows machine? Without Bash. Where would that be entered?
Some file finder?
Would he need to download specific software in order to reach this address?
Thank you all for you help.
See this thread - general info on ports
and this thread for more information on port forwarding
Once you have ssh setup you can use scp to move stuff around - or use a program like cyberduck to move stuff around graphically. I highly recommend you understand the security risks of setting up ssh - port 22 is a well known port and is brute force attacked by scripts all the time.
By the questions you are asking - I would recommend not trying to go down the route of opening ports and forwarding them. I would again recommend teamviewer as the security risk is much lower as the software and servers do all the heavy lifting of security.
The only difficulty I'd see with the solutions proposed is resuming of the file transfer and the integrity of the file if you get connection interuption etc.
Along the same lines as dropbox why not get a Box account - 50gb free
|All times are GMT -4. The time now is 07:42 PM.|
Powered by vBulletin
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.