Sonicwall VPN When the user tries to enable the VPN, it just stays at connecting. When you view the Log there is an entry that says "Failed to renew the IP address for the virtual interface" Double-click to get the properties of the connection. Click on the Peers tab, highlight your connection and click Edit. On the NAT Traversal drop-down box, set it to Disabled. On the Interface drop-down box, set it to LAN. OK out of all the menu's. Disable your connections and then enable. |
Solutions to everyday niggles which I find I need to use more then once. Nothing worse then coming across a problem you have fixed before but can't remember how...
Thursday 19 August 2010
Failed to renew the IP address for the virtual interface
Subscribe to:
Post Comments (Atom)
14 comments:
I have had this error and even after using the above fix, it didn't work. It transpired that it was the combination of router and machine. Even though I had other laptops connecting fine on the same site using the same VPN, when I changed the router the problem went away on this particular machine. I suspect that the machine was faulty in some way but didn't have the time to investigate further.
The suggestion worked great!! Thank you very much.
No problem, glad it helped you
Thanks also - similar problem - same error message.
The fix was to reboot my local router.
:)
I cant understand why sonicwall support dont know how to fix this - I get it regularly, from different locations.
Adam
I have to say that thier support with this has been below par. Speaking to them, it sounds like one of those error's they are not really sure how to fix.
I had the same problem but the solutions mentioned above did not work for me. But it encouraged me to play a bit with the settings and I found one which did the trick:
Properties / Peers / Edit / LAN Settings
Here I entered the IP of my router as the first hop: 192.168.1.1
OK'd out and I could connect
Thanks for the inspiration :-)
Thanks for the comment John, always nice to see it helps in some way.
Worth just noting that this DHCP staill will happen if you have an alternate IP that's on the same network as the VPN, or even sometimes a different network's alternate IP on the local adcapter.
This occasionally happens to me when I turn up a Sonicwall and put the 192.168.168.* network on my laptop and then forget to remove it.
I had this error so just typed it in the browser and lo and behold found you and it fixed it. Thanks so much for the public help.
This is because the DHCP is not able to assign an ip address, you can go to your virtual adapter an asign one manually.
This can solve the problem.
But obviously you can know the type of ip you have in the network you can help yourself with the log included in the application to know it.
For me the issue was sorted out when i set the NAT Traversal to Automatic on the SonicWall connection -> Properties -> Peers -> Edit -> NAT Traversal
Win10, same issue.
The only solution: uninstall app, be sure to remove network adapter also. Restart, Reinstall app.
Regarding Windows 10 and reinstalling the GVC, I would try a earlier version. I had this same issue multiple times and everything said in this blog thread is helpful. But, certain versions work better on certain OSs and hardware.
GVC version 4.9.9.1016 kinda sucks... possibly when it comes to older computers.
I have a TZ205 and my Windows 10 (64) laptop is connecting fairly well with GVC version 4.9.4.0306. Version 4.9.9.1016 gave me the DHCP problem. It would work once then never get another ip lease again. I had to reinstall every time.
Hi
Had the same issue here with a TZ190 and a client running windows 10 and GVC 4.9.9.1016
i uninstalled and installed the newer version 4.9.14.0427 and everything started working fine
Post a Comment