OK - this is wierd, has anyone else seen this behavior and have a solution? I'll schedule a scan job and it runs to completion as it should. But, during the scan and until the next reboot the server (2003) attempts unsuccessfully to connect to many of the clients in the scan group on port 135 with a null SID. This continues until I reboot the server then it starts again when the next scan starts. Thoughts?
↧