I use the Cisco VPN Client V5.0.07.0440 to connect to remote servers and then run RDS sessions on the servers.
This worked beautifully under 2.32d firmware.
I upgraded my 7800DXL to 2.32e a few days ago. I tried initially restoring the settings file I'd created prior to the firmware update and everything seemed to be working perfectly. Today was the first day I needed to use the VPN and the connection was failing with VPN Client error 412. This error is described at https://waa.ai/vfyR/adc351 and the error box is identical to the one shown on that page.
I then reset up the Billion manually but got the same results.
I then swapped the Billion for the crappy Plusnet router (but it was free!) and the VPN worked perfectly again.
Finally, I reloaded the 2.32d firmware into the Billion and the VPN works perfectly.
It's been a while since I set up the VPN stuff but I'm not conscious of having made any specific Billion settings to make it work. And the Plusnet router in its default state also worked.
So I'm wondering whether there is an issue with the 2.32e firmware, or is there a setting I just can't find at the moment in the new 2.32e firmware that I would need to set in order to make the new firmware support the Cisco VPN client?
As far as I can see I have no exotic or non-standard settings in my working 2.32d setup. Just my isp authentication and wifi settings. (N.b. it's not wifi because I'm using the Cisco VPN software from a wired computer!)
I guess I have a working solution in any case (2.32d) but I thought posting this might either help others avoid the time waste I've had troubleshooting this or would (preferably) provide a solution to making the 2.32e work with Cisco.
Thanks!
Pete
2.32e firmware and Cisco VPN Client V5.0.07.0440
-
- Posts: 35
- Joined: Wed Jun 19, 2013 2:13 pm
-
- Posts: 5398
- Joined: Tue Jul 19, 2011 4:30 pm
Re: 2.32e firmware and Cisco VPN Client V5.0.07.0440
Upgrade back to 2.32e then disable 'ALG >> IPSec' as shown the on the attached screen shot
You can find the ALG/IPSec option under 'Configuration >> NAT >> ALG' once logged into the router
You can find the ALG/IPSec option under 'Configuration >> NAT >> ALG' once logged into the router
You do not have the required permissions to view the files attached to this post.
-
- Posts: 35
- Joined: Wed Jun 19, 2013 2:13 pm
Re: 2.32e firmware and Cisco VPN Client V5.0.07.0440
Brilliant, thank you! I see 2.32d doesn't have that setting. I'll give it a go - many thanks for taking the trouble to respond - appreciated.billion_fan wrote:Upgrade back to 2.32e then disable 'ALG >> IPSec' as shown the on the attached screen shot
You can find the ALG/IPSec option under 'Configuration >> NAT >> ALG' once logged into the router
Cheers,
Pete
-
- Posts: 5398
- Joined: Tue Jul 19, 2011 4:30 pm
Re: 2.32e firmware and Cisco VPN Client V5.0.07.0440
peterb99 wrote:Brilliant, thank you! I see 2.32d doesn't have that setting. I'll give it a go - many thanks for taking the trouble to respond - appreciated.billion_fan wrote:Upgrade back to 2.32e then disable 'ALG >> IPSec' as shown the on the attached screen shot
You can find the ALG/IPSec option under 'Configuration >> NAT >> ALG' once logged into the router
Cheers,
Pete
Let me know how you get on Pete, you should be fine with the setting suggested

-
- Posts: 35
- Joined: Wed Jun 19, 2013 2:13 pm
Re: 2.32e firmware and Cisco VPN Client V5.0.07.0440
Hi there,billion_fan wrote:peterb99 wrote:Brilliant, thank you! I see 2.32d doesn't have that setting. I'll give it a go - many thanks for taking the trouble to respond - appreciated.billion_fan wrote:Upgrade back to 2.32e then disable 'ALG >> IPSec' as shown the on the attached screen shot
You can find the ALG/IPSec option under 'Configuration >> NAT >> ALG' once logged into the router
Cheers,
Pete
Let me know how you get on Pete, you should be fine with the setting suggested
Sorry for the delay in responding - I have been away for a few days.
Yes! You are 100% on the money - disabling IPSec fixed my problem with 2.32e and I am now happily up to date. Many thanks again for taking the trouble to share your knowledge.
All the best,
Pete