cifslogin is not working

[Timothy P. Jackson]

Hello everyone,

I am setting up a new cifs mount from HP-UX 11i and Windows Server 2003. The share point on the WS server has full control permissions on it. I use the following command to mount the share.

mount -F cifs serv1:/data1 /mnt1

When I try the following cifslogin command it errors out.

cifslogin serv1 cifsunix -P cifsunix -s

The error message I get is

"Logging in user UNIX: host is down"

Notice the wrong user name in the error message. The server is up because I can map to it from my desktop. I am sure it is a permissions problem but I cannot seem to find where.

I do have other cifs mounts working from this HP to other servers using the same login and password, so I am pretty sure the problem is not on the HP side.

Any help would be greatly appreciated!

Thanks,
Tim

[Paul Sperry]

Try:

cifsmount "///" -U -P -I


make sure matches theFull computer name

[Eric Raeburn]

Hello, Tim,

This is Eric from the HP CIFS Client software lab. Here is my assessment of the situation.

First, the methods and syntax you illustrate are correct. Your comment about a "wrong user name" I assume to be in reference to the string "UNIX" in the error message. In fact, in this error message, "UNIX" refers to a general class of errors (as opposed to, say, "server" or "transport"). In the case you present, the Unix error indicates a name-resolution problem, that is, the CIFS Client, using standard Unix name-resolution services, is unable to get the IP address of your "serv1".

If this is correct, then the suggestion posted previously by PaulS (specifying the server's IP address when mounting) should work. However, the advice to use the "full" computer name, which I take to mean the "fully qualified DNS name", is not necessary. When the IP address is specified, all name-resolution routines in the CIFS Client are bypassed, hence the fully-qualified name is not needed; the server name specified when mounting should be equal to the server's NetBIOS name, which is the "Computer Name" on the Windows system.

If specifying the IP address of the server is a sufficient solution for your purposes, you have four options. (1) Use "cifsmount" with the "-I ipaddress" option, as shown in the previous post. (2) If you prefer to use the "mount" and "cifslogin" commands, rather than "cifsmount", you can specify the IP address thus:

mount -F cifs -o ipaddr= server:/share /mntpt

and follow that, of course, with "cifslogin". (3) Create a server-specific section in the configuration file, specifying the IP address there. (4) If /etc/nsswitch.conf on the HP-UX host is configured such that "files" is an option for the "hosts:" entry, you can place an entry for the server in /etc/hosts.

It looks like you are using version A.01.xx of the CIFS Client, which uses only DNS for name resolution. If your system is HP-UX version 11.11 or later, I urge you to upgrade to the latest CIFS Client, available free at software.hp.com. Starting with version A.02.01, we also support NetBIOS (including WINS), making the issue of name resolution much easier for the user. The A.02.xx versions contain many other improvements as well.

Please post your results and let me know if any of this requires further clarification.

-Eric

[Timothy P. Jackson]

Thanks Eric and Paul for you response!

Sorry about the delay in posting, I was sent out of town suddenly. Any way, I used the command....

mount -F cifs -o ipaddr=10.96.5.20 :/ /

This seemed to solve the error message when I use the cifslogin but when I do a bdf I get an I/O error. If I do a cifslist -A it does not show anyone logged in for that cifsmount.

Any Ideas would be greatly appreciated

Thanks,
Tim

[Eric Raeburn]

Tim,

The best way to procede from here is for you to place a support call to HP. There is no obvious cause for these problems, though a server shutdown or reboot could be it (just a guess at this point). To make a better determination of the cause we would need to see a CIFS Client log with appropriate log levels enabled (support can advise you on this). It would also be helpful (though not absolutely necessarily) to see a network trace from a tool like tcpdump or tethereal.

Before you call HP support, please determine:

(1) whether the two errors occur immediately or if some amount of time must first transpire
(2) whether you can easily reproduce the problem

If you call HP support (which I urge you to do, unless my hunch above turns out to be true), mention that you have already "discussed" this issue here with Eric from the CIFS Client lab.

Thanks,
-Eric