samba - Mar 2004 - samba on nfs server or client

Hello all. I hope this question is not too dumb, but
I thought I'd ask it anyway since I'd like to get the
opinion of the samba gurus out there. My question is
this:

-- is it better to run smbd and nmbd on a server that
acts as a NFS server and has disks directly attached to it
or is it better to run samba on a seperate machine that
acts as a client to the NFS server?

In other words, in the first scenario, there is no "middleman"
server sitting between the NFS server and the windows client.
Are there any advantages / disadvantages to this approach?
It seems that this would be faster than having a dedicated
samba server that acts as an NFS client since NFS calls are
removed from the picture. Any insight on this is appreciated
as I am purely speculating. Thanks.

--Venkata

On Wed, 2004-03-24 at 08:29, Venkata wrote:
> Hello all. I hope this question is not too dumb, but
> I thought I'd ask it anyway since I'd like to get the
> opinion of the samba gurus out there. My question is
> this:
> 
> -- is it better to run smbd and nmbd on a server that
> acts as a NFS server and has disks directly attached to it
> or is it better to run samba on a seperate machine that
> acts as a client to the NFS server?
> 
> In other words, in the first scenario, there is no "middleman"
> server sitting between the NFS server and the windows client.
> Are there any advantages / disadvantages to this approach?
> It seems that this would be faster than having a dedicated
> samba server that acts as an NFS client since NFS calls are
> removed from the picture. Any insight on this is appreciated
> as I am purely speculating. Thanks.
No, it will always be both slower and more dangerous to run Samba on an
NFS client.  Slower, because the traffic must traverse 2 network links. 
More dangerous, because Samba cannot detect NFS access to the files it
shares, and therefore Oplocks break.

Always run just one file-server, sharing out multiple protocols (if
possible).

Andrew Bartlett

-- 
Andrew Bartlett                                 abartlet@pcug.org.au
Manager, Authentication Subsystems, Samba Team  abartlet@samba.org
Student Network Administrator, Hawker College   abartlet@hawkerc.net
http://samba.org     http://build.samba.org     http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.samba.org/archive/samba/attachments/20040324/3571454d/attachment.bin

Greetings Admin,

I'm trying to setup samba 2.2.8a, with domain authentication, to 
interface with CUPS 1.1.20 on debian linux.

I'm having problems running the cupsaddsmb command to copy the CUPS 
drivers to the samba [print$] share.  I am getting a "tree connect 
failed: NT_STATUS_BAD_NETWORK_NAME" error.

Could someone please let me know how to fix this?

much appreciated,
Ryan

HERE IS THE ERROR

cups:/usr/local/samba/bin# cupsaddsmb -v -H printserv -U SOMEUID -a
Password for itadmin required to access cups via SAMBA:
Running command: smbclient //cups/print\$ -N -U'SOMEUID%SOMEPASSWORD' 
-c 'mkdir W32X8
6;put /var/spool/cups/tmp/4060b6407542b W32X86/oa-c152-e1.ppd;put 
/usr/share/cup
s/drivers/cupsdrv5.dll W32X86/cupsdrv5.dll;put 
/usr/share/cups/drivers/cupsui5.d
ll W32X86/cupsui5.dll;put /usr/share/cups/drivers/cups5.hlp 
W32X86/cups5.hlp'
added interface ip=142.55.100.54 bcast=142.55.100.255 
nmask=255.255.255.0
Got a positive name query response from 142.55.100.62 ( 142.55.100.54)
Domain=[SHERNET] OS=[Unix] Server=[Samba 2.2.8a]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

HERE IS MY SMB.CONF

[global]
         workgroup = SHERNET
         netbios name = printserv
         log file = /usr/local/samba/logs/%m.log
         max log size = 50000
         debug level = 1
         name resolve order = wins host bcast

         wins server = win2k.sheridanc.ca
         wins proxy = no
         wins support = no
         dns proxy = yes
         local master = no
         preferred master = no
         domain master = no
         os level = 0
         security = domain
         encrypt passwords = true
         password server = *

         interfaces = 142.55.100.54/24
         allow hosts = 142.55. localhost
         hosts deny = 142.55.27.201

         printing = cups
         printcap = cups
         load printers = yes
         socket options = TCP_NODELAY

[printers]
         comment = All Printers
         path = /var/spool/samba
         browseable = no
         guest ok = yes
         public = yes
         writeable = no
         printable = yes
         printer admin = pc
         create mode = 0700

[print$]
         comment = Printer Drivers
         path = /usr/local/samba/drivers
         browseable = yes
         guest ok = no
         read only = yes
         write list = root