Network Problem
-
Is the Spiceworks install new? Try turning it off. Spiceworks has been known, from time to time, to cause switches and other gear to crash and/or reboot due to bad reactions to the scanning process.
-
Yes we are using the new Spiceworks.
-
@Joyfano said:
Yes we are using the new Spiceworks.
And the problem only started after Spiceworks was running?
-
Yes. Yesterday i run the Spiceworks early in the morning. Okay i stopped scanning the network now.
-
How quickly will you be able to tell if the issue has subsided?
-
Are you scanning anything on your network other than Windows machines and the switches?
-
@scottalanmiller said:
How quickly will you be able to tell if the issue has subsided?
I have to wait till the end of their shift till 5:00 PM.
-
@scottalanmiller said:
Are you scanning anything on your network other than Windows machines and the switches?
No its only for windows machine and switches.
-
If turning off Spiceworks fixes the issue, you will likely need to exclude the switches from the scanning range. Or you might want to consider a different tool for the scanning. For Windows machines, for example, Meraki SM is free and very robust and has no network effects.
-
@scottalanmiller said:
If turning off Spiceworks fixes the issue, you will likely need to exclude the switches from the scanning range. Or you might want to consider a different tool for the scanning. For Windows machines, for example, Meraki SM is free and very robust and has no network effects.
Thank you for the suggestion. I we will find out later. I would like to use another free application.
-
Meraki is free and because it installs onto the Windows boxes (and Macs) it doesn't do the network scan. So it is massively easier to manage, more reliable and more secure because you can leave your ports closed.
