I am more than a tab bot confused, and perhaps someone can help me figure out where to start [:)]
I am trying to set up an ASG box at my small local firehouse, and the configuration is SILLY simple. ASG 8.0 on a an old server I had sitting around (2.6ghz w/ 4GB RAM), 3 NIC's in it (one onboard and one dual-port NIC - it was all I had sitting around).
So I set the box up to basically JUST do firewall and outbound NAT - but quickly found that the box was not allowing connections to our medical billing/reporting system for no apparent reason. I did not have any proxy, IPS, even AV configured - so there was no clear answer as to why this was the case.
I swapped out the ASG box for the old router that was in place and it started working again. It should be noted that there is/was no inbound NAT'ing taking place - literally, just a NAT gateway. The ASG should have behaved in the same fashion...
I also noted that the box would go to VERY high CPU for no apparent reason - and I mean it would hit 100% CPU for 10 mins or so - with no clear cause. It coincided with the 15 min updates for the dashboard or close to it, but the stupid low amount of traffic does not make sense as to why that would be. We are literally talking 4 machines on the entire network.
Putting Wireshark on both sides of the firewall shows the packets trying to get to the medical reporting site, but not making it through the firewall.
I also tried changing the NIC assignments, but that did not help either... ??? I run this at home with ease, and a significantly more complex configuration... I could reinstall, but I want to find the cause or I could be making more needless work for myself. In the end, I had to remove it from service, and go back to the router.
I looked at every live log I could find to no avail. Anyone have any suggestions where I should look to troubleshoot the issue, if there is nothing of significance in the logs?
Thanks,
Bob
This thread was automatically locked due to age.
