AIX

Is your nsmb0 in the "Available" state after the upgrade?

Code:

hostname:/:# lsdev | grep nsmb0
nsmb0       Available       N/A

Do you see that your cifs fileset was upgraded as well?

Does this come back clean?:

Code:

lppchk -v

Hello,

Sorry to liven up an old thread but I too am having this issue and was wondering what the resolution was?

I'm wondering if the $ on the server's share is causing issues?

Code:

mount -v cifs -n serverIP/username/password /share$ /mnt/mountpoint/

"There was an error connecting the share or the server.
Make sure the lsdev command shows that device nsmb0 is in
the Available state. Also make sure that the share name,
user name and password are accurate."

Code:

aixclient:/:# lsdev | grep nsmb0 
nsmb0   Available       N/A

Now if I try to mount a public share to my PC instead of the server it doesn't return any error, but the mount point doesn't contain the shared files and it doesn't show up when you run the mount command.
What does happen is AIX creates a binary file called 'core' in the directory where it should have mounted to my machine.

Alas i can't help you with your original problem, but in this detail i can assure you it is correct. Windows names all its shares with a "$" at the end. For example, if you export "C:\" on "\\yourhost" you would see "\\yourhost\C$" remotely when browsing the network resources.

I'm not sure about more recent Windows-versions but at least NT 4.0 definitely had these shares (the local disks per default with "everybody/full control" rights on them and they were propagated as soon as you started the "server" service. This was a major security loophole back then. Most workstations could mount (for read/write even!) every other workstations harddisk without any password or other security in place.

I hope this helps.

bakunin

Hi bakunin,

Thank you for your reply, unfortunately if I mount to a shared path without a $ (hidden share) the problem still occurs.