logo       

Can't read anything on mounted share: msg#00037

linux.file-systems.cifs

Subject: Can't read anything on mounted share

I am using cifs to mount windows 2003 server shares like this


# mount -t cifs //hostname/d /mnt/temp/ -o username=mydomain/administrator
Password:
mount error 20 = Not a directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)


But it is a directory!


# ll /mnt/
total 16
drwx------ 2 root root 4096 Aug 3 15:23 cdrom/
drwx------ 2 root root 4096 Aug 3 15:23 floppy/
drwxr-xr-x 2 root root 4096 Oct 18 12:53 temp/
drwxr-xr-x 2 root root 4096 Oct 17 10:24 usb/


I'm quite stuck on this. Is it a bug or what?


If I try smbfs instead then I get the following:

# mount -t smbfs //hostname/d /mnt/temp/ -o username=mydomain/administrator
Password:
18751: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
SMB connection failed


Why am I getting error denied or these strange results when I know the password is correct, I use it all the time and I have tried it several times...


I'd much appreciate it if anybody could help out on this. I have the same problem from all my linux machines trying to connect to any Windows 2003 server in my new Active Directory 2003 domain. Windows 2000 servers connect fine, as do XP Sp2 workstations. I have this problem on all Windows 2003 servers that I can tell including domain controllers and member servers (non domain controllers).

I have tried making the group policies for the domain as follows:

Domain member: Digitally encrypt or sign secure channel data (always) disabled
Domain member: Digitally encrypt secure channel data (when possible) disabled
Domain member: Digitally sign secure channel data (when possible) disabled

Microsoft network client: Digitally sign communications (always) disabled
Microsoft network client: Digitally sign communications (if server agrees) disabled

Microsoft network server: Digitally sign communications (always) disabled
Microsoft network server: Digitally sign communications (if client agrees) disabled

Domain Controller: LDAP server signing requirements none
Network security: LDAP client signing requirements none

Network security: Lan Manager authentication level Send LM & NTLM responses


In the Windows logs I get

Dec 18 14:18:50 hostname security[failure] 529 NT AUTHORITY\SYSTEM
Logon Failure:
Reason:Unknown user name or bad password
User Name:ROOT
Domain:MYDOMAIN
Logon Type:3
Logon Process:NtLmSsp
Authentication Package:NTLM
Workstation Name:\\x.x.x.x
Caller User Name:-
Caller Domain:-
Caller Logon ID:-
Caller Process ID:-
Transited Services:-
Source Network Address:x.x.x.x
Source Port:0

I don't understand why it says ROOT instead of administrator for username?

The linux hosts are not members of the domain and have not been integrated to use kerberos or anything like that yet, but they do have the right username and password for the domain admin account.

So why doesn't this work?


-h

--
Hari Sekhon


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise