Stop Microsoft
Operating Systems => Linux and UNIX => Topic started by: Doogee on 20 January 2003, 13:16
-
i dont know which forum this should go in but since linux rules all im chhosing the linux forum, mods move it if it seems inappropriate.
Ok here goes.
Since i have absolutely NO IDEA about samba and am giving it up (dont say use samba) i need a bit of an alternative to share files to my network.
What i was thinking was a telnet/ssh server or something like that (what would i use) where i make a public directory, lock the client to that directory and i place files there when needed.
There will be both linux and windows clients.
This server must only acess on the Local Network and not be able to be touched by the internet (i use an adsl router hub thing which connects all the computers on a local network and to the internet)
So what do i need to get started and how will the clients recive the files from the network?
More info will be given if needed.
Thanks
-
I'm going to go against your wishes and tell you to use Samba since you have Windows and Linux clients. If you had only Linux clients I would tell you to use NFS. Samba is really extremely easy and usually only takes only changing one or two parameters from the default configuration to have it working appropriately for you. I would suggest buying a book on Samba. There are several good Samba books at your local book store.
-
a while back i tried it and coukdnt do it i jsut need to be able to get files off my computer when i need to. i wouldnt even usesamba much anyway. also i would like the experiance. so come on throw this shit at me.
-
Setting up Samba is easy (if you throw an afternoon - well, less, probably - at it and read the docs carefull, that is). Correctly configuring ssh is much harder (with the protection stuff, that is), so learn Samba first.
More important, Smb is designed for what you want. Telnet/ssh isn't.
Anyway, if you do want to do ssh (NO telnet please, it's obsolete), make sure your firewall blocks any connection attemps to the server from outside your LAN (your firewall docs should tell how, this shouldn't pose a problem). This is a safeguard to make sure nothing gets through.
Also, your server should block any such attemps (redundancy is a good thing in security). This should also be in your docs, and differs per server (if yours can't do this, get another one).
Last, make sure every account has a decent password. If anything gets through to connect (ie by taking control of one of the clients, or another way of bypassing the firewall and server policies), it still can't do anything that way.
In short, read the docs. From front to back, preferrably. Building a server takes work, a misconfigured server is worse than no server at all.
Ssh makes you log in as a normal user, so there is no real way of locking you in a certain directory (AFAIK). You can, of course, restrict ssh logins to a single user, with limited access.
-
You might be able to use NFS anyways. M$ has NFS support somewhere, you just have to dig. Also you could set up a web server and allow writing to it from the local network. Infact you could make it accessible to the local network only. But configuring SMB would be jus as easy