Re: [cobalt-users] Please SPECULATE - Telnet and SSH connections timeout.

[Carrie Bartkowiak <ravencarrie@xxxxxxxx>]

On Thu, 9 Aug 2001 11:32:28 -0400, Glenn Parsons mumbled something 
like:
>>Please, SPECULATE!

1. You have a DNS entry (or more) set up incorrectly
2. The internal router that is forwarding requests is not forwarding 
to the new improved "moved" port
3. The programs that you are using aren't configured for the new 
improved "moved" port
4. You haven't configured IPChains or Portsentry to allow connections 
to the new improved "moved" port, or
5. You haven't told IPChains or Portsentry that you've got SSH 
running on whatever port it's on
6. You're using the wrong protocol to connect (ie: 1 instead of 2) in 
your program
7. Try using the IP to connect rather than the FQDN (this is a 
suggestion, not a speculation)
8. You don't have the server's keys cached in your program (the first 
time Putty connects it asks if you want to cache the keys - perhaps 
someone clicked 'no')
9. You've done something else somewhere that has triggered IPChains 
or Portsentry to toss you into the routing table or block you; 
something that is totally unrelated to connecting with a shell. Check 
the routing table, hosts.deny, and IPChains current rules
10. You need to try a different program? If you're using SecureCRT, 
for example, try Putty. Or vice-versa (I think SecureCRT has a demo 
trial available, not sure).

These all might lead nowhere, but at least it's some sort of answer. 
;)

--
CarrieB
"The computer can't tell you the emotional story.  It can give you 
the exact mathematical design, but what's missing is the eyebrows." 
--Frank Zappa