Ask a new question

Network errors after Upgrading to Win10 1703 WSAENOBUFS (10055)

Hi there,

I recently updated my Dell Precision M6500 to Windows 10 1703 "Creators Update".

Both Windows 10 Versions before were working without bigger problems.

Now, after some time, my system stops beeing able to connect to any Network Target (Internet, LAN, or local). Some tools return "WSAENOBUFS (10055)" errors, some do just not connect ("could not connect...").

None of our own tools could connect, nor browsers, DBs, etc.

Established connections continue to work, e.g. copying files from network shares, etc.

More network usage results in faster occuring of connection problems.

Any suggestions?

Example error message (sry, its in german, i translated the error message back to its error code 10055)

Image

Hello,

The error message you're getting translates to:

   " An operation on a socket cannot be performed because the system lacks sufficient buffer space or because a queue is full. "

You may increase the maximum number of ephemeral ports as a resolution to this issue.

Have you updated your network adapter driver yet? Incompatible or outdated driver could cause connection issues such as this.

You may also run the Network troubleshooter if drivers are all up to date.

Check our support page for available workarounds and guidelines regarding the connectivity issue you're experiencing.

Let us know if you have questions.

Regards.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi again,

The Network troubleshooter did not help.

Updating the driver is not possible, no direct driver from the manufacturer and the current driver for the "Broadcom NetXtreme 57xx Gigabit Controller" is from Microsoft (20.8.2015, Version 17.2.1.0). No further updates available.

I was able to reduce the occurence of the error a lot by removing the "HyperV Virtual Switch", sitting in between everything.

The error happens very rarely now. Maybe there were some changes introduced in 1703 in HyperV which caused these errors.

Do you know anything about this?

I do not know why i should need to "increase the maximum number of ephemeral ports", it was never necessary in the prior windows version with the identical configuration (HyperV Switch + Broadcom). 

When i need the VMs again, i will be forced to reactivate the HyperV switch.

If it will then happen again, i will follow the linked steps and report back here about success or failure.

Thx

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated April 20, 2025 Views 295 Applies to: