samba - Nov 1999 - using smbmount for NT share

I posted a previous thread about using smbmount, but I am still having some
problems, using samba version 2.0.5a on SuSE 6.2.

I issue the statement:

smbmount //NTServer/share /mnt/test -Iaddress -Uid%pswd

Afterwards, if I go to the mount directory, i.e. 'cd /mnt' and issue the
command 'ls -l' I get an error message 'ls: test: Input/output
error'.
After that, the mount point is pretty much hosed until I reboot the server
(I haven't looked to see how to stop the smb daemon process yet, which might
fix it as well).  I can't issue a 'umount' command without getting a
message
that the device is busy.

I have also tried running the smbmount command using debug level 9.   Along
with a dump of parameters from the smb.conf file, I get the following
messages which make it appear that the mount command is talking to the NT
Server. Is there some parameter I'm missing from the smb.conf file that
could be causing a problem?  I can use smbclient and look at the NT Server
share with no problems.

Thanks,
Cary

<some output from using -d9>
Added interface ip=xxx.xxx.xxx.xxx bcast=xxx.xxx.xxx.255 nmask=255.255.255.0
Connecting to xxx.xxx.xxx.xxx at port 139
write_socket(4,76)
write_socket(4,76) wrote 76
Sent session request
size=0
smb_com=0x0
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=0
smb_flg2=0
smb_tid=0
smb_pid=0
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=0
 session request ok
write_socket(4,168)
write_socket(4,168) wrote 168
size=97
smb_com=0x72
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=136
smb_flg2=1
smb_tid=0
smb_pid=357
smb_uid=0
smb_mid=1
smt_wct=17
smb_vwv[0]=7 (0x7)
smb_vwv[1]=12803 (0x3203)
smb_vwv[2]=256 (0x100)
smb_vwv[3]=1024 (0x400)
smb_vwv[4]=17 (0x11)
smb_vwv[5]=0 (0x0)
smb_vwv[6]=256 (0x100)
smb_vwv[7]=0 (0x0)
smb_vwv[8]=0 (0x0)
smb_vwv[9]=64768 (0xFD00)
smb_vwv[10]=67 (0x43)
smb_vwv[11]=20480 (0x5000)
smb_vwv[12]=55652 (0xD964)
smb_vwv[13]=21365 (0x5375)
smb_vwv[14]=48934 (0xBF26)
smb_vwv[15]=41985 (0xA401)
smb_vwv[16]=2049 (0x801)
smb_bcc=28
size=97
smb_com=0x72
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=136
smb_flg2=1
smb_tid=0
smb_pid=357
smb_uid=0
smb_mid=1
smt_wct=17
smb_vwv[0]=7 (0x7)
smb_vwv[1]=12803 (0x3203)
smb_vwv[2]=256 (0x100)
smb_vwv[3]=1024 (0x400)
smb_vwv[4]=17 (0x11)
smb_vwv[5]=0 (0x0)
smb_vwv[6]=256 (0x100)
smb_vwv[7]=0 (0x0)
smb_vwv[8]=0 (0x0)
smb_vwv[9]=64768 (0xFD00)
smb_vwv[10]=67 (0x43)
smb_vwv[11]=20480 (0x5000)
smb_vwv[12]=55652 (0xD964)
smb_vwv[13]=21365 (0x5375)
smb_vwv[14]=48934 (0xBF26)
smb_vwv[15]=41985 (0xA401)
smb_vwv[16]=2049 (0x801)
smb_bcc=28
write_socket(4,148)
write_socket(4,148) wrote 148
size=85
smb_com=0x73
smb_rcls=0
smb_reh=0
smb_err=0
smb_flsmbmount started (version 2.0.5a)

Cary Mader     /  Phoenix Dev Center
602-770-0241   /  cary.mader@eds.com

Email Text Messages (100 characters)
6027700241@messaging.sprintpcs.com

I don't know about Suse's kernel in this particular version, but there
used
to be an option in the smbs filesystem regarding "win95 bug
workaround". If
this option is turned on and one tries to access a NT system, something
wrong will happen. I had once problems like yours with a stock redhat 6.0
system, with kernel 2.2.5. I recompiled it without that option and it
started to work fine. I also remember some warnings on Bugtraq about this,
that one shouldn't use stock redhat 6.0 systems to access NT servers.
Newer kernels don't have this option anymore, they detect on the fly the
remote system and adjust accordingly.
Anyway, this is what happened to me. Maybe it will help you.
>I posted a previous thread about using smbmount, but I am still having some
>problems, using samba version 2.0.5a on SuSE 6.2.
>
>I issue the statement:
>
>smbmount //NTServer/share /mnt/test -Iaddress -Uid%pswd
>
>Afterwards, if I go to the mount directory, i.e. 'cd /mnt' and issue
the
>command 'ls -l' I get an error message 'ls: test: Input/output
error'.
>After that, the mount point is pretty much hosed until I reboot the server
>(I haven't looked to see how to stop the smb daemon process yet, which
might
>fix it as well).  I can't issue a 'umount' command without
getting a
message
>that the device is busy.

"Mader, Cary J" wrote:
> 
> I posted a previous thread about using smbmount, but I am still having some
> problems, using samba version 2.0.5a on SuSE 6.2.
> 
> I issue the statement:
> 
> smbmount //NTServer/share /mnt/test -Iaddress -Uid%pswd
> 
> Afterwards, if I go to the mount directory, i.e. 'cd /mnt' and
issue the
> command 'ls -l' I get an error message 'ls: test: Input/output
error'.
> After that, the mount point is pretty much hosed until I reboot the server
> (I haven't looked to see how to stop the smb daemon process yet, which
might
> fix it as well).  I can't issue a 'umount' command without
getting a message
> that the device is busy.
> 
I don't know what your problem in mounting is, or how to fix it, but to
get it unmounted properly you might try doing 'smbumount', *then*
'umount'.  This seems to be a quirk in 2.0.5 that is supposedly fixed in
2.0.6.  Who knows, maybe if you get it unmounted OK, you can then mount
it!?