- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: cifsmount for NT-shares
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
Discussions
Discussions
Forums
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
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
тАО02-04-2004 07:55 PM
тАО02-04-2004 07:55 PM
cifsmount \\paspcc01\smb /tmp/paspcc01
where paspcc01 is the NT-system, smb the sharename and /tmp/paspcc01 the mountpoint.
The messages I get are as follows
Remote user root's password:
Connecting Server: UNIX: Host is down
I've added the domain=bayant in the config file but that doesn't help.
paspcc01 is reachable from the Unixhost ( ping ).
I've tried the following, but with the same result:
cifsmount \\paspcc01.bayant\smb /tmp/smb -U bayant\\andco
Remote user bayant\andco's password:
Connecting Server: UNIX: Host is down
Could anyone give me hint which command to use
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 08:33 PM
тАО02-04-2004 08:33 PM
Solutionare you sure you need backslashes?
The documents I see say:
cifsmount //
See
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B8724-90044/B8724-90044_top.html&con=/hpux/onlinedocs/B8724-90044/00/00/33-con.html&toc=/hpux/onlinedocs/B8724-90044/00/00/33-toc.html&searchterms=cifsmount&queryid=20040205-023209
JP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 08:54 PM
тАО02-04-2004 08:54 PM
Re: cifsmount for NT-shares
But this brings me to the next problem:
DOS Access Denied.
This is my command:
cifsmount //paspcc01.bayant/smb /tmp/smb -U smb
The share is created with full access for everyone, and I've added user smb just to be sure. I've tried adding the -u (for unencrypted passwords) but that doesn't help.
User smb is a local user on paspcc01.
If I try a domainuser ( bayant\andco ), I get the same result.
Using the IP-adress instead of the hostname gives me:
Connecting Server: UNIX: Connection refused
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 08:58 PM
тАО02-04-2004 08:58 PM
Re: cifsmount for NT-shares
I believe you should use forward slashes, otherwise you'll need to escape the back slashes and it starts to look quite confusing!
An alternative is to use:
mount -F cifs paspcc01:/smb /tmp/paspcc01
cifslogin paspcc01 yourloginname
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 09:18 PM
тАО02-04-2004 09:18 PM
Re: cifsmount for NT-shares
# cifslogin paspcc01 smb
Remote user smb's password:
Logging in User: DOS: Access denied
Do I need to do anything special on the NT-side ?
Thanks for helping out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 09:57 PM
тАО02-04-2004 09:57 PM
Re: cifsmount for NT-shares
I seem to recall that there's something on the NT side that allows or disallows certain IPs from authenticating. It's worth manually adding your HP-UX box to the allowed list.
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 10:51 PM
тАО02-04-2004 10:51 PM
Re: cifsmount for NT-shares
got any idea where I do that ?
lmhosts ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2004 11:19 PM
тАО02-04-2004 11:19 PM
Re: cifsmount for NT-shares
I'm afraid I don't know ;(
The situation involved a fairly secure system, where only certain machines were allowed to authenticate against the PDC. The host PC was allowed to authenticate, but the CIFS client was not. Although we were logging into the host, the actual authentication request was being sent from the CIFS client to the PDC - and the CIFS client was not allowed to authenticate so it failed.
It might be worth having a chat with your NT admins to see if they're aware of this functionality.
regards,
Darren.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2007 06:09 AM
тАО03-30-2007 06:09 AM
Re: cifsmount for NT-shares
# cifslogin windows_box_ip admin
Remote user admin's password:
Logging in User: UNIX: Connection refused
#
Please suggest
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2007 08:34 PM
тАО04-10-2007 08:34 PM
Re: cifsmount for NT-shares
Just wondering what cifslist -A show you. I have expirienced this kind of behaviour as well when doing the mount using the servers fqdn and the login using just the hostname. Maybe start from scratch and make sure you're persistent in using either the fqdn or just the hostname.
Regards,
Harm