1
Currently configuring a new mac server to be used in an environment with 40+ macs. I am having an issue accessing the server using server.local on devices that our connected to our WLAN. Devices connected to our wired LAN have no issue connecting to the mac as it is on the same LAN. Devices connected to our WLAN cannot connect to the mac with server.local, although it can connect by entering the servers IP address.
A basic explanation of our network:
Sonicwall has a zone configured for LAN on 192.168.1.X, and has a WLAN zone with 2 VLANs for 2 separate wireless networks, with the wireless network that is trying to connect to the server on 172.31.10.X.
Obviously this is a DNS issue but I just can't seem to find where to fix it. Is it on the server, the client end, or the sonicwall.
does this 'sever' have the ability to be configured as a DNS server? What DNS addresses are being handed out on the WLAN segment (via DHCP I would assume)? Are they the same as the addresses being handed out on the LAN segment? If the two VLANs can communicate I would take a look to make sure everyone has the same DNS info on the LAN and WLAN sides. – Richie086 – 2014-01-07T18:34:53.747
The server can be configured as a DNS server. The same DNS addresses are being handed out to both the LAN and WLAN, and they are external name servers. Maybe what I should try is to configure the server as a DNS and then point the LAN and WLAN to that. – mhammcom – 2014-01-09T15:18:55.943
That's exactly what I was going to suggest that you do. :) – Richie086 – 2014-01-10T17:54:35.127