Ok here goes... I have an NT 4.0 box with the C drive shared.

Im trying to access the drive from linux using samba...

If I use samba client ex: smbclient //FILESERVER/C everything is rosey, I get the samba command prompt, and can navigate through the directory structure, see files, and do whatever samba allows...

However....

If I try to mount the Windows share ex: smbmount //FILESERVER/c /mnt/fileserverc, the share mounts, but... if I navigate into the mount point and do and ls... I get the following:

ls: A: No such file or directory
ls: A: No such file or directory
ls: b: No such file or directory
ls: C: No such file or directory
ls: C: No such file or directory
ls: C: No such file or directory
ls: D: No such file or directory
ls: D: No such file or directory
ls: I: No such file or directory
ls: M: No such file or directory
ls: M: No such file or directory
ls: N: No such file or directory
ls: n: No such file or directory
ls: p: No such file or directory
ls: P: No such file or directory
ls: R: No such file or directory
ls: T: No such file or directory
ls: W: No such file or directory
. ..

Now, the strange thing is that this list shows the first letter of all of the top level directories on the Windows C drive... but of course I cant move into them, see files, etc. like I can with smbclient.

Am I missing something?

The share has permissions of full control for everyone, and contains an NTFS file system.

Hi!

You shoud really connect with a known Windows user.
mount -t smbfs -o username=<ntusername>,password=<password> //<host>/C\$ <mountpoint>

HTH

Bob

I tried that too... same problem.

Hi!


What servcie pack of nt 4.0 have you got? Encryption changes happened after SP4? What version of samba?


You can inctrease the logging level in smb.conf to a higher level -

log level (G)

The value of the parameter (an integer) allows the debug level (logging level) to be specified in the smb.conf file. This is to give greater flexibility in the configuration of the system.

The default will be the log level specified on the command line or level zero if none was specified.

Example: log level = 3
This will give you an idea of where to troubleshoot. You can also log individual machines via -
# this tells Samba to use a separate log file for each machine
# that connects
log file = /usr/local/samba/var/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

Cheers

Thanks, but Ive figured it out...

I needed to upgrade to the latest version of Samba. I was running 2.2, now Im running 3.? and all is well.