hi everyone
months ago i installed software on hp-ux box. So instead of going to the server room (which is far and cold :) ), I put the DVD in my windows xp box and mount it using CIFS, it was successful.
Now I want to install another software on the same hp-ux box using the same windows... (3 Replies)
I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access. # mount -t cifs //servername/sharename /mnt/temp -o password=""
mount error 13 = Permission denied Refer to the... (3 Replies)
Hello,
I've been using AIX cifs to mount windows XP shares with no problems till now.
Now it's Windows Server 2008 R2 - no go:
mount -v cifs -n host1/user1/pass1 /share1 /mountpt1
There was an error connecting the share or the server.
Make sure the lsdev command shows that device nsmb0 is in... (6 Replies)
Hi all,
We are experiencing below mentioned error on mounting windows Share on AIX 5.3 when we migrate our TL from 8 to TL12-SP01, we also checked the allowed password length for mounting CIFS which is fine(10 characters in our case). On IBM fix central site there is a fix IZ63140 for... (10 Replies)
Dear Experts,
Im facing a unique situation. We got a windows server folder cifs mounted on my AIX server. Before restarting the win server I tried unmounting the cifs mount. It got hanged and win server was restarted however.
Now Im trying to mount the same. It prompts for password... (3 Replies)
Hi
i have some problem to mount a Windows Server 2008 R2 share on AIX. I found the artikel 157701-aix-cifs-mount-windows-server-2008-share on the Forum (cant post the Link) witch decribe my situation but there is no solution.
I can mount a share to a Windows 2003 SP2 Server but not to 2008 R2... (2 Replies)
hi,
I have the following permission problems with cifs.mount : a share on a VNXe (EMC NAS) is accessed by two RHEL 5.9 accounts (authenticated by Active Directory); One account has read+wite permission to the share , the second one has only read permission. Both accounts uses the following... (0 Replies)
On Slackware14.0
Compiled cifs-utils with kerberos support
on request-key.conf added
create cifs.spnego * * /usr/sbin/cifs.upcall %k %d
But when i try
mount -o sec=krb5 -t cifs //SLACK64//Users /media/users
mount error(38): Function not implemented
Refer to the... (1 Reply)
Hi,
I can't find any documentation of all available mount options of mount -v cifs
Unfortunately you can specify any fantasy options, no complains, and the mount command shows this option
In particular I want to know if there is a possibility to completely disable cifs caching in aix,... (3 Replies)
I have a Linux server with a cifsmount, the entry in /etc/fstab looks like this: //windows_server_name/xyz /opt/xyz cifs credentials=/etc/creds/xyz.creds,uid=abc,gid=abc,noserverino,directio,_netdev 0 0
The username and password are stored in /etc/creds/xyz.creds
This works fine.:wall: How... (1 Reply)
Discussion started by: Joke Holmer
1 Replies
LEARN ABOUT REDHAT
lsdev
LSDEV(8) Linux System Manual LSDEV(8)NAME
lsdev - display information about installed hardware
SYNOPSIS
lsdev
DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.
OPTIONS
None.
FILES
/proc/interrupts
IRQ channels.
/proc/ioports
I/O memory addresses.
/proc/dma
DMA channels.
BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use
different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
`keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).
The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the
`serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in
itself.
This program only shows the kernel's idea of what hardware is present, not what's actually physically available.
SEE ALSO procinfo(8).
AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl>
3rd Release 1998-05-31 LSDEV(8)