We could tell it was something to do with having two WAN connections because when we ran on only one (which was our faster one), everything was fine. Unfortunately that proved to be a dead end as well.
Deer hunter for pc cracked#
Responses from the community led me to think we'd cracked it and that it was caused by packet splitting when spilling over from one WAN to the other. I logged a support case with SonicWALL and also posted on the Spiceworks community. Eventually we realised that making any setting change on the SonicWALL - enabling or disabling a rule or a policy - would fix it for about 15 minutes. Everything started to work again, and our email was flowing once more. There was one we weren't sure about so we disabled it. We went back to checking our settings, including NAT Policies. I searched discussion forums and took some comfort from apparently not being the only one, but the thread I found didn't offer me a solution. Opening the Exchange Queue Viewer showed a stack of undelivered messages with - guess what - DNS failures. To make matters worse, I then realised our Exchange server wasn't sending any email out. Unfortunately it all broke again a few minutes later. I switched it off and - bingo! Our DNS and browsing all came to life again. I checked and found one of them still switched on in one of the zones. content filtering) but our intention was to operate with all those switched off in the first instance in case of performance problems. The router included bundled subscriptions to SonicWALL security services (e.g. (The SonicWALL uses its own DNS settings to resolve names in reports, for example, but ordinary Web browsing requests should be handled by the DNS server.) Security services We played around with DNS settings on the SonicWALL, but we knew they shouldn't have been relevant because DNS requests from users are handled by our DNS server. Web browsing was very slow - a real disappointment for Day 1! After a while we figured we had a DNS problem because all our nslookups, pings and tracerts to external sites were failing. It was only when we went live that things unraveled. Every so often the CPU would hit 100% and then we'd lose connectivity on both connections.)ĭuring configuration, testing and initial deployment of the SonicWALL all seemed well. (We have two Internet connections and our venerable Zyxel was unable to cope with rising demand.
We recently upgraded our router from a Zyxel Zywall 35 to a SonicWALL NSA 240.