jaein.blogg.se

1. #Sonicwall netextender mac how to#
2. #Sonicwall netextender mac mac os#
3. #Sonicwall netextender mac install#
4. #Sonicwall netextender mac software#
5. #Sonicwall netextender mac download#

We are using SonicWall Global VPN Client across the organization for remote connection. If this still does not work you can use the route command in the terminal to force the traffic over the vpn to the gateway on the other side, but it’s easier to do in the net extender’s configuration.Windows vpn client sonicwall The connection so far has proven to be stable and works every time. The way around this is the use a more specific route to get the traffic to the gateway, try adding each server individually to the “Client Routes” section with a /32 mask, this will make the route more specific and it should rate higher in the client’s route table, thereby forcing traffic to that one IP (or collection of individual IPs each with their own /32 mask) out over the vpn tunnel. The reason why this does not work is because the client wont route to the gateway the traffic that it thinks is local. You’re probably using a /24 subnet mask in both locations (meaning the office and the client network) so the address will be 255.255.255.0 on the one route back to the main office. Try adding a “Client Route” under the “NetExtender” section of your Sonic Wall router. The rest of the article will still help you work around the problem though, so good luck! My writing about about double checking this file will have no impact on this particular problem.

#Sonicwall netextender mac mac os#

Update 2: Thomas (see below) pointed out that it doesn’t matter what’s in the nf file as Mac OS 10.6 and higher no longer uses this file to determine DNS servers.

#Sonicwall netextender mac download#

You can download version 5.0.680 here: NetExtender.MacOSX.5.0.680

#Sonicwall netextender mac how to#

Click Here to see how to manually edit a hosts file on a Mac. To circumvent this problem we actually went back to version 5.0.680, and statically configured a hosts file for all of the major resources on the other end of the VPN tunnel.

Update 1: Upon further review, it appears that NetExtender version 5.0.679 breaks the bonjour protocol on the Macs that it is installed on. I’ve attached version 5.0.679 for download if you’re experiencing the same problem. Version 5.0.679 on Mac OS 10.6.5 was what ended up working for me. And Finally I was able to connect again and continue to resolve DNS still. I was able to disconnect and continue to resolve DNS, even better. I was able to connect and resolve DNS, good.

#Sonicwall netextender mac install#

I then rebooted the Mac and was able to install NetExtender version 5.0.679. I was able to bypass this error by performing the following:ĭrop to Command line and enter the following commands: It would not allow me to re-install, stating that a more current version was already installed.

I downloaded the file, removed the current NetExtender and then attempted to re-install the version 5.0.679. I called SonicWall back and after much discussion they recommended that we roll back to version 5.0.679. I flushed the dns cache, I verified the /etc/nf file had the two DNS servers that the NetExtender had placed in there when I connected, and I verified with telnet that a firewall was not blocking DNS to the DNS servers. I verified that I could telnet to port 53 across the tunnel, a NSlookup test proved that I the records I was looking for did exist. I could resolve DNS on my local subnet, and on the internet, but I was unable to resolve anything on the internal DNS servers at the main office that I was connecting to. Now on version 5.0.680 I was unable to resolve DNS on the other end of the VPN tunnel when connected. I thought my problems were over until I re-connected to test that the VPN was still working. I updated the first client and Success! I was able to connect, disconnect, and then continue to resolve DNS.

#Sonicwall netextender mac software#

I updated one of the client Macs to 10.6.5, but still no luck.Ī call to SonicWall ended up with them giving me a new version of the NetExtender software for the Mac, version 5.0.680. I started with a review of the release notes of the SonicWall firmware, which mention a problem with Mac OS prior to version 10.6.5 and NetExtender. I had already updated the endpoint device, a SRA 1200, and the NetExtender was whatever version came with SRA 1200 firmware SonicOS SSL-VPN 4.0.0.3-20sv, which was the most recent firmware available at the time of writing. Once the connection was ended, boom, no DNS resolution. The problem didn’t appear until after the software was connected to a endpoint, and then disconnected. The client computers were able to resolve DNS properly prior to installation. Over the last few days I’ve been running into a problem with Mac OS 10.6 clients and the SonicWall SSL VPN client, NetExtender.