Re: ssh from 012 cable to server in US fail

2009-04-30 Thread Rami Addady
Thanks for all the replays, Now after 3 day it suddenly stat  to work.  I didn't done any change in both sides. My guess is that 012 block port 22 abroad, because of some ssh worm that attract from local PC's and consume bandwidths etc. Rami shimi wrote: On Tue, Apr 28, 2009 at 1

Re: ssh from 012 cable to server in US fail

2009-04-30 Thread shimi
On Tue, Apr 28, 2009 at 11:10 AM, Rami Addady wrote: > Hi, > > > I have weird problem , staring this morning I can't ssh to a server in US, > from some computers that connect to the Internet using 012 cabels. > > But if I'm ssh to server in 012 farm and then from it to the US server is > work fi

Re: ssh from 012 cable to server in US fail

2009-04-29 Thread Baruch Siach
Hi Geoffrey, On Thu, Apr 30, 2009 at 07:31:43AM +0300, Geoffrey Mendelson wrote: > BTW, does anyone know whom the new Minister of Telecommunications is? > The English press reported that there was one, but never mentioned who > it was. According to the page at http://www.moc.gov.il/137-en/MOC.asp

Re: ssh from 012 cable to server in US fail

2009-04-29 Thread Geoffrey Mendelson
2009/4/29 ronys : > FWIW, Netvision, although they've started blocking outgoing SMTP (port 25), > still allow SSH with no problems, both locally and to the US. > > I doubt that it's a Big Brother type of issue (yet). Who was it that said > not to attribute to malice that which can be attributed to

Re: ssh from 012 cable to server in US fail

2009-04-29 Thread Imri Zvik
On Tuesday 28 April 2009 13:57:36 Ira Abramov wrote: > these all sound annoyingly like the "adventures" a friend of mine had > when connecting to my server from china, including obvious > man-in-the-middle attacks, such as each time hׁ” tried to connect, the > "server" would display a different hos

Re: ssh from 012 cable to server in US fail

2009-04-29 Thread Imri Zvik
Hi, We are not aware of such problem, and if such one exists, it is not intentional. Please provide me with some more information off-list (IP addresses, capture files of connection attempts if possible etc.), and we will check into it. --imriz ___

RE: ssh from 012 cable to server in US fail

2009-04-29 Thread ronys
ag Sameach, Rony -Original Message- From: linux-il-boun...@cs.huji.ac.il [mailto:linux-il-boun...@cs.huji.ac.il] On Behalf Of Ira Abramov Sent: Tuesday, April 28, 2009 1:58 PM To: linux-il@cs.huji.ac.il Subject: Re: ssh from 012 cable to server in US fail Quoting Tomer Cohen, from the p

Re: ssh from 012 cable to server in US fail

2009-04-29 Thread Rami Addady
Hi, Can't change port number.  Some user connect this server from post 22. Rami Tzafrir Cohen wrote: On Tue, Apr 28, 2009 at 11:10:30AM +0300, Rami Addady wrote: Hi, I have weird problem , staring this morning I can't ssh to a server in US, from some computers that

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Tzafrir Cohen
On Tue, Apr 28, 2009 at 11:10:30AM +0300, Rami Addady wrote: > Hi, > > > I have weird problem , staring this morning I can't ssh to a server in > US, from some computers that connect to the Internet using 012 cabels. > > But if I'm ssh to server in 012 farm and then from it to the US server >

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Shay Ohayon
Hello folks, I am also connected through 012 Cables (HOT) and am unable to connect (ssh) to servers in The Netherlands and US. Also tried talking to tech support and they didn't even had a clue. Please update if any of you got a solution (or any support from any of the companies). For the record

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Ira Abramov
Quoting Tomer Cohen, from the post of Tue, 28 Apr: > Hi, > > I had the same issue yesterday evening (012, cable). After few hours I > periodically tried, I was able to access the machines (one is located in > Dreamhost, the other at sourceforge.net), but very slowly and with sudden > disconnection

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread sara fink
Please follow these steps: 1. I will highly suggest to launch wireshark when you try to ssh. If you see a RST, I won't be surprised at all. You may see a RST that comes from your ip. Don't be surprised. 2. You must understand the following thing: they have clients rank A and clients rank D. fro

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Tomer Cohen
Hi, I had the same issue yesterday evening (012, cable). After few hours I periodically tried, I was able to access the machines (one is located in Dreamhost, the other at sourceforge.net), but very slowly and with sudden disconnections after about one minute of each connection. On Tue, Apr 28,

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Rami Addady
Hi, Can you provide the server logs? (The connected site) There are no new entry in /var/log/secure ou can also try and run it with '-v' to add verbosity there too. The -v output can be found in my first post Thank, Rami Noam Meltzer wrote: Can you provide the server logs? (The

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Noam Meltzer
Can you provide the server logs? (The connected site) It can easily shed light on the subject. On RHEL the log file in interest is /var/log/secure. - Noam On Tue, Apr 28, 2009 at 11:10 AM, Rami Addady wrote: > Hi, > > > I have weird problem , staring this morning I can't ssh to a server in US,

Re: ssh from 012 cable to server in US fail

2009-04-28 Thread Yedidyah Bar-David
On Tue, Apr 28, 2009 at 11:10:30AM +0300, Rami Addady wrote: > Hi, > > > I have weird problem , staring this morning I can't ssh to a server in > US, from some computers that connect to the Internet using 012 cabels. > > But if I'm ssh to server in 012 farm and then from it to the US server >

ssh from 012 cable to server in US fail

2009-04-28 Thread Rami Addady
Hi, I have weird problem , staring this morning I can't ssh to a server in US, from some computers that connect to the Internet using 012 cabels. But if I'm ssh to server in 012 farm and then from it to the US server is work fine! I called 012 technical support but they didn't help me.