Windows 7 network polling?
I Recently installed Windows 7 to work on a project that relies heavily on socket layer communication (using Chromium and OpenGL) and have not been able to get the Chromium (BTW NOT Google's project) client to talk to the Chromium server. I have this same project working on Vista and XP with no problems. My symptom is that I get the message "Connection Refused" when the program tries to make the connection. WinDump indicates that the Windows 7 box is continually issuing a string of commands like:22:22:20.043211 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 42:63(21) ack 1 win 6521022:22:20.143811 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 63:84(21) ack 1 win 6521022:22:20.143830 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 84 win 539322:22:20.244384 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 84:107(23) ack 1 win 6521022:22:20.344962 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 107:129(22) ack 1 win 6521022:22:20.344980 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 129 win 539322:22:20.445554 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 129:150(21) ack 1 win 6521022:22:20.546149 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 150:171(21) ack 1 win 6521022:22:20.546182 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 171 win 539322:22:20.646772 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 171:192(21) ack 1 win 6521022:22:20.747331 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 192:213(21) ack 1 win 6521022:22:20.747353 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 213 win 539222:22:20.797830 arp who-has launchmodem tell OldLaphroaig.launchmodem.com22:22:20.798305 arp reply launchmodem is-at 00:0f:db:c6:a4:02 (oui Unknown)22:22:20.798318 IP OldLaphroaig.launchmodem.com.50304 > launchmodem.53: 38836+PTR? 17.10.168.192.in-addr.arpa. (44)22:22:20.800041 IP launchmodem.53 > OldLaphroaig.launchmodem.com.50304: 38836*1/0/0 (64)22:22:20.847906 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 213:237(24) ack 1 win 6521022:22:21.050061 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 237:263(26) ack 1 win 6521022:22:21.050083 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 263 win 539222:22:21.150638 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 263:284(21) ack 1 win 6521022:22:21.352643 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 284 win 539222:22:21.362552 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 284:313(29) ack 1 win 6521022:22:21.463142 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 313:334(21) ack 1 win 6521022:22:21.463161 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 334 win 539222:22:21.563725 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 334:355(21) ack 1 win 6521022:22:21.664314 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 355:376(21) ack 1 win 6521022:22:21.664331 IP OldLaphroaig.launchmodem.com.49192 > sciend.3389: . ack 376 win 539222:22:21.764896 IP sciend.3389 > OldLaphroaig.launchmodem.com.49192: P 376:397(21) ack 1 win 6521022:22:21.821170 IP OldLaphroaig.launchmodem.com.61870 > launchmodem.53: 49047+PTR? 40.10.168.192.in-addr.arpa. (44)22:22:21.822951 IP launchmodem.53 > OldLaphroaig.launchmodem.com.61870: 49047*1/0/0 (69)while the XP and Vista machines are completely quiet. Can anyone tell me what is going on? I have only the one on board NIC and am connected to only one network.The Chromium connection is trying to connect through localhost. I have a debug statement in the server code that indicates the server never gets a chance to either accept or reject the connection request. I'm convinced the WinDump output is a clue to a network setup issue that is causing the problem. I've been at this for quite some time now and am at wit's end. Any help would be greatly appreciated.
March 18th, 2010 5:33pm

This issue can be caused by the incompatible Kerberos encryption types. I suggest that you make the following changes on the Windows 7 computer: 1. Open gpedit.msc. 2. Find the policy Windows Settings -> Security Settings -> Local Policies -> Security Options ->Network Security: Configure encryption types allowed for Kerberos 3. Configure the policy. If it is not configured, actually both DES cipher suites are disabled. I suggest that you enable all the suits. Then please check the result. If the issue persists, please change the NTLM type in Windows 7. You may refer the following article. Network security: LAN Manager authentication level Please find the following policy Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level Change the level to “Send LM & NTLM - use NTLMv2 session security if negotiated”.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2010 12:07pm

Thanks for the reply. I've been working on an XP system and just now got back to the Windows 7 problem. I made teh adjustments to the group policy as you suggested but Chromium still does not connect. I pulled up my XP box group policy settings and tried to make the 7 policies look as much like the working XP settings as I could. Obviously, I couldn't make them look exactly the same since 7 has more choices. I also tried using the ip address directly instead of relying on localhost and the connection is still refused. Is there a tool or some setting that will log attempts and failures that might give me a better idea of why there is a failure?
March 25th, 2010 4:53pm

You can track network packages with Network Monitor 3.3. Microsoft Network Monitor 3.3Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2010 6:03am

My problem turned out to be an ipv4 vs. ipv6 issue. The listener opened the socket as an ipv6 socket while the client was trying to send data to the socket as an ipv4 socket. Once I forced the listener to create the socket as AF_INET everything worked.
April 1st, 2010 6:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics