Event ID 4227 when a client application tries to connect to a Windows Server 2008 SP2-based server during a dynamic port allocation process

Symptoms

When a client application tries to connect to a Windows Server 2008 Service Pack 2 (SP2)-based server during a dynamic port allocation process, the connection fails, and the application does not work as expected. Additionally, event ID 4227 is logged on the server, and the client application receives a WinSock error 10048 (WSAEADDRINUSE).

Notes

Cause

This issue occurs because a new dynamic port that has a "Closing" status is allocated. Then, the Tcpip.sys driver registers the event ID 4227 on the server.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 SP2.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    23xxx

    Windows Server 2008

    SP2

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are

    listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.23264

31,232

02-Nov-2013

11:42

x86

Tcpip.sys

6.0.6002.23264

915,392

02-Nov-2013

13:24

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.23264

40,448

02-Nov-2013

12:23

x64

Tcpip.sys

6.0.6002.23264

1,417,152

02-Nov-2013

14:15

x64

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Tcpipreg.sys

6.0.6002.23264

80,896

02-Nov-2013

11:29

IA-64

Tcpip.sys

6.0.6002.23264

2,976,192

02-Nov-2013

13:11

IA-64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

File property

Value

File name

X86_07d832875b515e11fe3999cc548cc028_31bf3856ad364e35_6.0.6002.23264_none_2b23f4283c15afe6.manifest

File version

Not applicable

File size

717

Date (UTC)

05-Nov-2013

Time (UTC)

07:09

File name

X86_3b48f9f8dc57d913deb2d9f72b6317af_31bf3856ad364e35_6.0.6002.23264_none_815b028d63e6b50b.manifest

File version

Not applicable

File size

702

Date (UTC)

05-Nov-2013

Time (UTC)

07:09

File name

X86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.23264_none_8850572a1bde0ab9.manifest

File version

Not applicable

File size

4,845

Date (UTC)

02-Nov-2013

Time (UTC)

13:40

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.23264_none_b55133757cd75123.manifest

File version

Not applicable

File size

6,400

Date (UTC)

02-Nov-2013

Time (UTC)

13:41

Additional files for all supported x64-based versions of Windows Server 2008

File property

Value

File name

Amd64_e3bf7d0554c2c36ba963d571463e64b6_31bf3856ad364e35_6.0.6002.23264_none_bea0c8227a5202a0.manifest

File version

Not applicable

File size

706

Date (UTC)

05-Nov-2013

Time (UTC)

07:09

File name

Amd64_e441d8f93eea3011129e54d91e13e6b5_31bf3856ad364e35_6.0.6002.23264_none_c487551864b86765.manifest

File version

Not applicable

File size

721

Date (UTC)

05-Nov-2013

Time (UTC)

07:09

File name

Amd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.23264_none_e46ef2add43b7bef.manifest

File version

Not applicable

File size

5,122

Date (UTC)

02-Nov-2013

Time (UTC)

14:33

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.23264_none_116fcef93534c259.manifest

File version

Not applicable

File size

6,422

Date (UTC)

02-Nov-2013

Time (UTC)

14:34

Additional files for all supported IA-64-based versions of Windows Server 2008

File property

Value

File name

Ia64_1eea6fd3c7b4167e49b833da130dd1b0_31bf3856ad364e35_6.0.6002.23264_none_88cab8bbb592f16f.manifest

File version

Not applicable

File size

1,066

Date (UTC)

05-Nov-2013

Time (UTC)

07:09

File name

Ia64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.23264_none_8851fb201bdc13b5.manifest

File version

Not applicable

File size

5,118

Date (UTC)

02-Nov-2013

Time (UTC)

13:29

File name

Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.23264_none_b552d76b7cd55a1f.manifest

File version

Not applicable

File size

6,411

Date (UTC)

02-Nov-2013

Time (UTC)

13:29



Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×