On Sun, 2010-10-03 at 19:25 -0400, Jim wrote:
> On 10/03/2010 02:31 PM, JD wrote:
> >
> > On 10/03/2010 08:15 AM, Jim wrote:
> >> From the Client to Server ssh geo...@61.243.171.16 and the Client
> >> timed
> >> out and nothing has shown up on Server debug.
> >>
> >> I can ssh to any of my la
On 10/03/2010 04:25 PM, Jim wrote:
>On 10/03/2010 02:31 PM, JD wrote:
>> On 10/03/2010 08:15 AM, Jim wrote:
>>>From the Client to Server ssh geo...@61.243.171.16 and the Client
>>> timed
>>> out and nothing has shown up on Server debug.
>>>
>>> I can ssh to any of my laptops on my loc
On 10/03/2010 02:31 PM, JD wrote:
>
> On 10/03/2010 08:15 AM, Jim wrote:
>> From the Client to Server ssh geo...@61.243.171.16 and the Client timed
>> out and nothing has shown up on Server debug.
>>
>> I can ssh to any of my laptops on my local lan but not across the internet.
>>
>> if I kn
On 10/03/2010 11:49 AM, James McKenzie wrote:
>
> Good idea. Also check the contents of hosts.allow/hosts.deny. One
> further thing is to check if the IP address is being changed (NAT)
> in-between the two systems. That can cause more troubles...
>
> James McKenzie
If NAT, then the the sshd
On 10/3/10 11:43 AM, JD wrote:
>
> On 10/03/2010 09:09 AM, Jim wrote:
>> On 10/02/2010 08:28 PM, JD wrote:
>>> On 10/02/2010 02:42 PM, Jim wrote:
What is the 6749 in this command ?
# netstat -nltp | grep 22
tcp0 0 0.0.0.0:22
0.0.0.0:*
On 10/03/2010 09:09 AM, Jim wrote:
>On 10/02/2010 08:28 PM, JD wrote:
>> On 10/02/2010 02:42 PM, Jim wrote:
>>> What is the 6749 in this command ?
>>>
>>>
>>> # netstat -nltp | grep 22
>>> tcp0 0 0.0.0.0:22
>>> 0.0.0.0:* LISTEN 6749/sshd
>>> tcp
On 10/03/2010 08:15 AM, Jim wrote:
>From the Client to Server ssh geo...@61.243.171.16 and the Client timed
> out and nothing has shown up on Server debug.
>
> I can ssh to any of my laptops on my local lan but not across the internet.
>
> if I knew that when I went from FC12 to 13 I would ha
On 10/02/2010 08:28 PM, JD wrote:
>
> On 10/02/2010 02:42 PM, Jim wrote:
>> What is the 6749 in this command ?
>>
>>
>> # netstat -nltp | grep 22
>> tcp0 0 0.0.0.0:22
>> 0.0.0.0:* LISTEN 6749/sshd
>> tcp0 0 0.0.0.0:8822
>> 0.0.0.0:*
On 10/02/2010 08:38 PM, JD wrote:
>
> On 10/02/2010 04:35 PM, Jim wrote:
>> On 10/02/2010 07:05 PM, JD wrote:
>>> On 10/02/2010 12:14 PM, Jim wrote:
On 10/02/2010 02:52 PM, JD wrote:
> On 10/02/2010 11:43 AM, Jim wrote:
>> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0
On 10/03/2010 10:16 AM, Aaron Konstam wrote:
>>
>> sometimes you may have changed the default port for ssh service. Check
>> whether the port is 22.
>> Check /etc/ssh/ssh_config in servers
> Or check that that address is reachable from your machine using host or
> dig.
Is it possible that machi
On Sat, 2010-10-02 at 22:10 +0530, Kalpa Welivitigoda wrote:
> On Sat, Oct 2, 2010 at 10:02 PM, Jim wrote:
> > Wether I run NX (nomachine) or SSH I get the same error message, no
> > matter what host I try to connect to.
> >
> > And on the host servers SSHd is running.
> > And so is the Client bo
Jim wrote:
> On 10/02/2010 04:44 PM, Jim wrote:
>> # ifconfig -a
>> eth0 Link encap:Ethernet HWaddr 00:1D:72:A5:DD:B5
>> inet addr:69.243.171.15 Bcast:69.243.175.255 Mask:255.255.248.0
>> inet6 addr: fe80::21d:72ff:fea5:ddb5/64 Scope:Link
>> UP BROADCAS
On 10/02/2010 04:35 PM, Jim wrote:
>On 10/02/2010 07:05 PM, JD wrote:
>> On 10/02/2010 12:14 PM, Jim wrote:
>>> On 10/02/2010 02:52 PM, JD wrote:
On 10/02/2010 11:43 AM, Jim wrote:
> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW
> tcp dpt:22
OK
On 10/02/2010 02:42 PM, Jim wrote:
>What is the 6749 in this command ?
>
>
> # netstat -nltp | grep 22
> tcp0 0 0.0.0.0:22
> 0.0.0.0:* LISTEN 6749/sshd
> tcp0 0 0.0.0.0:8822
> 0.0.0.0:* LISTEN 1666/smfpd
> tcp0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2010 11:32 AM, Jim wrote:
> Wether I run NX (nomachine) or SSH I get the same error message, no
> matter what host I try to connect to.
>
> And on the host servers SSHd is running.
> And so is the Client box.
>
> Running NX
> Error messa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim wrote:
> On 10/02/2010 07:05 PM, JD wrote:
>> On 10/02/2010 12:14 PM, Jim wrote:
>>> On 10/02/2010 02:52 PM, JD wrote:
On 10/02/2010 11:43 AM, Jim wrote:
> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW
>
On 10/02/2010 07:05 PM, JD wrote:
>
> On 10/02/2010 12:14 PM, Jim wrote:
>> On 10/02/2010 02:52 PM, JD wrote:
>>> On 10/02/2010 11:43 AM, Jim wrote:
ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
dpt:22
>>> OK, So port 22 is open.
>>> Is this on the serv
On 10/02/2010 12:21 PM, Jim wrote:
>On 10/02/2010 02:52 PM, JD wrote:
>> On 10/02/2010 11:43 AM, Jim wrote:
>>> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
>>> dpt:22
>> OK, So port 22 is open.
>> Is this on the server where sshd is running or is this
>> on the
On 10/02/2010 12:14 PM, Jim wrote:
>On 10/02/2010 02:52 PM, JD wrote:
>> On 10/02/2010 11:43 AM, Jim wrote:
>>> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
>>> dpt:22
>> OK, So port 22 is open.
>> Is this on the server where sshd is running or is this
>> on the
On 10/02/2010 06:19 PM, Craig White wrote:
> On Sat, 2010-10-02 at 17:42 -0400, Jim wrote:
>> What is the 6749 in this command ?
>>
>>
>> # netstat -nltp | grep 22
>> tcp0 0 0.0.0.0:22
>> 0.0.0.0:* LISTEN 6749/sshd
>> tcp0 0 0.0.0.0:8822
>> 0.0.0.0
On Sat, 2010-10-02 at 17:42 -0400, Jim wrote:
> What is the 6749 in this command ?
>
>
> # netstat -nltp | grep 22
> tcp0 0 0.0.0.0:22
> 0.0.0.0:* LISTEN 6749/sshd
> tcp0 0 0.0.0.0:8822
> 0.0.0.0:*
What is the 6749 in this command ?
# netstat -nltp | grep 22
tcp0 0 0.0.0.0:22
0.0.0.0:* LISTEN 6749/sshd
tcp0 0 0.0.0.0:8822
0.0.0.0:* LISTEN 1666/smfpd
tcp0 0 :::22
On 10/02/2010 04:44 PM, Jim wrote:
>On 10/02/2010 04:02 PM, Roberto Ragusa wrote:
>> Jim wrote:
>>> On 10/02/2010 01:11 PM, Roberto Ragusa wrote:
Jim wrote:
> On 10/02/2010 12:32 PM, Jim wrote:
>> Wether I run NX (nomachine) or SSH I get the same error message, no
On 10/02/2010 04:02 PM, Roberto Ragusa wrote:
> Jim wrote:
>>On 10/02/2010 01:11 PM, Roberto Ragusa wrote:
>>> Jim wrote:
On 10/02/2010 12:32 PM, Jim wrote:
> Wether I run NX (nomachine) or SSH I get the same error message, no
> matter what host I try to connect to.
Jim wrote:
> On 10/02/2010 01:11 PM, Roberto Ragusa wrote:
>> Jim wrote:
>>>On 10/02/2010 12:32 PM, Jim wrote:
Wether I run NX (nomachine) or SSH I get the same error message, no
matter what host I try to connect to.
And on the host servers SSHd is running.
And so
On 10/02/2010 02:52 PM, JD wrote:
>
> On 10/02/2010 11:43 AM, Jim wrote:
>> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
>> dpt:22
> OK, So port 22 is open.
> Is this on the server where sshd is running or is this
> on the client where you are invoking /usr/bin/ssh
On 10/02/2010 02:52 PM, JD wrote:
>
> On 10/02/2010 11:43 AM, Jim wrote:
>> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
>> dpt:22
> OK, So port 22 is open.
> Is this on the server where sshd is running or is this
> on the client where you are invoking /usr/bin/ssh
On Sat, 02 Oct 2010 13:53:32 -0400
Jim wrote:
> What is the -n -n After eth0 mean ?
man tcpdump
-n Don’t convert host addresses to names. This can be used to
avoid DNS lookups.
-nnDon’t convert protocol and port numbers etc. to names either.
--
users mailing list
users@lists.fedo
On 10/02/2010 11:43 AM, Jim wrote:
> ACCEPT tcp -- 0.0.0.0/00.0.0.0/0 state NEW tcp
> dpt:22
OK, So port 22 is open.
Is this on the server where sshd is running or is this
on the client where you are invoking /usr/bin/ssh ??
If on the server, then take a look at the
On 10/02/2010 02:34 PM, JD wrote:
> sudo iptables -L -n
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[r...@acer mickey]# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- 0.0.0.0/00
On 10/02/2010 12:40 PM, Kalpa Welivitigoda wrote:
> On Sat, Oct 2, 2010 at 10:02 PM, Jim wrote:
>> Wether I run NX (nomachine) or SSH I get the same error message, no
>> matter what host I try to connect to.
>>
>> And on the host servers SSHd is running.
>> And so is the Client box.
>>
>> Runn
On 10/02/2010 11:28 AM, Jim wrote:
>On 10/02/2010 02:09 PM, JD wrote:
>> On 10/02/2010 09:32 AM, Jim wrote:
>>> Wether I run NX (nomachine) or SSH I get the same error message, no
>>> matter what host I try to connect to.
>>>
>>> And on the host servers SSHd is running.
>>> And so is the
On 10/02/2010 02:09 PM, JD wrote:
>
> On 10/02/2010 09:32 AM, Jim wrote:
>> Wether I run NX (nomachine) or SSH I get the same error message, no
>> matter what host I try to connect to.
>>
>> And on the host servers SSHd is running.
>> And so is the Client box.
>>
>> Running NX
>> Error messa
-
From: users-boun...@lists.fedoraproject.org
[mailto:users-boun...@lists.fedoraproject.org] On Behalf Of JD
Sent: Saturday, October 02, 2010 2:09 PM
To: Community support for Fedora users
Subject: Re: SSH can't connect
On 10/02/2010 09:32 AM, Jim wrote:
>Wether I run NX (nomac
On 10/02/2010 09:32 AM, Jim wrote:
>Wether I run NX (nomachine) or SSH I get the same error message, no
> matter what host I try to connect to.
>
> And on the host servers SSHd is running.
> And so is the Client box.
>
> Running NX
> Error message: ssh: connect to host 70.236.39.98 port 22
On 10/02/2010 01:11 PM, Roberto Ragusa wrote:
> Jim wrote:
>>On 10/02/2010 12:32 PM, Jim wrote:
>>> Wether I run NX (nomachine) or SSH I get the same error message, no
>>> matter what host I try to connect to.
>>>
>>> And on the host servers SSHd is running.
>>> And so is the Client box.
On 10/02/2010 01:11 PM, Roberto Ragusa wrote:
> Jim wrote:
>>On 10/02/2010 12:32 PM, Jim wrote:
>>> Wether I run NX (nomachine) or SSH I get the same error message, no
>>> matter what host I try to connect to.
>>>
>>> And on the host servers SSHd is running.
>>> And so is the Client box.
Jim wrote:
> On 10/02/2010 12:32 PM, Jim wrote:
>>Wether I run NX (nomachine) or SSH I get the same error message, no
>> matter what host I try to connect to.
>>
>> And on the host servers SSHd is running.
>> And so is the Client box.
>>
>> Running NX
>> Error message: ssh: connect to host
On 10/02/2010 12:32 PM, Jim wrote:
>Wether I run NX (nomachine) or SSH I get the same error message, no
> matter what host I try to connect to.
>
> And on the host servers SSHd is running.
> And so is the Client box.
>
> Running NX
> Error message: ssh: connect to host 70.236.39.98 port 22
On Sat, Oct 2, 2010 at 10:02 PM, Jim wrote:
> Wether I run NX (nomachine) or SSH I get the same error message, no
> matter what host I try to connect to.
>
> And on the host servers SSHd is running.
> And so is the Client box.
>
> Running NX
> Error message: ssh: connect to host 70.236.39.98 p
40 matches
Mail list logo