Lost Network Connections to File Server and NAS After SonicWall Firewall Installation

If you are using the different ethernet ports for your zones, you will manually have to create firewall and forwarding rules from each one to the others

Hi Scott,
Each ethernet port on the TZ270 firewall is in fact assigned a different zone.  And none of the zones should be able to talk to each other in any way.  My problem is with devices in the same zone.  The firewall ethernet port that is assigned to "Work" is connected to a Dell unmanaged switch that is then connected to all of the devices.  The server, desktop, NAS and printer are all using static IP on this one network.  Do I need to create rules for allowing services in the same zone?  For example, allow DNS between Work and Work?  If so, what services do I need to allow?

arnold - very sound advice.  You are 100% correct, I did not make the changes in phases.  I was driven to do this all at once for several reasons.  My prior configuration used a Juniper Networks SSG5 firewall that stopped working for some unknown reason after my internet service went down.  I was planning on upgrading the firewall because it was a bottleneck with its lack of support for gigabit and that it was end of life.  My wife who is a doctor works from home and needed her internet working ASAP.  My son was home from college finishing his summer job via remote work and also needed his internet ASAP.  I purchased the SonicWall and deployed it under fire, while dealing with some family health emergencies - a very non-ideal way to roll it out.  I know it is not ideal, but I would like to try to get this working without unplugging everything and starting over.  If that is the only way, then I will bite the bullet.  

Does my problem sound like something caused by my firewall or could it be something on my server?  I checked the server and all the AD services are running.  However, when I look at my NIC on my work PC it is saying I am connected to "Network 3, a private network".  It is not showing my domain name.  When I am logged into the server and looking at its NIC, it says it is connected to MyDomain.local. Does this help diagnose the problem?

Even though all the services are running, would it be worth the try to restart my file server in an effort to resolve this AD/DNS issue?

Additional note - after searching various forums I came across this advice for this situation:

Normally when I've seen this I've had to unregister the PC from the domain, clear all DNS records from the DC, and then rejoin the domain.

That makes some sense to me.  What do you think?  How do I do this exactly?

Best wishes ...on all counts

Enable smbv1 on the Windows 10 as described in the link, if your nas does not gave an option to enable smbv1 support.

The problem, you made many changes to what you have, drive mappings for a user are within the user profile.
Disjoining the system from a domain does not alter user profile settings as you will be reading it on rejoin, unless you rename the user's folder.

My understanding you have one zone on the sonicwall feeding an unmanaged switch to which all your devices are connected, correct?

The wife's and son's internet access is going through the other interfaces. Correct?
But the operation of the office, relies on these servers?

As the user, regedit hkey_current_user\softwate\microsoft\currentversion\explorer
I think it is under this or the Windows nt stracture of the same path.

What you are looking for is mountpoint2 key where the mapped drives/UNC mappings are.

Misread/misinterpreted your disjoin/rejoin related question. Post reared.
The server setup is shielded from accessing the Internet?

Confirm IP on the workstation does it use DHCP to get an ip or is it static as well?
Deals with whether it has a path to the IPS of the server/Nas.

The domain designation on the network is Aitomatic, discovery when a domain based system boots and looks to locate the DC to process GPO that is when it determines whether it is domain based, or determines classification public or work/private.

Work/private even public will not interfere with traffic outgoing from the workstation to access server, or nas.
A quick fix to try, set a static ip on the workstation in the same range as the one on the server and see if access is restored.
What do you get when you run
Nslookup -q=SRV _ldap._tcp.dc._msdcs.mydomain.local

Do you get your server as a response?

You could look through the ARP table on the sonicwall to determine which zone this PC is in versus where the server is. And then setup the inter zone access rule.
I.e. Allow the PC to access the other zone by specific rules ....

Continuation.
Often, when the workstation is booted before a DC is available it would fall into a classification  commonly public, but when manually changing classification, the option is provided to make the new choice the default when connecting to hew networks.

Main issue is that your workstation, windows 10, lost access to all the resources, not just one. This is why I think it is in the wrong zone/ip.... than the server and the nas. presumably the server can access the nas; or you have three devices in three different sones.

Can you bring the ssg5 back?
Not sure the significance of the port speed limit on the ns5.

Depending on what you have, the 100 MB connection to the internet should be sufficient the internal communication will be at the switch level, direct communication between servers, nas, and computer if they are within the same zone.
100MB limit will not impact anything since (if I remember your question) you do not have any inter zone communication.


depending on what your upstream feed is, reconnecting the NS5 as it was provided the sonicwall has been configured to use the prior IP ranges.
if the upstream can have two ethernet ports, the ssg5 and the sonicwall can both be connected to the upstream feed.
then you can work with both connected, the Wife's and Son's feeds can be left on the sonicwall, while the rest reestablished, and reworked.

Hi Arnold,
You gave me a lot of info to absorb.  I will be looking at this and posting some questions and follow-up in the next 6 hours or so.  Thank you!

Hi Arnold, I finally have a block of time to try to resolve this problem I created. First, I looked into the SMBv1 issue you mentioned in your last post. I saw a similar issue discussed on a Synology forum, btw. You were right. My NAS was configured to ONLY accept SMB1.  I changed the settings on the NAS so that it requires SMB2 with Large MTU as a minimum and SMB3 as a maximum. Here is a pic of my new settings.  
Note Enable Opportunistic Locking was previously checked.  Now that I am accepting SMB2, should the "Enable SMB2 lease" box also be checked?

I also modified my W10 desktop by turning off SMB 1.0/CIFS Automatic Renewal and SMB 1.0/CIFS Client. Here is a pic of how my W10 desktop is now configured.
Since these two changes, I noticed some improvement.  When I reboot I still do not see my server of NAS drives.  When I go to map the first server drive, I need to enter my username and password for the domain.  Once I do that for the first server drive, I can now map the other two drives without entering my credentials.  The same thing is true for the three NAS-mapped drives.  I enter my domain username and password for the first mapped NAS drive and it remembers it for the other two mapped drives.

I am now going to move on to try and figure out why it cannot remember my credentials in the first place. I think the key reason is that the PC cannot contact the domain controller to authenticate the request.

Windows only provides response for credentials to things it sees as a local LAN.

Something makes the auto detection of the LAN whether it is as you not inability to talk to the DC.......

Not sure about large MTU, minimum option should be minimal.  

Smbv2 lease, not sure test with both modes. Lease suggests it will add overhead to periodically refresh the connection/access

Problem Solved! Thank you, Arnold.  It turns out that after I fixed the SMBv1 problem I also had a problem with my NIC settings.  I had my NIC using external DNS servers on the internet, not my file server's DNS.  No wonder it could not resolve the address for my mapped drives!  Once I changed my DNS server to my file server, I mapped all 3 server and all three NAS drives.  Then when I rebooted my startup bat that maps the NAS drives ran successfully for the first time and I was able to see all 6 mapped drives without having to log in!  Very relieved!  Thanks for all your patience.  I will have some follow-up questions in a separate post sometime soon, if you would be willing to help me some more.  Take care.

Glad to hear.

Post the next question here after you open it.
I'll take a look if possible, or know the subject ....