SCIENTIFIC-LINUX-USERS Archives

December 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bluejay Adametz <[log in to unmask]>
Reply To:
Bluejay Adametz <[log in to unmask]>
Date:
Tue, 27 Dec 2011 12:13:28 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
>> When it fails, does it fail immediately, or does it take a few seconds
>> before the error shows up?
>>
>> If it fails immediately, it could be a router or firewall blocking
>> something or maybe iptables.
>
> It fails immediately, and soon the error message is gone in the next try.
> That is happened sometimes, say once in seven times ssh.  I don't think
> firewall could work that way.  Am I right?

Yes, I would expect a firewall to either deny (possibly generating the
'no route' error by explicitly denying the connect), or allow it,
every time.

Are there any routers involved, or are both the home and office
machines on the same LAN, in the configuration where you see the
failures?

                                                         - Bluejay Adametz

If you don't climb out on the limb, you may never get the fruit.
NOTICE: This message, including any attachments, is only for the use of 
the intended recipient(s) and may contain confidential and privileged 
information, or information otherwise protected from disclosure by law.  
If the reader of this message is not the intended recipient, you are 
hereby notified that any use, disclosure, copying, dissemination or 
distribution of this message or any of its attachments is strictly 
prohibited.  If you received this message in error, please contact the 
sender immediately by reply email and destroy this message, including all 
attachments, and any copies thereof. 



ATOM RSS1 RSS2