We uodated the software as instructed. We continue to have problems as outlined below

Thu May 11 10:29:52 2017 ***** All the error messages of session started at Thu May 11 10:29:52 2017 are shown below *****
Thu May 11 10:29:52 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:30:14 2017 ***** All the error messages of session started at Thu May 11 10:30:14 2017 are shown below *****
Thu May 11 10:30:14 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:33:16 2017 ***** All the error messages of session started at Thu May 11 10:33:16 2017 are shown below *****
Thu May 11 10:33:16 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:39:49 2017 ***** All the error messages of session started at Thu May 11 10:39:49 2017 are shown below *****
Thu May 11 10:39:49 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:43:09 2017 ***** All the error messages of session started at Thu May 11 10:43:09 2017 are shown below *****
Thu May 11 10:43:09 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:47:13 2017 ***** All the error messages of session started at Thu May 11 10:47:13 2017 are shown below *****
Thu May 11 10:47:13 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]
Thu May 11 10:48:42 2017 ***** All the error messages of session started at Thu May 11 10:48:42 2017 are shown below *****
Thu May 11 10:48:42 2017 Visitor Network Interface Card did not bind the PatronSoft FirstHop Driver, or some of the following services failed to start: rasman, lmhosts, netman. Please reboot Windows and start FirstSpot again [may need to do this multiple times]

1)
I use Version 8.1.102 and last saturday (11/1, the firstspot had crashed again (this happens about once every month or sometimes once every two month!)

I know, that the firstspot stops working, cause I use an controlled-ruckus-WLAN thru the firstspot (controller is on Internet-side an the WLAN-APs is on visitorside) and ruckus says, that the wlan-accesspoints where disconnected about 22:00.

strange thing is, that the latest log-entry is about 04:00 of this date.. I dont have any log-entires between 4:00 an the possible crash 22:00? The logging starts then excactly with the new reboot (with was 2 days later!)

I didnt do a Cold-shutdown, just a normal reboot by windows.. but nothing stands in the logfiles ?

Strange?

2) I have the Windows-Update activated on this server. I found out (over win-log-file), that the windows-Update is beeing startet about every 10 min.. It stopps the DNS-client and then starts the DNS-Client again? it also affects the "WinHTTP WebProxy Auto-Discovery-Service" as well?

according to Windows-Update, the KB890830 has failed, the KB4048958 was successfully installed. I dont know the installation-time, only the installation date - and thats the "possible Servercrash"?

=> so I disabled the automatically "windows-update"... Should this be the solution?

1) First, any crash dump and suspicious entry in Windows Event Viewer around that timeframe?

We suspect this is a known problem related to ARP. Please run the below commands and post your output here. If this problem happens again, before restart FirstSpot or Windows, please rerun the below commands so that we can compare between the two.

Code:

ipconfig/all
arp -a
route print

2) There is always a risk in automatic windows update. So we suggest manual Windows update and then retest FirstSpot if you encounter problems._________________~ Patronsoft Limited ~