Windows Server 2012 R2 multiple machines often have events 4227, 135, 4231.

Question

Windows Server 2012 R2 multiple machines often have events 4227, 135, 4231.When these events occur, the server will not be able to connect to the public network, resulting in the production system unable to use.The server must be restarted to recover.Is there any corresponding solution?

Answer 1

Hi,

I am doing research on the error codes, since it may need some time to do research, I will get back as soon as I get any update.

Thanks for your understanding!

Best Regards,
Anne

Answer 2

Hi,

• Check if decrease TcpTimeWaitDelay and increase MaxUserPort could help to solve the issue.

The location of the TcpTimeWaitDelay is:

HKEY_LOCAL-MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters. Add REG_DWORD named TcpTimedWaitDelay, we may set the value to 30 seconds, by default, the value is 4 minutes.

Here is the detailed information about TcpTimedWaitDelay:

https://technet.microsoft.com/en-us/library/cc938217.aspx

• Then we may use command netsh int ipv4 set dynamicport tcp start=10000 num=20000 to expand dynamic port range.

For more information about the error, please refer to the following links:

https://social.technet.microsoft.com/Forums/ie/en-US/b632acdc-a546-4014-a299-4c27781e6c5a/tcpip-failed-to-establish-an-outgoing-connection-event-id-4227?forum=winserverPN

https://borncity.com/win/2016/12/20/events-id-4231-and-4227-tcpip-no-internet-connection/

(Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
)

---

If the reply could be of help, please help to accept it as an answer, thanks for your cooperation!
Thanks for your time!
Best Regards,
Anne