Operating System - HP-UX
1833875 Members
1958 Online
110063 Solutions
New Discussion

Problems with bdf / cifsclient / samba smbclient

 
Jan Verheijen
Occasional Advisor

Problems with bdf / cifsclient / samba smbclient

NFS access failed for server bakvi3409: RPC: Remote system error
NFS fsstat failed for server bakvi3409: RPC: Remote system error
bdf: /opt/bse/exchange/edi/soh/YAS2: I/O error

cifslogin bakvi3409 -s root
Remote user root's password:
Logging in User: UNIX: No such device or address

smbclient //bakvi3409/interface -U root added interface .....
Got a positive name query response from Password:
session setup failed: NT_STATUS_NO_LOGON_SERVERS
Live Today
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: Problems with bdf / cifsclient / samba smbclient

Shalom Jan,

It appears your machine has lost its trust relationship with the domain.

You may need to have the domain controller reset the trust relationship.

You may need to do a net join (net command is in /opt/samba/bin) to rejoin the domain. This will require a password from the primary domain controller.

Note that cifsclient runs on top of the NFS client, hence the NFS errors.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Jan Verheijen
Occasional Advisor

Re: Problems with bdf / cifsclient / samba smbclient

domain is optional so thats not the problem!
Live Today
Jan Verheijen
Occasional Advisor

Re: Problems with bdf / cifsclient / samba smbclient

On another Unix machine it's working !
Live Today
Eric Raeburn
Trusted Contributor

Re: Problems with bdf / cifsclient / samba smbclient

Jan,

First, it looks like you are using a fairly old version of the CIFS Client (A.01.xx). In the latest version, A.02.01, NetBIOS name resolution was introduced. I believe this is relevant to your situation, because the error message you get grom cifslogin indicates that the cifs client is unable to resolve the address of the server bakvi3409. This would occur, for example, if the server is in a different DNS domain from the client, or if the server's NetBIOS name is different from its DNS name.

Also, have you mounted the server (cifsmount or 'mount -F cifs ...')? In the earlier versions of the cifs client, you could not do cifslogin without mounting first.

I recommend two options:

(1) Specify the IP address of the server on the command-line when you mount it, or,

(2) Upgrade to A.02.01 (available at software.hp.com -- click "Internet-ready and networking"), and try again.

Please post your results.

-Eric