So my sonicwall 3600 went down. Sonicwall sent a replacement. I uploaded the saved configuration into the replacement and didn't notice any problems.

The next day, users say they can't access the VPN. After a half day talking to Sonicwall support, we figured out that users cannot access the VPN using their UPN as they used to on the old 3600 but can access it using their SAM.

In general I prefer to reconfigure everything from scratch. Initially to get everyone back online ASAP - I understand migrating settings but as soon as you have a maintenance window I'd reset to factory defaults and configure everything from scratch provided that you take good notes of the settings. This insures that there are no issues with the old settings. It is the same philosophy of upgrading OSes opposed to clean installs...I always prefer the later in all aspects.

There is most likely a difference between the SonicOS versions from your old unit vs the replacement and that could be the difference. I'd check the Release Notes of the current firmware to see if there are any known bugs related to this. Then I'd upgrade the SonicOS so that its on the most current release.

Also, re-inspect the NPS and make sure the objects are still correct for the SonicWALL. You may have to remove them and re-create them. Same with the RADIUS authentication on the SonicWALL. You'll most likely need to break the entire existing link and re-establish it between the SonicWALL and the NPS. On the SonicWALL remove the RADIUS settings, reboot and re-create the link again. NPS should take a reboot too.

Featured Post

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!