Cameras Unreachable From Milestone Server, Why?

I have a customer that is running Milestone 2014 Professional. The system is comprised of 4 buildings. 1 Server per building and it is running in a master slave environment. OS is Windows 7 Professional. The issue that I am having is at random a camera will no longer respond to pings from the server. If I login to the switch I can ping the camera fine. If I plug my laptop into the switch I can ping the camera just fine. Disabling and re-enabling the NIC sometimes works. Also sometimes a reboot of the server will also sometimes fix the issue. Each server is running on its own subnet through 1 NIC on each server. The other NIC on all of the servers goes to the customers LAN. I have never seen anything like this happen before and I am at a loss right now. Any all help is very much appreciated.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

**** ******** ** *** ********* ***. **** ******* *** *** ping *******/******* **** *** **** ********** ** *************.

***********:

- ***** ** *** ** *** *** ********** *** ****, firewalls ** *******

- ***** *** *** *** ************ *** ******** *** (******** activeX, ********* ************, ***.)

- ***** ******* *****

- **** *** ******** ****** **** *****, ******** ** *** ports ******

- ***** *** ********, ** ***** *** ********, ****** ***** draw ** ******

- ***** *** ******* ** ******** ********

***** *** ***** * ***** *****... ** ** ******, ** could ** * ***** ****** ** ******. ***** **** *** now. * ** **** ****** **** **** ***** ***** ** well.

(**** * ***** ****** *** **** ***** ** ** **** trouble ******** ** ****** ** ********* ****)

** **** *** *** *** ***'* **** **** **** *** server, **** **** **** **** *** ***** ****** ** ***** down ** ****? *'* ****** ** ********** *** **** ***** here.

**** **** ****, *** ******** *** *** ** ** *****. I've **** ******* **** **** *** *** ** ********, *** some ******** *** *** ******. ** *** ******* ** *** things ***/*** *** **********.

* ****** **** *** ****** ******. ****** ** ** **** a ******* *****. ****** ** ******** ***********... ***** ****** ***** (255.255.255.0 ** *** *** **** ** ***.***.*.*...); ** ********** **** the ****** ** *** ****** *** **** **** ** ******** as ********; ***** *** *** *** *** *** **** *** switch ***** **'* **** *** *** ********* (**** * **** up/down ***** ********** *** ****** **** ***** *** *** ****'* notice.)

* **** **** ******* ********** ***** *** *** ***** *** a ****** ** ** *** ***** ***. *'* *** **** if *'** **** ******* **** *** **** *******, *** * suspect ** ***** **** ** **** ************* ****** ** *** switch ***** ********* ***** **** ***** ***.

********* *** ** * ******** *** ******** ***/** ***** ** broadcast * ******** ** *** ******* **** "*** *** ** 1.1.1.1? **** ** ** ** *.*.*.*", *** ******* *** **** IP ******* ****** ******* **** ***** *** *******. **** ******** then ****** **** *********** *** * *****.

** ******* **** ******** ****, * **** **** ******* ************* issues (****** ********* **'*, ******** ******* ********** ***) ****** ** the ** ** * ****** ******* ** ** *** *** cache ***** *** ***** ***.

* ******** *** **** ****** ** * **** ***** *** cameras **** ****** ***** **'* *** **** ****** *** ************ their ***** ******* (***.*.*.*).

** ******* *** *** *********** ***** **, **'* ******** ******* the *** ***** ** ******* *****.

*** *** ***** *** ***** ** *** *** ***** ** runningarp -* from the command prompt. Try looking through the result for both the IP and the MAC of the affected camera(s) to see if anything stands out.

* ****'* **** *** ** *** ********* *** **** ***** bitrate? ***** ********* ****** ********** ** ***** *** ********** *******?