Web服务器是带有IIS 6的Windows Server 2003.Web服务是运行在.NET 4.0中的ASMX。
当以名为“ALBERT”的域用户的身份调用Web服务时,一切正常。
POST http://elvis.ecq.local/sems/Services/DecVotingService.asmx HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.225) Content-Type: text/xml; charset=utf-8 SOAPAction: "http://tempuri.org/GetEventDivisions" Host: elvis.ecq.local Content-Length: 449 Expect: 100-continue Connection: Keep-Alive <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><GetEventDivisions xmlns="http://tempuri.org/"><eventID>165</eventID><isGroupEvent>false</isGroupEvent><roUserName>ALBERT</roUserName><CHKSUM>3dcdaea4f9dbcaac689a4ce19c0fcd97</CHKSUM></GetEventDivisions></soap:Body></soap:Envelope>
当使用域用户'DALRYMPLE'完成相同的调用时,请求超时。
POST http://elvis.ecq.local/sems/Services/DecVotingService.asmx HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.225) Content-Type: text/xml; charset=utf-8 SOAPAction: "http://tempuri.org/GetEventDivisions" Host: elvis.ecq.local Content-Length: 452 Expect: 100-continue Connection: Keep-Alive <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><GetEventDivisions xmlns="http://tempuri.org/"><eventID>165</eventID><isGroupEvent>false</isGroupEvent><roUserName>DALRYMPLE</roUserName><CHKSUM>2de3f62d249a2024394e9c410e7904b9</CHKSUM></GetEventDivisions></soap:Body></soap:Envelope>
每台testing使用同一台PC。 什么导致请求超时一个用户而不是另一个?
更新
使用“DALRYMPLE1”的相同testing成功。
POST http://elvis.ecq.local/sems/Services/DecVotingService.asmx HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.225) Content-Type: text/xml; charset=utf-8 SOAPAction: "http://tempuri.org/GetEventDivisions" Host: elvis.ecq.local Content-Length: 453 Expect: 100-continue Connection: Keep-Alive <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><GetEventDivisions xmlns="http://tempuri.org/"><eventID>165</eventID><isGroupEvent>false</isGroupEvent><roUserName>DALRYMPLE1</roUserName><CHKSUM>87193ccb2f173499d03e2383d9a989f0</CHKSUM></GetEventDivisions></soap:Body></soap:Envelope>
更新
当请求的内容长度为452时,似乎超时。
更新
我们已经缩小到用于连接到服务器的3G调制解调器。 我们有两种types的调制解调器 – 当请求为452字节时,较新的调制解调器失败,而较旧的调制解调器工作成功。 真奇怪 我们正在调查与现代供应商。
用户DALRYMPLE也可以正常使用LAN连接。
我怀疑MTU,试着把它上移或下移1,看看它是否改变了什么,质量保证进一步的问题,并将其设置为不会中断的值。