
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2018 10:33 AM
Solved! Go to Solution.
- Labels:
-
General Discussion

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 02:42 PM
I worked with support and they had me do the following which so far has resolved the issue (so far as in the past 2 days)
- Go to Scanning\Scanned item interval in the web console
- Disable the following:
- PNPSIGNEDDRIVERS
- PRINTERDRIVERS
- SYSTEMDRIVERS

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2022 06:48 PM
I know this is from 4 years ago, but I am now having the same exact issue and not sure where to go from here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2022 12:04 AM
Hello Todd, have you tried to run the netstat command provided by @MB1 above?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 02:42 PM
I worked with support and they had me do the following which so far has resolved the issue (so far as in the past 2 days)
- Go to Scanning\Scanned item interval in the web console
- Disable the following:
- PNPSIGNEDDRIVERS
- PRINTERDRIVERS
- SYSTEMDRIVERS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 05:46 PM
Yes, we're investigating reports that querying Win32_SystemDrivers can cause a performance impact on the scanning server and the scanned system in some circumstances.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-16-2018 02:19 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-16-2018 12:09 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2018 04:27 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2018 11:46 PM
https://blogs.technet.microsoft.com/clinth/2013/08/09/detecting-ephemeral-port-exhaustion/
The standard range of 16.000 should be more than enough for Lansweeper operation, but that depends on your setup, of course... on my setup, with ~9000 machines and a single server, I have 180 connections open right now, not running any schedule scans...
If you want a GUI tool, you have TCPView, but that is getting a little old :
https://docs.microsoft.com/pt-pt/sysinternals/downloads/tcpview
This will shown active TCP/UDP connections, but that error may (*MAY*) indicate another issue...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2018 02:14 PM
I recommend taking a look at this discussion: https://serverfault.com/questions/131935/network-error-no-buffer-space-available
It might be someone else holding your network buffers without releasing them.
