+ Reply to Thread
Results 1 to 4 of 4
  1. #1
    Registered User
    Join Date
    02-28-2007
    Posts
    154

    Might have found the activesync problem

    I noticed the other day when I connected my phone (and it refused to connect) that my system logs had some new entries.

    Here they are in order. As you know when the phone connects it grabs an IP address.

    ..............
    TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
    .......................
    Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000F1F26A078. The following error occurred:
    The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
    .............................
    Your computer has lost the lease to its IP address 192.168.1.100 on the Network Card with network address 000F1F26A078.
    ......................................................

    If you paste these errors in google they have a patch to fix it. Since I ran the patch I have not had any failures to connect and I have not had any more of these entries.

    FYI

  2. #2
    Registered User
    Join Date
    10-30-2007
    Posts
    60
    Why not post a link to the patch for the convenience of all?

  3. #3
    Registered User
    Join Date
    02-28-2007
    Posts
    154
    Windows XP SP2
    additional tweaking information
    2004.09.18 10:29 EST by Philip


    In addition to the tweaks already covered in Win 2k/XP Registry Tweaks and More Win 2k/XP Tweaks, the Windows XP Service Pack 2 introduces a few new issues covered in the article below. Please make sure you understand what you are doing before making any changes to your Operating System. Note the information below only applies to Windows XP Service Pack 2.



    Remove the limit on TCP connection attempts

    Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and "reduce the threat" of worms spreading fast without control. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time.

    Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?... If you also consider that each of those infected computers will infect 10 others at the same rate:
    second 1: 1+10 computers
    second 2: 10+10*10 computers (110 new ones)
    second 3: 10+100*10 computers ( 1110 new ones)
    second 4: 10+1000*10 computers (11110 new ones)
    ....
    all the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute.

    In other words, even though it is not going to stop worm spreading, it's going to delay it a few seconds, limit possible network congestion a bit, and limit the use of your PC to 10 connection attempts per second in the process ! I have no problem with the new default setting limiting outbound connection attempts. Still, users should have the option to easily disable or change this setting. I might be going out on a limb here, but ever since the introduction of Windows XP I can't help thinking that I dislike all the bult-in Windows "wisardry" in a sense that the system also limits user access. That irritating trend to ease the mental load on end users is somewhat insulting, considering that Windows is to make the more "intelligent" choice instead of the end user, as well as limit their access to tuning such settings...
    End of rant.

    With the new implementation, if a P2P or some other network program attempts to connect to 100 sites at once, it would only be able to connect to 10 per second, so it would take it 10 seconds to reach all 100. In addition, even though the setting was registry editable in XP SP1, it is now only possible to edit by changing it directly in the system file tcpip.sys. To make matters worse, that file is in use, so you also need to be in Safe mode in order to edit it.

    You only need to worry about the number of connection attempts per second if you have noticed a slowdown in network programs requiring a number of connections opened at once. You can check if you're hitting this limit from the Event Viewer, under System - look for TCP/IP Warnings saying: "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Keep in mind this is a cap only on incomplete outbound connect attempts per second, not total connections. Still, running servers and P2P programs can definitely be affected by this new limitation. Use the fix as you see fit.

    To change or remove the limit, you can use the following program:

    Event ID 4226 Patcher - A patching program for removing or changing the limit imposed on connection attempts in SP2. The patcher has the ability to restore tcpip.sys back to the original... Still, you might want to back up tcpip.sys, use it at your own risk. The author of this patch can be reached @ www.LvlLord.de - Tipps, Tricks & Utilities - News



    Edit tcpip.sys manually to remove the TCP/IP socket creation limit

    Another option, for the more adventurous is to modify your tcpip.sys file manually, using a hex editor. The following instructions refer to the final release of XP SP2, with a tcpip.sys file of exactly 359,040 bytes, CRC-32 is 8042A9FB, and MD5 is 9F4B36614A0FC234525BA224957DE55C. Even thouh there might be multiple tcpip.sys files in your system, make sure to work with the one in c:\windows\system32\drives\ directory.

    To remove the tcpip.sys socket creation limit:
    - Backup your original tcpip.sys file before editing please, this is somewhat important !
    - In your hex editor, go to offset 4F322 hex (or 324386 decimal).
    - Change 0a 00 00 00 to 00 00 0a 00

    All done ! The above change does not require editing of the CRC in offset 130 hex (thanks for the clever solution Thomas Wolf Tompkins).

    Notes:
    If any of the data above does not match exactly (crc, file size, md5, or the data at offset 4F322) please double-check what you are doing, or abort completely.

    The above information increases the RATE of opening outgoing connections. It has nothing to do with the limit of 10 connections to network shares on a Windows workstation PC for sharing files (a MS imposed limit to force you to upgrade to a server version of the OS). This 10 connections to network shares limit was introduced with NT4 workstation (SP3), and exists in Windows 2k workstation, and Windows XP home/pro/mc. It only applies to authenticated windows services, such as file and print sharing.

    www.LvlLord.de - Tipps, Tricks & Utilities - Downloads

  4. #4
    Registered User
    Join Date
    02-28-2007
    Posts
    154
    Let it be so........

    www.LvlLord.de - Tipps, Tricks & Utilities - Downloads


    ..............
    Event ID 4226 Patcher (4226 fix)

    What's this all about?
    After almost everybody knows the <<EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts>>, I used a day to create for educational purpose a fix for this argumentative feature.

    Unfortunately there exists no REG-key which could easily be set (would be so nice and easy, right? *smile*). The file TCPIP.SYS in the directory C:\WINDOWS\SYSTEM32\DRIVERS and C:\WINDOWS\SERVICEPACKFILES\I386 has to be changed (system dependend eventually in C:\WINDOWS\SYSTEM32\DLLCACHE, too).

    Needed things:
    - Windows XP SP2 (from RC2 upwards) or Windows 2003 Server SP1 beta
    - patcher
    - a small amount of time

    What's been done:
    To say it easy: the before 10 half-open connections are beeing increased to 50 (can be changed during runtime and with the parameter /L) and the CRC is been corrected. And that's it!

    Comment:
    The method described here, should only be used by users, who know how to handle all the described. With the download of the here published program the user know, that changes are made on third party files. For damages in every kind I cannot be hold responsible for. Indeed, tests worked fine here. However, nothing is impossible.
    Info: When error occurs, the patcher can change the TCPIP.SYS back to the original!

    Instruction:
    Just download the patcher and execute it. It will automatically find the windows directory and ask, if it should increase/decrease. For higher values, please check the help with parameter /?.
    After a successful patch, the new TCPIP.SYS will be automatically installed. After that, the computer should be restarted.


    Windows MIGHT complain about needed system files being altered and damage etc etc...
    Last edited by madmax200; 01-19-2008 at 11:33 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts