Re: Fileserver question

From: David Wright (david_c_wright_at_hotmail.com)
Date: 06/17/04 

Date: Thu, 17 Jun 2004 17:21:49 +0200

Marko Ramius wrote:

> I want to set up a fileserver running Suse 9.0, accessible from another
> box running both 9.0 and Windows. I currently have both computers in the
> same room and connected to a router. What is the simplest way to set up
> the fileserver? Connect it to the other comp with another ethernet card
> or use the router? I am willing to ditch the router if it means
> simplicity as I am not at all a "computer geek".
>
>
> Charlie

Connecting through the router is easier, you just need standard patch
cables, going directly you need a crossed cable, which isn't always as easy
to come by.

Does the router support DHCP? If so, it is easiest to connect the two
computers to the router and allow them to get their IP information from the
router, otherwise you will need to run a DHCP server on one of the
machines, preferably the server, or give both machines static addresses -
with a 2 machine network, it doesn't make much odds which way you do it,
although using fixed addresses (if the machines aren't being constantly
moved from network to network E.g. LAN Parties etc.) can be easier to get
to grips with, as the address of the server and the workstation won't keep
changing...

Once the two machines are connected to the router and have IP addresses in
the same range (something like 192.168.0.1 and 192.168.0.2 sub-net mask
255.255.255.0 - this will depend on the address the router uses), you
should be able to ping them (ping command from the command line, same
command under both Windows and Linux). Also make sure that both machines
are using the same domain/workgroup name, otherwise they won't be able to
see each other for SMB share.

Once you can ping the machines from each other, you need to set up the
server to give out NFS and Samba shares, Windows can only use SMB shares by
default, so you must use Samba in any case. When the second machine is
booted into Linux, it can use the Samba client to access the same shares,
or natively it can access an NFS share. It is your choice which way you go.

NFS is the native format, so *should* have less problems, but if you are
running Samba for when the machine is in Windows mode, using the Samba
Client in Linux mode as well means you only have one set of shares to
configure and maintain...

Does the router also serve your internet connection, or will you be doing
that through the server? If the latter, you need to also enable port
forwarding on the Linux box and set the default gateway on the other
machine to point to the server.

I hope that is enough to get you started.

The steps aren't that complicated, but they can be a bit longwinded. There
are plenty of HowTo's on the net. Post again when you have started to
configure and you need further advice...

Dave

Relevant Pages

  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • Re: Network Problem
    ... It is presently on a dual boot system with Kubuntu and Windows XP. ... the only way for your Ubuntu Box...or any other Linux box to converse with your 2wire router is via ethernet *not* USB. ... in between the #1 & #2 computers and then connecting it to the ethernet connection on the Modem/Router or I'll need to purchase a Wireless card to connect the #1 computer to the 2Wire. ...
    (Ubuntu)
  • Re: Low-bandwith ADSL, or something? (mostly off-topic)
    ... >> The motivation is my father, whose (Windows) box has been infected ... So part of a solution would be connecting via an ADSL ... initiated externally (for example one through an ADSL router that has ...
    (uk.comp.os.linux)
  • Re: The network cant see past our router - the HPUX half, anyway
    ... > PCs running Windows NT/2000, one running NT server, two sparcstations, ... It is a Cisco 1601/1603 router. ... > but I can't get the UNIX machines to see past the router to get this ... You need a two step route, ususally, i.e. ...
    (comp.sys.hp.hpux)
  • Re: The network cant see past our router - the HPUX half, anyway
    ... > PCs running Windows NT/2000, one running NT server, two sparcstations, ... It is a Cisco 1601/1603 router. ... > but I can't get the UNIX machines to see past the router to get this ... You need a two step route, ususally, i.e. ...
    (comp.unix.questions)