AnywhereUSB driver DgAwEncx.exe causing TCP Port Exhaustion

One of our clients Windows 2012R2 servers is unstable and multiple services cease to function every 3 to 6 days.
When this happens Windows filsharing to the server errors out, from testing loopback adresse on server itself an error is displayed:
“The name limit for the local computer network adapter card was exceeded.”
An additional symptom is failing RDP connection from affected server to other servers thorws “Internal Error”

We are only able to resolve the issue by restarting the server.

In the event log we find repeated issues when issue plays up:
Event ID 4231
A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.

Event ID 4227
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.

We’ve been able to narrow down the issue by running:
netstat -aqo
Which shows us a large number of ports with status BOUND. This number is increasing as time passes. Sample line:
TCP agfa-rip:0 BOUND 1168
Nearly all of the BOUND ports are tied to the same process number. When looking up the process involved, it is tied to AnywhereUSB service and driver DgAwEncx.exe
Counting the number of bound ports using
(netstat -aqo | Select-String -Pattern BOUND | Measure-Object -line).Lines
We see the number near double from 1168 after only 5 hours since reboot to about 3244 the next day, and only 100 BOUND ports are tied to other process IDs.

A restart of the AnywhereUSB service releases the bound ports.

The version of the AnywhereUSB driver installed is:

Any suggestions on how to remedy this issue would be most welcome.



I’m having the same issue here.

This was solved on our end by uninstalling the driver, and installing the latest one. I think I posted the details of the solution on another forum. Apparently the version in my question had a bug that caused this.