Some more information:
Since apache works perfectly, I stopped it and tried moving telnet to port
80. Still no connection. ssh didn't work over port 80, either, so I know
it's not a firewall problem.
After scouring the net, I read that sometimes having ipv6 enabled in the
kernel will confuse ssh, so I tried running sshd -4 to bind only to ipv4
addresses... still nothing.
Are there any other reasons two basically identical boxes won't ssh to each
other?
Again, I very much appreciate any suggestions.
-Owen
At 21:28 2001-07-09 -0700, Owen G. Emry wrote:
I just set up a new machine and for some infernal reason I can't ssh or
telnet to it. Here are the details:
-- both machines have static IPs, proper DNS entries, and are up to date
with latest Debian potato ssh and telnetd
-- new-machine is a fresh vanilla install, running the stock 3.19pre17 kernel
-- new-machine has two 3c509b cards, a configuration I've used forever
with no problems
-- i've tried it with one card just to make things simpler and it doesn't
change anything
-- telnetting from working-machine to new-machine I get "Connected, escape
character is <blah blah blah>" and then a several-second pause, and the
remote drops the connection
-- yes, I've uncommented the telnet line from /etc/inetd.conf (it's
connecting, and then the remote drops the connection)
-- when sshing from working-maching to new-machine it prints "exchanging
<something>" and the remote drops the session
-- ALL OTHER SERVICES WORK FINE (e.g. apache, ftp daemons, etc) but ssh
and telnet just don't want to talk to me
-- I tried running sshd -d (debug mode) on new-machine, but when I try to
ssh in, it says "cannot fork in debug mode" so I'm not getting any real
useful info.
Thanks _very much_ in advance. (I've been banging my head for 2 days on
this one.)
-Owen G. Emry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a
subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
