Hello,
Just setup the copssh on a windows 2003 server. Everything went wel during the install. After activating a user, I seem to login, because I see the last login date. Then at the same time I'm disconnected. Everytime, I see a quick error message like: setgid: Invalid argument
I've installed the application 3 times now and don't know what I actually doing wrong. Can someone help me please?
D.
Hello,
Just setup the copssh on a windows 2003 server. Everything went wel during the install. After activating a user, I seem to login, because I see the last login date. Then at the same time I'm disconnected. Everytime, I see a quick error message like: setgid: Invalid argument
I've installed the application 3 times now and don't know what I actually doing wrong. Can someone help me please?
D.
I try to login using the bash shell and this is de exact message i get:
daveo@localhost's password:
Last login: Fri Aug 26 15:59:37 2005 from host.domain.local
setgid: Invalid argument
Connection to localhost closed.
Thanks
What version of copssh do you use ? Is it an SP1 machine ?
Do you have a copy of installation log ?
What version of copssh do you use ? Is it an SP1 machine ?
Do you have a copy of installation log ?
Latest version...
I have this fixed (just 2 minutes ago) I changed numbers in the passwd file manually. Here is what it actually was and new:
Actually after a install:
ssh_user:unused_by_nt/2000/xp:11285:10513:ssh_remote,U-VISION\ssh_backup,S-1-5-21-1999127086-2052836264-159485872-1285:/home/ssh_backup:/bin/bash
After manually change:
ssh_user:unused_by_nt/2000/xp:11285:513:ssh_remote,U-VISION\ssh_backup,S-1-5-21-1999127086-2052836264-159485872-1285:/home/ssh_backup:/bin/bash
I've changed the xp:11285:10513 to xp:11285:513
I also noticed that only members of the domainadmins are permitted to login, even when you have granted this user for logging in to ssh server. (activate user)
I don't think that a good idea, unless it might be changeable to also allow domain users?
Best regards,
Dave
this would be caused if you only ran the mkpasswd and not the mkgroups command when you set it up. If the groups haven't been createdon the server side, the client connection will fail after authenticating successfully, with the error message setgid: Invalid argument
I had to do basically the same thing running version of COPSSH 1.3.8 on a Win 2000 Server with Domain. After adding a domain user via activate user, I had to modify the passwd file:
From:
user:unused_by_nt/2000/xp:11003:10512:alkat,U-DOMAIN\user,S-1-5-21-1659004503-1606980848-1708537768-1003:/home/user:/bin/bash
To:
user:unused_by_nt/2000/xp:11003:513:alkat,U-DOMAIN\user,S-1-5-21-1659004503-1606980848-1708537768-1003:/home/user:/bin/bash
Yep I had to do this, too.
Until now, I have been running the distribution from SSHWindows.SourceForge.Net with no need to change passwd manually. But I don't feel save since it has not been updated since July 2004...
(De)activation scripts might not work for domain users on localized windows machines, due to hard-coded 'Domain Users' in the scripts. Replace it with the localized name of the group 'Domain Users' in your environment.
Those scripts are known to work in English versions of Windows. I would like to know if this is not the case.