VLANS with DHCP server on Sonicwall Firewall - VLAN Clients not displaying in File Explorer

Question

DHCP is handled at Sonicwall and working correctly. Recently, we setup VLANS in Sonicwall and they are working correctly. What is NOT working is those VLANS being able to use UNC path to network folders. 2nd, The VLANS cannot connect to any shared names from servers. All servers are on the existing LAN IPs. I read where I needed to add a reverse lookup zone. I added the reverse lookup zone at the 2016 DNS manager.
Default IP 192.168.16X
VLAN IP 192.168.30.x
Reverse Lookup Zone 16.168.192
Reverse Lookup Zone 30.168.192
The hope is for those on the VLAN to use UNC shortcuts to servers on the 16.X LAN.
If they open the file explorer, the hope is to view those servers or clients in Network and view what is either mapped OR UNC for those shares.
What am I missing?
Thank you.

Answer 1

Hi ,

Before we go further, I would like to confirm the following questions:

1.How did you access network share? Via \IP address or \hostname?

2.Can you ping IP address successfully from VLAN Clients?

3.What's the exact error message if you cannot access network share?

4.What's the OS version of your VLAN clients?

Best Regards,

Candy

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

CandyLuo,
We have access the network share both ways. \sharename and or \IP address. Those on the 16.x network have no issue. Those on the new VLAN 30.x cannot see clients in the network.
Yes, we can ping those 16.x IPs from the command prompt.
WIndows 10 Pro clients

FYI, I can ping the 30.x from my 16.x my client machine with admin rights.

Here is something that I attempted to do today but failed. It might have some indications for you. I needed to add a new client in the VLAN and when I attempted to add that client via the wizard, it could not find the DNS server. However, I could do a command prompt ipconfig /all and the DNS was listed. It is pulling the correct VLAN IP address.

It is obvious I have something missing or incorrect. Most everything else seems to be working correctly.

@Anonymous