Event ID 4227 — TCP/IP Network Connectivity
Updated: April 17, 2008
Applies To: Windows Server 2008
Network connectivity allows your computer to communicate with other hosts on your network and the Internet. Connectivity might be full (Internet and intranet), partial (local subnet only), or non-existent.
|Product:||Windows Operating System|
|Message:||TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.|
Refresh the protocol configuration on the network interface by disabling it and then enabling it again.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To disable and then re-enable the network interface:
- Click Control Panel, double-click Network and Sharing Center, and then click Manage network connections.
- Right-click the network interface you want to disable, and then click Disable.
- Right-click the network interface again, and then click Enable.
To verify TCP/IP connectivity:
- Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
- Type ping followed by an IP address of another host on the network.
- If the ping command succeeds, connectivity is established.
Note: Windows Firewall might prevent a succesful ping operation. You might need to configure a port exception for the ping to succeed.
Related Management Information