- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problems with bdf / cifsclient / samba smbclient
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2006 04:27 AM
01-30-2006 04:27 AM
Problems with bdf / cifsclient / samba smbclient
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2006 04:32 AM
01-30-2006 04:32 AM
Re: Problems with bdf / cifsclient / samba smbclient
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2006 10:01 PM
01-30-2006 10:01 PM
Re: Problems with bdf / cifsclient / samba smbclient
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2006 10:05 PM
01-30-2006 10:05 PM
Re: Problems with bdf / cifsclient / samba smbclient
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2006 06:47 AM
01-31-2006 06:47 AM
Re: Problems with bdf / cifsclient / samba smbclient
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