When logged in to a machine via copSSH (1.3.6) and attempting to access a network resource, I get (after a 20 second delay):
-bash-3.00$ ls //ntdesk/spool
ls: //ntdesk/spool: Permission denied
Yet when running the Bash shell directly on that machine as the same user, I get:
bash-3.00$ ls //ntdesk/spool
System Volume Information
According to this (ran locally):
bash-3.00$ ls -al //ntdesk
dr-xr-xr-x 1 Tom Metro mkpasswd 0 Dec 10 13:34 .
dr-xr-xr-x 1 Tom Metro mkpasswd 0 Dec 10 13:34 ..
drwxr-xr-x 1 Tom Metro mkpasswd 0 Dec 5 13:17 spool
I should have access to it.
Running that remotely produces:
-bash-3.00$ ls -al //ntdesk
ls: reading directory //ntdesk: Bad file descriptor
dr-xr-xr-x 1 Tom Metro None 0 Dec 10 13:38 .
dr-xr-xr-x 1 Tom Metro None 0 Dec 10 13:38 ..
I tried touching a file, both remotely (test) and locally (test2), to see if there were any differences in the user or group ownership, but they look the same:
-rw-r--r-- 1 Tom Metro mkpasswd 0 Dec 10 13:29 test
-rw-r--r-- 1 Tom Metro mkpasswd 0 Dec 10 13:29 test2
However the same directory listing when viewed remotely appears as:
-rw-r--r-- 1 Tom Metro None 0 Dec 10 13:29 test
-rw-r--r-- 1 Tom Metro None 0 Dec 10 13:29 test2
So it appears group IDs are being mapped to names differently in the two scenarios. And a group name of "mkpasswd" seems suspicious (there is no group of that name in /etc/group).
My /etc/passwd entry:
Tom Metro::1003:513:Tom Metro,U-STARBUG\Tom Metro,:/home/Tom Metro:/bin/bash
Seems to say I should be a member of the group None:
and them I'm explicitly listed as a member of Users:
Maybe the space in the user name is fouling something up? (I tweaked the activate-user.sh script to permit spaces (I can send you the patch), as was discussed in another thread. It ran without errors.)