Re: Intranets, Linux, Windows, Samba and Macs!


"Ian Gregory" <foo@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:slrnfevobo.2lv.foo@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 2007-09-18, Jolly Roger <wbyylebtre@xxxxxxxxx> wrote:
On 2007-09-17 23:17:35 -0500, Heath Raftery <hraftery@xxxxxxxxxxxxx>
said:

Wouldn't it be better to have the webserver serve the files? This ugly
combination of protocols is asking for trouble, IMHO. Just because
Windows
uses the location bar in Explorer for *everything* (CIFS, local, web,
ftp,
scary1, scary2) doesn't mean you should take advantage of it!

Instead, can't you set up your webserver to share the resource in
question
and map it to a URL? Then links to the files would simply be URLs on the
webserver, and you only have one point of failure, instead of one for
every client.

Excellent advice.

Yes, that is what I was thinking too - at least for files where
read-only access is all that is required.

If the OP wants people on various clients to be able to modify
the files in question then things are trickier, with all sorts
of locking issues (locking over NFS is a notorious source of trouble).
In any case, the starting point would surely be to remotely mount
the central filesystem on all the clients and then do local access
on the clients. Accessing everything using a remote file "URL" might
seem like a neat trick but is likely to be more trouble than it
is worth even if it can be forced to work on all clients.

Ian

--
Ian Gregory
http://www.zenatode.org.uk/ian/

Yeah, I would have a few issues with this.
1) The intranet server doesn't have enough space to accomodate all the
shared files.
2) Even if it did, the current backup drive wouldn't stretch to including
the shares.
3) The shares are exactly that, shares wich many, many users have access
too. I don't really know how I can provide the same access but keep my
intranet structure files/directory protected.

Thanks for all the input so far though.

EJ


.

Relevant Pages

  • Re: Intranets, Linux, Windows, Samba and Macs!
    ... If the OP wants people on various clients to be able to modify ... of locking issues (locking over NFS is a notorious source of trouble). ... the starting point would surely be to remotely mount ...
    (comp.sys.mac.system)
  • pxe clients with freebsd 6.0-rel ?
    ... with a 4.10-rel box as dhcp/tftp/nfs server. ... I then decided to upgrade the pxe server running RELENG_4_10 to ... boot but was still showing the file locking trouble. ... clients without the file-locking trouble I encounter over the last few ...
    (freebsd-questions)
  • pxe clients with freebsd 6.0-rel ?
    ... with a 4.10-rel box as dhcp/tftp/nfs server. ... I then decided to upgrade the pxe server running RELENG_4_10 to ... boot but was still showing the file locking trouble. ... clients without the file-locking trouble I encounter over the last few ...
    (freebsd-stable)
  • ICS Client
    ... No other network Trouble ... Now I Can Browse Internet from all computers. ... Clients) - Got nothing...... ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant browse shares in trusted domain from Client
    ... > forests. ... > validated the trust, ... > shares on the DC's in Domain A from DC's in Domain B. ... > from both clients and DC's in Domain A, ...
    (microsoft.public.windows.server.active_directory)
Loading