Topic: Samba mount problem

[René]

Hi

I had the following configuration.
- SME Server 5.1.2 (Updated from 5.0 with CD) -> Server1
- SME Server 5.1.2 (fresh install from CD) -> Server2
- Windows NT 4.0 Workstation Sp 6a -> Client1

To share Data at Client1 I would like to mount a share at Client1 from the Server1 and Server2.

I have customized the file /etc/fstab on both SME, I have ad at the end of the fstab-file this line
//client1/test  /mnt/test  smbfs  username=test,password=sme

I have created on both servers the directory /mnt/test

then I have restart both servers

Now when I would like to mount I get the following:

On the Server2
[root@server2 /]# mount /mnt/test/
[root@server2 /]#

and now I can access over the mount point the share files at Client1

On the Server1
[root@server1 /]# mount /mnt/test/
2926: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
SMB connection failed
[root@server1 /]#

and now I can not access over the mount point the shared files at Client1

Has anyone an idea, what could be wrong?

Thanks for any suggestions
René

[BYte]

u havent added the -o username=test,password=sme

just something that might be stopping this from happening

try!

also is your nt workstation in NTFS format if so then this wont work as the kernel does not have nfs installed  which uses portmap

Hopes this gives you some help

[René]

BYte

when I ad the "-o" option in /etc/fstab I could not more connect without both servers I get at both servers the same error message:

[root@server2 /mnt]# mount /mnt/test/
[mntent]: line 12 in /etc/fstab is bad
mount: can't find /mnt/test in /etc/fstab or /etc/mtab
[root@server2 /mnt]#

line 12 is the line in which the mentioned entry is.

Yes, it is right my nt workstation has a NTFS formatted drive. But I think that is not the problem, because one of the servers could connect to the share at the client (client1) and copy there some files or dirs.

any others suggestions??

René

[Filippo Carletti]

> when I ad the "-o" option in /etc/fstab I could not more

You should omit "-o", write only username=... in fstab

> Yes, it is right my nt workstation has a NTFS formatted

NTFS doesn't play here, it's smbfs.

Try to connect using
smbclient //server/share -U username
and type the pass.

[René]

Filippo

at the server2 the command work well

[root@server2 /mnt]# smbclient //client1/test -U test
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=172.16.1.200 bcast=172.16.1.255 nmask=255.255.255.0
Got a positive name query response from 172.16.1.20 ( 172.16.1.20 )
Password:
Domain=[DOMAIN] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
smb: \>

but at the server1 I have still an error message

[root@server1 /mnt]# smbclient //client1/test -U test
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=172.16.1.106 bcast=172.16.1.255 nmask=255.255.255.0
Got a positive name query response from 172.16.1.20 ( 172.16.1.20 )
Password:
session setup failed: ERRDOS - ERRnoaccess (Access denied.)
[root@server1 /mnt]#

any other information?

René

[Des Dougan]

It very much looks to me that you're trying to mount both shares to the same mount point at the same time. Just as you can't be in two places at once, you can't mount two shares to the same place. Why don't you create /mnt/test and /mnt/test2, make the necessary /etc/fstab changes and then try the mount command?


Des Dougan

[Filippo Carletti]

- smbclient -d 4
 - tcpdump

[René]

@Des Dougan

I think it is not exactly the same as I would be at the same time in two different places. I am only pointing (with a mount point) with two servers at the same time to the same share on a Windows NT workstation. I think that should be possible. Or not?

@ Filippo Carletti

I am not an expert in SME/Linux and so I don't no what I should do with this two commands
smbclient -d 4 reports me an option list. Could I also use the command smbclient for use with /etc/fstab?

tcpdump reports me
root@mm-sme2 /root]# tcpdump
bash: tcpdump: command not found
[root@mm-sme2 /root]#

For further information thanks in advance

René

[Filippo Carletti]

Add '-d 4' to your smbclient command line (more debugging info).

[René]

@ Filippo Carletti

When I put in the option "-d 4" in the smbclient command line, I get a lot of information before I could enter the password for the user to connect to the share. But after input the password I get not anymore information as before.

[root@server1 /root]# smbclient //client1/test -U test -d 4
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=172.16.1.106 bcast=172.16.1.255 nmask=255.255.255.0
Client started (version 2.2.2).
resolve_wins: Attempting wins lookup for name client1<0x20>
resolve_wins: WINS server == <127.0.0.1>
bind succeeded on port 0
nmb packet from 127.0.0.1(137) header: id=31955 opcode=Query(0) response=Yes
    header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
    header: rcode=3 qdcount=0 ancount=1 nscount=0 arcount=0
    answers: nmb_name=CLIENT1<20> rr_type=32 rr_class=1 ttl=0
Negative name query response, rcode 0x03: The name requested does not exist.
resolve_lmhosts: Attempting lmhosts lookup for name client1<0x20>

René
getlmhostsent: lmhost entry: 127.0.0.1 localhost
name_resolve_bcast: Attempting broadcast lookup for name client1<0x20>
bind succeeded on port 0
nmb packet from 172.16.1.20(137) header: id=16688 opcode=Query(0) response=Yes
    header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
    header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
    answers: nmb_name=CLIENT1<20> rr_type=32 rr_class=1 ttl=300000
    answers   0 char .....   hex 6000AC100114
Got a positive name query response from 172.16.1.20 ( 172.16.1.20 )
Connecting to 172.16.1.20 at port 139
 session request ok
Password:
session setup failed: ERRDOS - ERRnoaccess (Access denied.)
[root@server1 /root]#

[Filippo Carletti]

Have you tried connecting to client1 from another pc ?

[René]

Filippo

Yes, I have tried to connect from a Win 2000 Server and also from an other SME 5.1.2. From boths no problems. I could only not connect from the one SME 5.1.2 Server to this client 1 (Windows NT 4.0 Workstation).

René