I set up a SonicWall TZ280W for a small medical office with separate wireless networks for staff, guests, and cameras. Internet access and printing worked, but scan to desktop folders stopped working. The copier was still connected to the internet provider's router, and changing its IP did not fix things.
What should I check before changing more of the network?
Start by mapping the actual path. Record the copier's IP, subnet mask, gateway, and DNS settings, then do the same for an affected workstation. Check which device is handing out DHCP addresses and whether the old and new networks use overlapping subnets.
Printing and scanning to a folder go in opposite directions. A workstation reaching the copier does not prove the copier can reach a shared folder on the workstation. Check the destination address and credentials in the copier's address book, as well as the workstation's file sharing settings.
For a quick isolation test, put the copier and a test workstation on the same staff network and check both printing and scanning. Give the copier valid settings for that network, then update any printer configuration that still points to its old IP.
If that works but the separated setup does not, investigate routing and access rules between the networks. Once you know the path, allow the specific traffic needed rather than opening everything between VLANs.
Don't rely on ping alone. From a suitable test machine, check whether the destination responds on the file sharing port, usually TCP 445 for SMB. That test from a workstation is useful, but it does not prove the copier has the same access.
Try a scan while capturing packets on the SonicWall. If the traffic passes through it, the capture can help show whether a rule is blocking it or whether the destination is failing to respond. If an IP responds to ping, unplug the copier briefly and check that the response stops. That can expose an address conflict or a test against the wrong device.
Check the provider router setup too. If the SonicWall WAN has a private address, there may be two routers doing NAT. That is not proof of the scan problem, but leaving the copier on the upstream network can make the path awkward.
Having the office devices behind the firewall and the provider equipment in bridge mode may simplify things. Confirm the provider's requirements and plan the change first, especially if the connection uses a static address.
Get a senior firewall engineer to review the configuration with you before making more production changes. A firewall alone does not establish compliance for a medical office. Review management and remote access restrictions, logging, and whether the licensed features meet the office's requirements.
Answers are reviewed before publication.
~rearrange!the+furniture:
If the address book uses workstation names, check whether the copier can resolve those names as well as reach the resulting addresses.