Adam Van Antwerp on Tue, 15 Jan 2002 15:25:20 -0500 |
debug: Sending command: /home/oracle/ debug: Entering interactive session. debug: Sending eof. bash: /home/oracle/: is a directory ^^^^^^^that does not look correct -----Original Message----- From: plug-admin@lists.phillylinux.org [mailto:plug-admin@lists.phillylinux.org]On Behalf Of Samantha Samuel Sent: Tuesday, January 15, 2002 3:21 PM To: Philadelphia Linux User's Group Subject: Re: [PLUG] RemoteX > > I did that, I did get back my prompt. But x windows did'nt pop up. > > And yes, I do have x windows configured. > > But there were no errors spit to your terminal? No. > > I didn't find anything of relevance. > > Unfortunately, that may be true, but I'd like to see what's actually > in your logs for about five entries around the PAM messages relevant > to the ssh -f login. Jan 13 04:02:00 kira syslogd 1.4-0: restart. Jan 13 04:02:00 kira syslogd 1.4-0: restart. Jan 13 04:02:00 kira syslogd 1.4-0: restart. Jan 14 19:00:55 kira sshd(pam_unix)[20568]: session opened for user oracle by (uid=0) Jan 14 19:01:47 kira sshd(pam_unix)[20568]: session closed for user oracle Jan 14 19:08:40 kira sshd(pam_unix)[20630]: session opened for user oracle by (uid=0) Jan 14 19:16:49 kira su(pam_unix)[20692]: session opened for user root by oracle(uid=400) > If there's really nothing there, then start another sshd on the > server end (doesn't matter if you're not root) as > > sshd -d -d -d -p 2022 > /tmp/sshd.log 2>&1 debug1: Seeding random number generator debug1: sshd version OpenSSH_2.5.2p2 debug1: load_private_key_autodetect: type 0 RSA1 debug3: Bad RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read SSH2 private key done: name rsa w/o comment success 1 debug1: load_private_key_autodetect: type 1 RSA debug3: Bad RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read SSH2 private key done: name dsa w/o comment success 1 debug1: load_private_key_autodetect: type 2 DSA debug1: Bind to port 2022 on 0.0.0.0. Server listening on 0.0.0.0 port 2022. Generating 768 bit RSA key. RSA key generation complete. I didn't get my prompt back after this, and while I was doing a cat on the log, I noticed that no further changes seemed to be happening, so closed it. > Then, on the client end, do: > > ssh -v -v -v -f {host} {X command} 2> /tmp/ssh.log SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). debug: Reading configuration data /etc/ssh/ssh_config debug: Seeding random number generator debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to <host Name> [ip number] port 22. debug: Seeding random number generator debug: Allocated local port 958. debug: Connection established. debug: Remote protocol version 1.99, remote software version OpenSSH_2.5.2p2 debug: no match: OpenSSH_2.5.2p2 debug: Local version string SSH-1.5-OpenSSH_2.3.0p1 debug: Waiting for server public key. debug: Received server public key (768 bits) and host key (1024 bits). debug: Host '<host Name>' is known and matches the RSA host key. debug: Seeding random number generator debug: Encryption type: 3des debug: Sent encrypted session key. debug: Installing crc compensation attack detector. debug: Received encrypted confirmation. debug: Doing password authentication. debug: Sending command: /home/oracle/ debug: Entering interactive session. debug: Sending eof. bash: /home/oracle/: is a directory debug: Transferred: stdin 0, stdout 36, stderr 0 bytes in 0.1 seconds debug: Bytes per second: stdin 0.0, stdout 375.6, stderr 0.0 debug: Exit status 126 Also, on my router ports 22 is open. Not 6000. On my comp 22 and 6000, and on the remote host, I don't know yet. > One additional thought: do you have logs on the firewall? If so, are > they blocking packets that seem relevant? (Remember, X wants to > communicate in the 600n range.) If you're seeing nothing at all on > the firewall, then I'd start getting suspicious that your ISP is the > one blocking the X forwarding. is that 600 range or 6000? The win box belongs to my roomie. So I have to check with him. Thx -- Samantha ------- Real programmers do not comment their code. If it was hard to write, it should be hard to understand. ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|