Hi all,

I'm trying to add a server to my network, the network consists of a modem to the internet, wireless router connected to modem, xp desktop connected via ethernet to router, win 7 laptop connected to router (wireless). The server is connected to the router via ethernet.

Here is the situation so far:
I have loaded ubuntu server 10.10 on the single 160gb hdd, I need help with the following.

1. Add a 2tb hdd and format it.
2. Add a firewall to the server.
3. Control the server from my laptop and desktop while connected to the lan and control from my laptop when on the road, openssh and putty, does the server need a static ip address to do this?
4. Access my files on the road as well as from home, samba?
5. Setting it up to auto backup pc and laptop files, rsync?

I am totally new to linux os, and command line, but would prefer to set the server up this way to help me learn.
I've read heaps and it still seems to be going straight over my head.
Are there any good walk throughs or guides for me to follow to set this up securely etc, all help appreciated.

Cheers.

I recently added a 2TB drive to my file server and wrote about it here, but I was using graphical tools.

Using command line tools, the process is fairly straightforward, along the lines of "if you already know the answer, every question is easy."

Short version:

1. Plug in the device.

2. Run dmesg and find the device in the output of the command.

3. Use cfdisk to partition it, if desired.

4. Use mkfs to format the partitions.

5. Repeat step 2 to see how the new partitions are sensed.

6. Use mkdir to create mount points under /mnt or /media.

7. Edit /etc/fstab to add the partitions to your file system table.

The first time I did this (for a thumb drive under the 2.4.x kernel), I think it took me half a day. Now, five years later, I can pretty much do it in my sleep except for the eyes having to be open thing.

Here's a description, with links about dmesg, fstab, and all that good stuff, that I wrote up about my podplayer.

Frankly, I would recommend that you install a GUI on your Ubuntu server system.

The command line is not the easiest way to start. The command line is always easier, but only if you already know the commands.

I was adept at the DOS and Windows command lines, but some things are just easier with a GUI. Once everything is configured, you should be able to log out of the GUI and your server should still serve.

The details of remote access to your file server are too much for me to type right now, but you will need your Linux server to have a static IP address and you will have to configure your router to pass your openssh traffic to your Linux box, or you can set it up as a DMZ host. If you do not do either of those, you will not be able to break through the NAT firewall to your Linux box. Keep in mind that you are opening your server to attack and SMB is not the most secure protocol, so you'll want to take precautions. If you only allow the SSH port through the router, and you require a cypher key for logging in, it will be pretty secure.

You shouldn't have any trouble accessing your box from within the LAN if you set up and configure SAMBA. Hopefully, someone else can address your rsync/remote backup questions. I haven't done much with Windoze lately.

I did not address the issues that djtoltz did, but I have some thoughts because BTDT.

Yes, your server should have a static ip inside your network so you can set your router to forward to it.

You can get dynamic DNS service that points to your router via a service such as no-ip.com or dyndns.com. (I have been a satisfied user of no-ip for quite a while. I know folks who are very happy with dyndns.)

Once you set up the dynamic dns service on your computer, set your router to forward external calls on the applicable port (usually port 80 unless your ISP blocks it, as mine does) to the static ip of your server. You also need to set your server to listen on that port and to make sure the port is open in your firewall.

Then you can connect remotely using ssh or scp (for file transfer).

I used to self-host my website, before the database outgrew my server, and ssh from remote sites helped me to fix problems from far away several times. Because I was running a website, I had Apache listening on port 80 and sshd listening on port 22.

No-ip.com has a good help file on how to set this stuff up.

Thanks very much for your help.
I will install the GUI to make sure the server is setup how I want it.
Then will tackle Command Line after that.
Cheers.

A new problem has come up after installing the GUI

Here is the link to the problem in the distro section

http://www.linuxquestions.org/questi...server-850102/

Thanks.