免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 11609 | 回复: 5
打印 上一主题 下一主题

putty :Software caused connection abort [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2007-03-26 11:23 |只看该作者 |倒序浏览
我的freebsd托管出去

PUTTY连上一会后,出现。Software caused connection abort,就断掉了,然后再次连还能连上
有谁碰到类似的问题吗?
这个是我freebsd的问题,还是托管商的问题

论坛徽章:
1
技术图书徽章
日期:2013-12-05 23:25:45
2 [报告]
发表于 2007-03-26 11:41 |只看该作者
网络品质不好可能会出现这样子的问题。

论坛徽章:
0
3 [报告]
发表于 2007-04-04 10:38 |只看该作者

我也一样!

现在非常郁闷中

论坛徽章:
0
4 [报告]
发表于 2007-10-18 10:16 |只看该作者
Error Message:

Software caused connection abort.

Explanation:

This error can occur when the local network system aborts a connection, such as when Winsock closes an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).

User Action:

Check the following: 1. Ping the remote host you were connected to. If it doesn't respond, it might be offline or there might be a network problem along the way. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again). 2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step). 3. Ping your local router address. If you are on a serial connection, your local router is the IP address of the host you initially logged on to using SLIP or PPP. 4. Ping a host on the same subnet as the host you were connected to (if you know of one). This will verify that the destination network is functioning. 5. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.

我今天也遇到了,呵呵,还在找解决办法...

论坛徽章:
0
5 [报告]
发表于 2007-10-18 10:21 |只看该作者
可以考虑把timeout设大一点,
A.7.11 PuTTY's network connections time out too quickly when network connectivity is temporarily lost.

This is a Windows problem, not a PuTTY problem. The timeout value can't be set on per application or per session basis. To increase the TCP timeout globally, you need to tinker with the Registry.

On Windows 95, 98 or ME, the registry key you need to create or change is
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\
  MSTCP\MaxDataRetries

(it must be of type DWORD in Win95, or String in Win98/ME). (See MS Knowledge Base article 158474 for more information.)

On Windows NT, 2000, or XP, the registry key to create or change is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
  Parameters\TcpMaxDataRetransmissions

and it must be of type DWORD. (See MS Knowledge Base articles 120642 and 314053 for more information.)

Set the key's value to something like 10. This will cause Windows to try harder to keep connections alive instead of abandoning them.

论坛徽章:
0
6 [报告]
发表于 2010-06-16 20:30 |只看该作者
可以考虑把timeout设大一点,
A.7.11 PuTTY's network connections time out too quickly when network co ...
carrison 发表于 2007-10-18 10:21


好的.
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP