01-26-2017 02:39 PM
01-26-2017 07:14 PM
01-27-2017 12:24 AM
I encountered the same issue a few months back after upgrading to v200.2.9.13.186. I logged a support case for it and was advised that it might be fixed in a future release, but in the meantime it could be worked around by using a static IP. Here's a thread on the subject: