Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Putty Problem to One Linux Server
March 15, 2010, 4:46 am
rate this thread
and I have been using it for years. I have three computers. On one
the OS is Windows XP Pro with Putty. The other two are servers running
Slackware with OpenSSH_5.3p1, OpenSSL 0.9.8l 5 Nov 2009
If I connect to server A from the XP desktop using Putty, I obtain a
connection that is rock solid and it will stay up for hours until I
manually disconnect. If I connect to server B using the same desktop
computer and Putty, it disconnects after about 5 minutes with the error
message "Network error: Software caused connection abort". If I try to
connect again right after it disconnects, I receive a "Network error:
Connection Refused" message. If I wait a bit, I am however able to
establish a new connection with no error message. It is also
interesting to note that if I have two Putty sessions running from XP to
server B, they both die at the same time and continuous 1 second pings
from server A to server B never miss a beat.
Lastly, when the connection dies between Putty and server B, if I also
have a Putty session running to server A it is not affected. And if I
have an ssh connection between server A and server B that is initiated
from a command line, it also is not affected. Simultaneous connections
between server A and server B are rock solid, connections between Putty
and server A are rock solid, but connections between Putty and server B
cannot be maintained.
The only difference I can think of between the two server setups is that
server B is the only one with a 100 MB connection. The other two are 1
GB connections with a single switch (HP-J9029A) in between all of them.
Most of what I have read indicates the "Software caused a connection
abort" is the result of a Windows network problem but with the Server
A connection being so solid, I am at a loss as to why it works in one
case but not the other. Any suggestions? Thanks.
Re: Putty Problem to One Linux Server
I thought I would post this in case someone else ever had a similar
headache since I found the problem - pilot error. In other words, I was
an idiot. After much gnashing of the teeth, I found another device on
the network with the same static IP address I used for server B. I had
installed the device months ago and forgotten about it. I guess that
says something about the need for good record keeping.
- » password-based authentication only from internal network
- — Next thread in » Secure Shell Forum
- » scp:Scp2/scp2.c:667: Received error SSH_FC_OK, error message
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum