Network setup and issues

To be clear, wireless connectivity is not officially supported.
Hog3PC was not built with the intention of running wirelessly or as an RFU but as many users have found in the past it does work in some network environments and we do our best to get end users up and running with these setups if possible.

With that said v3.2.0 is a much more network heavy release as it relies on a cloud type show data management system which is what makes the failover feature in v3.2.0 possible. Because of this it is likely that v3.2.0 is more prone to losing connection over a wireless link. In the upcoming v3.2.1 release (which we are testing right now) we've increased the server loss timeout for wireless connections to make it less likely that a wireless client will lose server and log off if the connection hiccups or the traffic gets too heavy but it is still going to be possible that the connection will be lost.

Now there a few optimizations you can try to make it more likely to have your wireless setup succeed in 3.2.0. First, double check that all computers have their Windows firewall turned off (not just exceptions), disable any un-needed network adapters including bluetooth adapters, and disable any virus scan or malware protection software. Any wireless device connecting to the show must have "run server" unchecked at log on and should be assigned to a net num different that that of the main desk. Also don't connect the router to any greater WAN. Just keep it isolated for the LAN.

The HogNet clock init error on your laptop seems to indicate some process in Windows preventing the Hognet clock process from properly starting (probably the firewall, which theory can be proven by just disabling as opposed to adding exceptions).

To be clear, wireless connectivity is not officially supported.
Hog3PC was not built with the intention of running wirelessly or as an RFU but as many users have found in the past it does work in some network environments and we do our best to get end users up and running with these setups if possible.

With that said v3.2.0 is a much more network heavy release as it relies on a cloud type show data management system which is what makes the failover feature in v3.2.0 possible. Because of this it is likely that v3.2.0 is more prone to losing connection over a wireless link. In the upcoming v3.2.1 release (which we are testing right now) we've increased the server loss timeout for wireless connections to make it less likely that a wireless client will lose server and log off if the connection hiccups or the traffic gets too heavy but it is still going to be possible that the connection will be lost.

Now there a few optimizations you can try to make it more likely to have your wireless setup succeed in 3.2.0. First, double check that all computers have their Windows firewall turned off (not just exceptions), disable any un-needed network adapters including bluetooth adapters, and disable any virus scan or malware protection software. Any wireless device connecting to the show must have "run server" unchecked at log on and should be assigned to a net num different that that of the main desk. Also don't connect the router to any greater WAN. Just keep it isolated for the LAN.

The HogNet clock init error on your laptop seems to indicate some process in Windows preventing the Hognet clock process from properly starting (probably the firewall, which theory can be proven by just disabling as opposed to adding exceptions).