Re: scp times out
On Oct 23, 2009, at 12:59 PM, Josef Lowder wrote: $ scp filename j...@192.168.1.68:/home/joe/filecopy This will give you more info about what's going on... scp -v filename j...@192.168.1.68:/home/joe/filecopy ssh: connect to host 192.168.1.68 port 22: Connection timed out lost connection /sbin/ifconfig shows 192.168.1.68 as the inet address. What do I need to do to get scp to work? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss PGP.sig Description: This is a digitally signed message part --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
From: Alex Dean a...@crackpot.org On Oct 23, 2009, at 12:59 PM, Josef Lowder wrote: $ scp filename j...@192.168.1.68:/home/joe/filecopy ssh: connect to host 192.168.1.68 port 22: Connection timed out /sbin/ifconfig shows 192.168.1.68 as the inet address. This will give you more info about what's going on... scp -v filename j...@192.168.1.68:/home/joe/filecopy First thing I'd check is the iptables rulesets. An overly paranoid firewall could cause this to happen. Second thing I'd check is the /etc/ssh/sshd_config , to make sure that sshd is listening on that interface (or all interfaces) and port 22. pgrep sshd returns a PID, right? If it doesn't, there's your problem right there. -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
Alex Dean a...@crackpot.org wrote: $ scp filename j...@192.168.1.68:/home/joe/filecopy This will give you more info about what's going on: scp -v filename j...@192.168.1.68:/home/joe/filecopy So I tried that and got this error message: scp -v filename j...@192.168.1.68:/home/joe/filename Executing: program /usr/bin/ssh host 192.168.1.68, user joe, command scp -v -t /home/joe/filename OpenSSH_4.2p1, OpenSSL 0.9.7g 11 Apr 2005 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.68 [192.168.1.68] port 22: Connection timed out ssh: connect to host 192.168.1.68 port 22: Connection timed out lost connection = = = So I examined the ssh_config file and found mostly remarked lines and no clues that meant anything to me there. $ cat ssh_config #$OpenBSD: ssh_config,v 1.20 2005/01/28 09:45:53 dtucker Exp $ # This is the ssh client system-wide configuration file. See # ssh_config(5) for more information. This file provides defaults for # users, and the values can be changed in per-user configuration files # or on the command line. # Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. # Site-wide defaults for some commonly used options. For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page. # Host * # ForwardAgent no # ForwardX11 no # RhostsRSAAuthentication no # RSAAuthentication yes # PasswordAuthentication yes # HostbasedAuthentication no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/identity # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # Port 22 # Protocol 2,1 # Cipher 3des # Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc # EscapeChar ~ Host * ForwardX11 yes ForwardX11Trusted yes Protocol 2,1 StrictHostKeyChecking no --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
On Fri, Oct 23, 2009 at 12:20 PM, Matt Graham danceswithcr...@usa.netwrote: From: Alex Dean a...@crackpot.org On Oct 23, 2009, at 12:59 PM, Josef Lowder wrote: $ scp filename j...@192.168.1.68:/home/joe/filecopy ssh: connect to host 192.168.1.68 port 22: Connection timed out /sbin/ifconfig shows 192.168.1.68 as the inet address. This will give you more info about what's going on... scp -v filename j...@192.168.1.68:/home/joe/filecopy 0) Verify default route is in place: netstat -rn (UG should be gateway) 1) Ensure ssh is on on the target machine. 2) Verify ports are open: nmap $target (to ensure iptables are not limiting ssh access by source/destination or mac address, port knocking) 3) Verify MTU issues if you are in a remote connection or VPN. 4) Travel to the machine and verify it's turned on (laugh), ethernet up, ssh on! -- www.obnosis.com Skype: (623)239-3392 ATT: (503)754-4452 http://www.obnosis.com/motivatebytruth/teamwork1.jpg --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
Matt Graham wrote: First thing I'd check is the iptables rulesets. An overly paranoid firewall could cause this to happen. Second thing I'd check is the /etc/ssh/sshd_config , to make sure that sshd is listening on that interface (or all interfaces) and port 22. pgrep sshd returns a PID, right? If it doesn't, there's your problem right there. How does one check the iptables rulesets? How does one deetermine if sshd is listening? pgrep sshd gives no response. so what does that mean? and how can I fix that? This scp worked a year ago when I tried it and I've made no changes in this system since ... so what's next? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: scp times out
try telnet 192.168.1.68 22 if you get some prompts then the port is working, if not it's probably being blocked. check your firewall settings. _ From: plug-discuss-boun...@lists.plug.phoenix.az.us [mailto:plug-discuss-boun...@lists.plug.phoenix.az.us] On Behalf Of Lisa Kachold Sent: Friday, October 23, 2009 12:27 PM To: Main PLUG discussion list Subject: Re: scp times out On Fri, Oct 23, 2009 at 12:20 PM, Matt Graham danceswithcr...@usa.net wrote: From: Alex Dean a...@crackpot.org On Oct 23, 2009, at 12:59 PM, Josef Lowder wrote: $ scp filename j...@192.168.1.68:/home/joe/filecopy ssh: connect to host 192.168.1.68 port 22: Connection timed out /sbin/ifconfig shows 192.168.1.68 as the inet address. This will give you more info about what's going on... scp -v filename j...@192.168.1.68:/home/joe/filecopy 0) Verify default route is in place: netstat -rn (UG should be gateway) 1) Ensure ssh is on on the target machine. 2) Verify ports are open: nmap $target (to ensure iptables are not limiting ssh access by source/destination or mac address, port knocking) 3) Verify MTU issues if you are in a remote connection or VPN. 4) Travel to the machine and verify it's turned on (laugh), ethernet up, ssh on! -- www.obnosis.com Skype: (623)239-3392 ATT: (503)754-4452 http://www.obnosis.com/motivatebytruth/teamwork1.jpg --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
Lisa wrote: 0) Verify default route is in place: netstat -rn (UG should be gateway) 1) Ensure ssh is on on the target machine. 2) Verify ports are open: nmap $target (to ensure iptables are not limiting ssh access by source/destination or mac address, port knocking) 3) Verify MTU issues if you are in a remote connection or VPN. 4) Travel to the machine and verify it's turned on (laugh), ethernet up, ssh on. 0) netstat -rn (results): Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG0 0 0 eth0 1) target machine finds /etc/ssh (how do I determine if it is turned on?) 2) don't understand 'nmap $target' but tried the following with these results: nmap -v -sS -O 192.168.0.68 Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2009-10-23 12:40 MST Initiating SYN Stealth Scan against 192.168.0.68 [1663 ports] at 12:40 Discovered open port 631/tcp on 192.168.0.68 The SYN Stealth Scan took 0.15s to scan 1663 total ports. For OSScan assuming port 631 is open, 1 is closed, and neither are firewalled Host 192.168.0.68 appears to be up ... good. Interesting ports on 192.168.0.68: (The 1662 ports scanned but not shown below are in state: closed) PORTSTATE SERVICE 631/tcp open ipp MAC Address: 00:14:85:1E:5F:5E (Unknown) Device type: general purpose Running: Linux 2.4.X|2.5.X|2.6.X OS details: Linux 2.4.0 - 2.5.20, Linux 2.4.18 - 2.6.7 TCP Sequence Prediction: Class=random positive increments Difficulty=3597859 (Good luck!) IPID Sequence Generation: All zeros Nmap finished: 1 IP address (1 host up) scanned in 12.492 seconds Raw packets sent: 1679 (67.4KB) | Rcvd: 1677 (77.6KB) 3) Don't know how to Verify MTU issues if you are in a remote connection or VPN but I am not in a remote location. The two machines are side by side. 4) Travel to the machine and verify it's turned on (laugh), ethernet up, ssh on. Both machines are working, connected via ethernet, and both connect to Internet. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
From: Josef Lowder j...@actionline.com Matt Graham wrote: First thing I'd check is the iptables rulesets. How does one check the iptables rulesets? iptables -L . And then looking at the output for anything dumb. pgrep sshd returns a PID, right? If it doesn't, there's your problem right there. How does one deetermine if sshd is listening? netstat -a will tell you which processes are listening on which ports. pgrep sshd gives no response. so what does that mean? and how can I fix that? That means sshd is not running, and the solution is obvious: Restart sshd. This scp worked a year ago when I tried it and I've made no changes in this system since ... so what's next? No changes in a year? What? Don't you keep the system updated? -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
I last wrote (in part): This scp worked a year ago when I tried it and I've made no changes in this system since. Then Matt Graham wrote: No changes in a year? What? Don't you keep the system updated? That's correct. I have several computers, on some of which I do regular updates, but on my old reliable I never make changes (or updates) because it works more reliably than any of my other computers. I tried doing updates on it a couple of times and each time the updates royally messed everything up so bad that it took me weeks to get it back to working reliably again. So that is how I keep it, and it never fails. Can't say the same for the others. Change is not always good. In this case, I've finally figured out that the scp problem is apparently related to the fact that I changed modem/routers and the new Motorola router (from Qwest) has apparently created the current problem. Today, I found that I had to enable passthrough in order to be able to pass files between computers on my network, but in doing that, the inet address got messed up and now I can't get that reset to the correct inet address. I've searched the 'net and tried everything I could find to try. One time I did get it working, but then (apparently) the router messed it up again. I've tried: # dhclient -r # dhclient # ifdown eth0 # ifup eth0 # /etc/init.d/network restart ... and a bunch of other things. After many repeated attempts, at one point, ifconfig showed the correct inet address and I was able to connect ... but then it self-disconnected somehow and I've not been able to get it restored. This is just another reason why, once I get a computer system to work correctly, I dread changing things. If it ain't broke, don't fix it. Once you get it fixed, don't mess with it. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
On Fri, 2009-10-23 at 17:12 -0500, Josef Lowder wrote: I last wrote (in part): This scp worked a year ago when I tried it and I've made no changes in this system since. Then Matt Graham wrote: No changes in a year? What? Don't you keep the system updated? That's correct. I have several computers, on some of which I do regular updates, but on my old reliable I never make changes (or updates) because it works more reliably than any of my other computers. I tried doing updates on it a couple of times and each time the updates royally messed everything up so bad that it took me weeks to get it back to working reliably again. So that is how I keep it, and it never fails. Can't say the same for the others. Change is not always good. In this case, I've finally figured out that the scp problem is apparently related to the fact that I changed modem/routers and the new Motorola router (from Qwest) has apparently created the current problem. Today, I found that I had to enable passthrough in order to be able to pass files between computers on my network, but in doing that, the inet address got messed up and now I can't get that reset to the correct inet address. I've searched the 'net and tried everything I could find to try. One time I did get it working, but then (apparently) the router messed it up again. I've tried: # dhclient -r # dhclient # ifdown eth0 # ifup eth0 # /etc/init.d/network restart ... and a bunch of other things. After many repeated attempts, at one point, ifconfig showed the correct inet address and I was able to connect ... but then it self-disconnected somehow and I've not been able to get it restored. This is just another reason why, once I get a computer system to work correctly, I dread changing things. If it ain't broke, don't fix it. Once you get it fixed, don't mess with it. I can't quite figure out if this is an indictment on all Linux in general or the specific distribution that he uses but this is pathetic. If the distribution you choose to use breaks because you update, you need to find a different one...period, end of discussion. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: scp times out
netstat -anp |grep 22 (get anything?) ps -e |grep ssh /etc/init.d/sshd start or /etc/init.d/ssh start nmap localhost (watch for port 22) On Fri, Oct 23, 2009 at 3:48 PM, Craig White craigwh...@azapple.com wrote: On Fri, 2009-10-23 at 17:12 -0500, Josef Lowder wrote: I last wrote (in part): This scp worked a year ago when I tried it and I've made no changes in this system since. Then Matt Graham wrote: No changes in a year? What? Don't you keep the system updated? That's correct. I have several computers, on some of which I do regular updates, but on my old reliable I never make changes (or updates) because it works more reliably than any of my other computers. I tried doing updates on it a couple of times and each time the updates royally messed everything up so bad that it took me weeks to get it back to working reliably again. So that is how I keep it, and it never fails. Can't say the same for the others. Change is not always good. In this case, I've finally figured out that the scp problem is apparently related to the fact that I changed modem/routers and the new Motorola router (from Qwest) has apparently created the current problem. Today, I found that I had to enable passthrough in order to be able to pass files between computers on my network, but in doing that, the inet address got messed up and now I can't get that reset to the correct inet address. I've searched the 'net and tried everything I could find to try. One time I did get it working, but then (apparently) the router messed it up again. I've tried: # dhclient -r # dhclient # ifdown eth0 # ifup eth0 # /etc/init.d/network restart ... and a bunch of other things. After many repeated attempts, at one point, ifconfig showed the correct inet address and I was able to connect ... but then it self-disconnected somehow and I've not been able to get it restored. This is just another reason why, once I get a computer system to work correctly, I dread changing things. If it ain't broke, don't fix it. Once you get it fixed, don't mess with it. I can't quite figure out if this is an indictment on all Linux in general or the specific distribution that he uses but this is pathetic. If the distribution you choose to use breaks because you update, you need to find a different one...period, end of discussion. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- Skype: (623)239-3392 ATT: (503)754-4452 www.obnosis.com http://www.obnosis.com/motivatebytruth/will_work_4_bandwidth.jpg --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
