Re: setgid: Invalid argument

From: jay <libertysmith_at_**********.***>
Date: Mon Aug 11 2003 - 13:03:20 EDT

I have cygwin and openssh working, but I am still not connecting
vnc through the ssh tunnel.
For you take note of step 5, 6,and 7.
These steps have taken lots of time to put together.
Hope it may help you.
If you find anything new or need answers, let me know.
Try uninstalling your cygwin, install fresh, and try my steps.
You can also study and try the following the page below.

http://eudyptula.freezope.org/ms/Cygwin-SSH-VNC-HowTo.html

Tightvnc and openssh
          For tightvnc download
                    http://search.rpmseek.com/search.html
          For cygwin and openssh
                    http://sources.redhat.com/cygwin/

Windows 2000/xp setup
Steps:

1. Router setup and use virtual server, or port forwarding
    forward the computer ip of the server to port 5901 and 5801

2. Install Tightvnc-server
    execute vncserver on windows computer.
    right click on V icon in right of taskbar
    select properties
    select ports in display or port numbers to use
    use ports 5901 and 5801 from step 1
    Enter Password for client to login with
    right click the vncserver icon and select advance.
    Check the loop back enabled box.
   You now have a Tightvnc Server.

3. Install Tightvnc-viewer on the other computer (Client)
    Execute vncviewer in a konsole or find it in a menu.
    enter router wanip with :x which is the xdisplay number
    Example: 65.34.2.212:1
    To find your wanip logon to www.whatismyip.com
    For local use, use the server computer ip.
    To find your ip, In konsole type ifconfig
    In windows ipconfig or winipcfg
    Example: 192.144.3.133:1
    Enter password from step 2
   You should be doing remote control of the server.

Linux Suse setup
Steps:

1. Install Tightvnc-viewer for linux

2. Execute vncviewer in konsole

3. type in the windows server ip with the :1
    type in the password.
    or for internet logon, use the router wanip with :1
    Test it by taking control of the windows box.

4. Install Tightvnc-server for linux
    Execute "vncpasswd" and set a new password for clients
    Execute "vncserver :1"
    The :1 is for xdisplay 1
    You now have a vnc server in windows and linux
    Execute "vncserver -kill :1" to remove the server

5. If you want a secure shell, install openssh in linux.
    I use suse linux.
    In suse goto yast2, system, runlevel editor, runlevel properties.
    Make sure sshd is running.
    For windows find and install cygwin and openoffice for windows.
    They are free programs for windows.
    If you use a router you must forward the server's ip to port 22.
    ssh uses port 22.
    After installing cygwin make group and password according to the
    documentation to be able to login with ssh.

    With nt, 2000,and xp you will need to execute these as is.
    Example 3-5. Setting up the groups file for local accounts
    $ mkdir /etc
    $ mkgroup -l > /etc/group

    Example 3-6. Setting up the passwd file for local accounts
    $ mkdir /etc
    $ mkpasswd -l > /etc/passwd
    These commands will take windows user information and store them in
    a group and passwd file in the c:/cygwin/etc folder.
    Do not change the word /etc/group and /etc/passwd.

6. Now it is time to give it a try. In a terminal window on my own desktop,
    I entered vncviewer -via xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx:1
    where the xxx's represent server IP address in both instances.
    The -via option directs tightVNC to use ssh for a secure tunnel
    through which to operate.
    See man page for -via switch. Type in konsole "man vncviewer"
    Now you can vnc through an ssh tunnel
    which gives you some security.

7. If you change or add any useraccounts or a computer ip in windows,
    you must execute the mkgroup and mkpasswd again to update the files
    located in c:\cgwin\etc\group and c:\cygwin\etc\group
    Also in my suse linux when i had executed ssh I got a warning
    of intrusion.
    I had to delete /home/myuseraccount/.ssh/known_hosts file
    This is the file that has the key for security. If anything
    in the host system changes this key will alert me.
    Just delete it if you know that you are aware of changes to
    your system. Remember that .ssh is a hidden folder.
    In konqueror click on view and show hidden files.

help:
if ssh or vnc login fails look at server ip... use ipconf ifconf winipcf
If you get a localloop back disabled, in windows right click the
vncserver icon and select advance. Check the loop back enabled box.

For tightvnc download
    http://search.rpmseek.com/search.html
For cygwin and openssh
    http://www.redhat.com/software/cygwin/

http://www.realvnc.com/pipermail/vnc-list/2003-June/039500.html
http://www.realvnc.com/pipermail/vnc-list/2003-June/039521.html
http://linuxworld.sys-con.com/story/32625.htm

ports:
I found these inside of /home/useraccout/.vnc/vnc:1.log
     Listening for VNC connections on TCP port 5901
     Listening for HTTP connections on TCP port 5801
ssh port 22

vnc connection set ports 5901 for xdisplay :1 in router
execute "vncpasswd" to make the server password
vncviewer and enter wanip with :x which is the xdisplay number
enter password

good help for ssh and vnc
http://eudyptula.freezope.org/ms/Cygwin-SSH-VNC-HowTo.html
http://www.uk.research.att.com/vnc/intouch.html
http://www.realvnc.com/swish-e/search2/vnc-list?pos=0&action=search&query=local+loop-back+connections+are+disabled+&submit=search

commands:
vncpasswd -f command-line option
       providing passwords on stdin and writes
       encrypted passwords to stdout.
vncserver -kill :1
F8 menu
vncviewer's -tunnel option handling

ports:
I found these in /home/useraccout/.vnc/vnc:1.log
Listening for VNC connections on TCP port 5901
Listening for HTTP connections on TCP port 5801
ssh port 22
vnc port 23

On Wednesday 30 July 2003 01:43 pm, Trent J Nelson wrote:
> Hello,
>
> My name is Trent Nelson and I trying to attempt to get SSH running on a
> Win2k server. I have downloaded and installed Cygwin and included the
> OpenSSH packages during the install. I followed the sets located here:
>
> http://tech.erdelynet.com/cygwin-sshd.html
>
> I get the following error when I try to connect to the Windows box. I
> can ssh out to any of my other servers. Here is the error I get:
>
> bash-2.03$ ssh tnelson@sisyphus
> tnelson@sisyphus's password:
> Last login: Wed Jul 30 13:42:42 2003 from sisyphus.ibest.uidaho.edu
> setgid: Invalid argument
> Connection to sisyphus closed.
> bash-2.03$
>
> Any help would be greatly appreciated!!
>
> Thanks,
>
> Trent

--
List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
List Archives:    http://erdelynet.com/archive/ssh-l/
To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/ and enter your email address at the bottom to "Edit Options". If you don't know your password, have it emailed to you. Then unsubscribe.
Received on Mon Aug 11 21:51:53 2003

This archive was generated by hypermail 2.1.8 : Fri Jul 29 2005 - 17:33:57 EDT