1833742 Members
2445 Online
110063 Solutions
New Discussion

Re: Cifsclient help

 
Gary Hines
Advisor

Cifsclient help

Hi,
I'm having trouble getting the cifsclient to work. When doing the mount -F cifs everything seems to go well. And the cifslist -A shows the share as mounted. However, when I do the cifslogin, it quickly comes back with a "Logging in User: UNIX: Host is down". Any ideas?
6 REPLIES 6
Michael Elleby III_1
Trusted Contributor

Re: Cifsclient help

Hello-

This is a quick shot in the dark, but are the Samba daemons (smbd and nmbd) running on the server, and, have you defined your user to Samba?

Mike E.
Knowledge Is Power
Gary Hines
Advisor

Re: Cifsclient help

Hi Mike,
I should have mentioned that I'm trying to connect to a Windoze 2000 computer. Since it's the CIFS client that I'm trying to use, I don't think I need the Samba daemons running.
Michael Elleby III_1
Trusted Contributor

Re: Cifsclient help

Sorry, I meant to add..

When I stated about the daemons running on the server, I meant the server that houses the local filesystem you are mounting to your client...

Mike-
Knowledge Is Power
Craig Rants
Honored Contributor

Re: Cifsclient help

I don't know too much about the W2K side of things, but I would assume that the client is trying to connect to tcp or udp port 139 on the W2K box. Can you see if that port is available and listening on that box? Maybe telnet to that port to check the tcp side of things.

GL,
C
"In theory, there is no difference between theory and practice. But, in practice, there is. " Jan L.A. van de Snepscheut
Michael Elleby III_1
Trusted Contributor

Re: Cifsclient help

Ok,

One, is your domain set to the same domainname that the W2K box is using in the /etc/opt/cifsclient/cifsclient.cfg file?

Two, is your username on the unix box a valid user in the domain, so that it can be authenticated when you attempt access to the W2K filesystem?

Mike-

Knowledge Is Power
Gary Hines
Advisor

Re: Cifsclient help

Thanks for all the help. I finally got it. One of the problems was the domain, but after fixing that the error still occurred. The problem ended up being that I didn't have the computer that I was attempting to connect to in the /etc/hosts file.