Mailinglist Archive: opensuse-edu (103 mails)

["Alan Davies" <staff.asd@xxxxxxxxxxxxxxxxxxxxxxxx>]

On Mon 04 Dec, Gary Stainburn wrote:

> 
> > smbmount //server/share /mnt/mountpoint
> 
> Sorry.  I wrongly assumed that you'd used the normal unix 'mount' command 
> before and understood mountpoints.

I would like to say - publically - that I am very greatful for the help
received.  I realise that thinking down to my level requires considerable 
effort!

> In keeping with this idiom, everything starts from a root (/) partition.  
> Other partitions are connected (mounted) at specific points on this root 
> partition. The boot partition (/dev/hda5 on my system) is mounted on 
> /boot, thus once mounted, you access that partition by 'cd'ing into 
> /boot.

Getting it to do this was my problem.

> 
> Mount -t smb and smbmount work similarly, but allow you to do the same 
> with a remote Win9x share.  It mounts the remote service as part of the 
> local system's directory tree structure.  For example, I have a directory 
> on my local system called /mnt/smb. If I mount a remote SMB service, I 
> put it there so I always know what I've done with it (although running 
> mount without arguments would tell me that anyway).
> 
> Hope this makes things a little clearer for you.

So - creating a 'mountpoint' is effiectively creating a link to an already
exisiting directory entry (it doesn't produce that direcotry entry for you?)

I had mistakenly assumed that smbd and nmbd were running be default - as smbclient
worked fine.  I know understand that smbclient works independently and in the
opposite direction to those daemons. (I know know about the extra options for
ps command...)

So I now hvae swat running, smbd, nmbd running and my LINUX box appears in the
browse list of by NT domain. smbmount now works and I can connect to my NT share
and/or home directory on NT system.

Which all brings me to the final problem...connecting to the LINUX box from a 
remote station.  (smbclient //localhost/test -U% works fine)


My test samba config file is:

[global]
log level=1
max log size = 1000
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest ok = no
workgroup=BHEADS  (my NT Domain name so that it appears in the right browse list)
[homes]
browseable = no
map archive = yes
[printers]
path = /usr/tmp
guest ok = yes
printable = yes
min print space = 2000
[test]
browseable = yes
read only = no
guest ok = yes
public = yes
path = /test


Entering the share from the brwose list on the NT server brings up a 
logon/password box (which surprises me - as I thought guest logon was ok).

Using a LINUX username and password The subsequent error message on the NT box reads 
'The account is not authorised to login from this station'

Is this a problem with encrypted passwords?  I add the line 'encrypt passwords= yes'
to my smb/conf file (as per page 73, Reilly)  and ....testparm doesn't like it.

Later in Reilly it states 'encrypted passwords = yes' which it also doesn't like.

What should it be?  Perhaps I should ask NT to do password authenication..

The hosts.deny file only contains a http-rman: all line.

-- 
Alan Davies
Head of Computing
Birkenhead School