Re: Fileserver question
From: David Wright (david_c_wright_at_hotmail.com)
Date: 06/20/04
- Next message: Floyd L. Davidson: "Re: Does IBM REALLY support Linux?"
- Previous message: Hendrik van Hees: "Re: 9.1 student ver = full prof version?"
- In reply to: Marko Ramius: "Re: Fileserver question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 20 Jun 2004 16:49:50 +0200
Marko Ramius wrote:
> David Wright <david_c_wright@hotmail.com> wrote in
> news:casctc$ild$00$1@news.t-online.com:
>
>> 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
>>
>
> Dave,
> I have, through your initial suggestion of using the router,
> managed to get the file server up and running. It is accessible from
> both Suse and Windoze.
>
> There are two remaining issues, one trivial
> and one potentially major. The trivial issue is that in Win, the
> shares do not show up in the network neighborhood. They did, but I
> was having windows-related problems accessing the server and moved
> them from that folder. I now cannot see them again, even with a
> refresh. I can, however, still access the shares from where I moved
> them to. Any thoughts on getting them to show in the network
> neighborhood?
>
Hmm, sorry haven't experienced that problem... You have drag-and-dropped the
folders to a new location? Where did you move them to?
Alternatively, try selecting "Network Neighbourhood"->"whole
network"->"Microsoft Windows Networks"->your workgroup. This should list
all severs within your workgroup and allow you to then select a server and
look at its shares. It isn't elegant, but it should work.
Not sure why Windows gets rid of things in Network Neighbourhood, but
sometimes they appear to be there, other times they disappear. Possibly
something to do with browseability when booting. But going through the
whole network and reselecting the workgroup should list all shares again.
> The potentially major concern is security on the
> server. I want ONLY my machine to have access to the server. The
> router does serve as a DHCP server so (I think) the two machines
> have static IP's. Of course, I have a strong password but I am
> still concerned about server security. Any thoughts on this? Again,
> thanks for your excellent help.
>
> Charlie
If they are being served by DHCP, unless you have specifically told the
router to give them a fixed address (based on their MAC address), then they
will not have fixed IP addresses. They will be served out of the pool. BUT
if the server is always switched on first and the client 2nd, then they
should always be served the same addresses...
I assume by your question, that your router is serving as an internet
gateway. If the router doesn't provide a firewall to the outside world,
then your have a couple of choices...
But firstly, go to shields-up (https://grc.com/x/ne.dll?bh0bkyd2) and use
their test mechanism to see which holes are being left open to the
internet. Then, after you have implemented a security system to your
liking, go back and make sure you are protected.
1. If you have an old machine kicking around (or can find one cheap), then
download a firewall installation such as IP Cop or Smoothwall (there are a
few others out there as well). This sits on your router and acts as an
internet gateway (using either modem, USB, or second Ethernet card to
connect to your modem, ISDN TA or DSL modem, depending on how you are
connected. This should block all attempts at outsiders trying to get into
your network. (Using Shields-up and with no local firewall on my Linux box,
Shields-up is reporting, apart from Ping, that my machine doesn't exist).
2. Install a router that has a built in firewall, a basic router based
firewall is better than nothing at all, but I haven't played with one, so I
don't know how good they are, Netgear and Linksys (among others) produce
these.
3. Install personal firewalls on each machine. SuSE comes with a built in
firewall and can be configured through YaST. I haven't configured it myself
and don't know how it plays as a personal firewall. Under Windows, there
are many firewalls, I use Norton, along with Norton AV, but there are some
free ones such are Kerio (www.kerio.com), Outpost Personal Firewall
(www.agnitum.com), Securepoint Personal Firewall (www.securepoint.cc),
Sygate Personal Firewall (www.sygate.com) and Zone Alarm
(www.zonelabs.com).
(a quick Google on 'Linux "personal firewall"' listed a range of products
and reviews. Try also http://www.all-internet-security.com/firewall/).
If you have a spare machine (mine is a Pentium 133/64Mb RAM/2Gb HD and is
more than capable of serving my small network), then a standalone firewall
is an ideal solution (you only need to configure and update 1 firewall,
although I also run a personal firewall under Windows to stop trojans and
worms getting out - until now, I haven't recieved/caught a
worm/virus/trojan, but I'll still keep running the security, just in
case...
Hope this helps.
Dave
- Next message: Floyd L. Davidson: "Re: Does IBM REALLY support Linux?"
- Previous message: Hendrik van Hees: "Re: 9.1 student ver = full prof version?"
- In reply to: Marko Ramius: "Re: Fileserver question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
