radmin服务端保持连接不断问题分析与解决（Radmin server to maintain connectivity problems continue to analyze and solve）.docVIP

下载本文档

85
0
约6.26千字
约 13页
2017-09-27 发布于河南
举报
版权申诉

radmin服务端保持连接不断问题分析与解决（Radmin server to maintain connectivity problems continue to analyze and solve）.doc

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

radmin服务端保持连接不断问题分析与解决（Radmin server to maintain connectivity problems continue to analyze and solve）

radmin服务端保持连接不断问题分析与解决（Radmin server to maintain connectivity problems continue to analyze and solve） [original]Radmin server to maintain connectivity, problems analysis and resolution Article title: [constant problem analysis and solution on top of grassgrass released in the original]Radmin server: keep constant problem analysis and solution of 2006-07-1514:25 [[original landlord]Radmin server to keep Article author: grassgrass (kityest@163.com) Source: Evil octal information security team () 1. Problem description Radmin is an excellent remote control software, used to do the springboard back again good however, but every time even a springboard, inspect the springboard connection, can still see and connect our springboard to Radmin, but the display is TIME_WAIT, and this has been. Quote: ProtoLocalAddress ForeignAddress State TCP :135 :0 LISTENING TCP :445 :0 LISTENING TCP :1030 :0 LISTENING TCP :1031 :0 LISTENING TCP :139 :0 LISTENING TCP :139 :0 LISTENING TCP 20:1030 21:1034 TIME_WAIT UDP :445 *: * UDP :1026 *: * UDP :123 *: * UDP :1900 *: * UDP :123 *: * UDP :137 *: * UDP :138 *: * UDP :1900 *: * UDP :123 *: * UDP :137 *: * UDP :138 *: * UDP :1900 *: * UDP 20:123 *: * UDP 20:1900 *: * 2. Problem analysis The initial guess should be that the setsocketopt setting timeout has problems. Could it be an unlimited timeout? Debugging Radmin server, the next breakpoint in setsocketopt, the results are as follows: The first time it broke off Copycode 71A42E308BFF, MOVEDI, EDI 71A42E32 55, PUSHEBP 71A42E33, 8BEC, MOVEBP, ESP 71A42E35, 837D0C00, CMPDWORDPTRSS:[EBP+C], 0 71A42E39 0F8425010000 JEWSOCK32.71A42F64 71A42E3F, 8B4510, MOVEAX, DWORDPTRSS:[EBP+10] 71A42E42, 837D0C06, CMPDWORDPTRSS:[EBP+C], 6 71A42E46, 8B4D14, MOVECX, DWORDPTRSS:[EBP+14] 71A42E49 7475, JESHORTWSOCK32.71A42EC0 71A42E4B FF7518 PUSHDWORDPTRSS:[EBP+18] 71A42E4E 51, PUSHECX 71A42E4F 50, PUSHEAX 71A42E50 FF750C PUSHDWORDPTRSS:[EBP+C] 71A42E53 FF7508 PUSHDWORDPTRSS:[EBP+8] 71A42E56 E809000000 CALLJMP.WS2_