Re: Fileserver question

From: Marko Ramius (mine??_at_haha!!.com)
Date: 06/18/04 

Date: Fri, 18 Jun 2004 11:07:02 -0500

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?

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

Relevant Pages

  • Re: New install into existing subnet
    ... over to exchange sometime next week. ... Disable the DHCP server on the router, ensure the SBS box is the ... Ensure that all machines with fixed IP addresses are ...
    (microsoft.public.windows.server.sbs)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: How do I see users that logged in ?
    ... - I know W98 machines should be migrated, but there are to many hindrances: ... Each subdirectory contains sub-subdirectories like administration, drawings, ... I know you can use the $ to share in windows, ... Can you log on to the server as user X and log on localy as user Y ??? ...
    (microsoft.public.windows.server.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... thesystemtimeis jumping ahead an additional ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ...
    (microsoft.public.windowsxp.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
    (microsoft.public.windowsxp.general)