SEO

* AIX 5.3
oslevel -s :5300-05-06-0000
* lslpp
bos.cifs_fs.rte 5.3.0.61

Hello,
I try to mount cifs fs from windows, but there is a problem with
mountig domain controller's (windows 2003 server) fs.
With regular workstation it works (with domain account):
mount -v cifs -n 192.168.x.x/domain_user -o wrkgrp=domain1 /test /mnt

But when i try to do this with domain controllers - mount fails :
"There was an error connecting the share or the server.
Make sure the lsdev command shows that device nsmb0 is in
the Available state. Also make sure that the share name,
user name and password are accurate."

Strange is that on other server which is in domain but is not a domain
controller it works well.

In all examples we use Active Directory account (not local users).
lsdev | grep nsm :
nsmb0 Available N/A

any sugestions ?


regards
Kmet

PS. I know i can use SAMBA, but i don't want to do this.

> PS. I know i can use SAMBA, but i don't want to do this.

SAMBA does not provide CIFS or SMBFS (now old) capability for mounting
windows fileshares on an AIX box. This is available on other
platforms, but not on AIX. That's why we need the cifs_fs package.

But you can use Samba to help diagnose things.

I'm having the same problem with a share on an DC and receive the same
error as yourself.
Funny enough, same thing on Linux.

With Samba CIFS on Linux I added the port=139 option and it works.
On AIX there doesn't seem to be such an option for cifs_fs.

To test this out on AIX I used Sambas smbclient.

First, try without any port options.

smbclient '\\yourdc\sharename' -U username -W windowsdomain

It will respond with a Password: prompt and after entering the correct
password you get:

session setup failed: NT_STATUS_LOGON_FAILURE

Now try it with the port option:

smbclient '\\yourdc\sharename' -U username -W windowsdomain -p 139

Your prompted for the password and then it'll give you the smb: \>
prompt and your in.

So I'm not sure what's up with this and how to force cifs_fs to use
port 139 exclusively but digging into it further.

If you need samba to test, use the precompiled AIX binaries at
samba.org.
They work great and don't leave the bad taste of incompatibility with
other libraries as they roll their own.

I'm not having much luck with this.

I've followed some of the Samba talk on forcing port 139 but it
doesn't lead to exactly why it's needed on either the AIX or Windows
side in this case.

mkcifsmnt seems to be limited to basic options.

I see you can specify some aditional options via -o if you use the
mount -v cifs command.
Is there a full listing of what the options are?

>
> I see you can specify some aditional options via -o if you use the
> mount -v cifs command.
> Is there a full listing of what the options are?


You can use options specified in "man mount" (I used wrkgrp, which
worked well), but there are no options for changing port...

Thanks. I see there is for NFS but not for CIFS.

Looks like we are stuck until the reason behind needing it is found.

On Jun 19, 6:05 am, kme...@gmail.com wrote:
> * AIX 5.3
> oslevel -s :5300-05-06-0000
> * lslpp
> bos.cifs_fs.rte 5.3.0.61
>
> Hello,
> I try to mount cifs fs from windows, but there is a problem with
> mountig domain controller's (windows 2003 server) fs.
> With regular workstation it works (with domain account):
> mount -v cifs -n 192.168.x.x/domain_user -o wrkgrp=domain1 /test /mnt
>
> But when i try to do this with domain controllers - mount fails :
> "There was an error connecting the share or the server.
> Make sure the lsdev command shows that device nsmb0 is in
> the Available state. Also make sure that the share name,
> user name and password are accurate."
>
I got fed up with cifs on AIX. Instead of using a domain AD account
- try using an account that is local admin on the file share server
that you wish to mount up - been using it that way for years now. The
problem was that the cifs was passing the domain prefix wrongly or not
passing it at all or something like that. Check your domain
controller or AD logfile - or just us a local account.

> I got fed up with cifs on AIX. Instead of using a domain AD account
> - try using an account that is local admin on the file share server
> that you wish to mount up - been using it that way for years now. The
> problem was that the cifs was passing the domain prefix wrongly or not
> passing it at all or something like that. Check your domain
> controller or AD logfile - or just us a local account.

AFAIK there are no local accounts in windows 2003 serwer (DC).
Besides, AD accounts work well with desktops and non-DC servers...