Hi, sorry for my english.
I have a RV082 configured with 3 account for QuickVPN
LAN RV082 192.168.10.1
At my home I have 2 PC (first 192.168.1.100 and second 192.168.1.101)
at first I have QuickVPN 1.2.6, this connect to RV082 but not see shared Printer and directory.
at second I have QuickVPN 18.104.22.168 but not connect in log: Local IP address conflicts with the subnet of remote VPN Server
at second disinstall 22.214.171.124 and install 1.2.11 but nothing.
can you help me?
Are you trying to use QuickVPN to connect from a home PC to your RV082 at work? If so, what's your home router's model?
Please ensure the ip address of QuickVPN client is not in the same subnet as the LAN IP of RV082. Otherwise the tunnel will not connect.
How is RV082 connected to the internet? Does RV082 see another firewall router in front of it?
Router Alice (Telecon Italia), With 8 IP Static public address, but used only one for RV082 (No firewall)
RV082 is configured: WAN1 with IP static.
This RV082 is connect with another RV082 in VPN tunnel in second office, VPN is OK.
192.168.10.2 Server with 6 directory shared and one printer shared
192.168.10.200 - 209 DHCP
Configured 3 user for VPN Client access and all 3 active.
At my home:
Modem Ericsson HM220DP
ADSL with Dynamic IP
Router USRobotics model: 8000-02
1 PC: 192.168.1.100 - Quick VPN 1.2.6 Connect but not see printer or directory shared
2 PC: 192.168.1.101 - Quick VPN 1.2.11 - Not connect problem with [WARNING]Local IP address conflicts the subnet of remote VPN Server
I don't know if you trying to tunnel or use the vpn client, but the vpn client does not allow netbios to pass thru so you will not see the shared printers and files. If you tunnel between 2 routers it should allow netbios to pass thru, but the quick vpn client does not. Regardless if you want to use tunneling between routers or using the Quick vpn client both ends need to be on separate subnets. I hope it helps.
Not sure the issue you are having but it sounds like the local ip address is the same as the local lan ip address of the remote vpn router. They have to be on different subnets. Example 192.168.1.1 on the remote connection, and 192.168.2.1 on the rv082.
Thanks David Carr,
Office Subnet RV082 is 192.168.10.0 and home is 192.168.1.0
With QuickVPN 1.2.6 on first PC 192.168.1.100 connect
With QuickVPN 1.2.11 on secondo PC 192.168.1.101 Nothing
Hey Davide, I would call into our SBSC and let our support engineers do some troubleshooting and see if they can help your resolve this issue. The number is 866-606-1866.
We do this day in and out here using the RV042. It's a great router except QuickVPN doesn't work. It never has. Use the PPTP server and everything will work fine.
We are having the same issue
RV082 with 2.0 firmeware
Home pc: 192.168.1.x
Error message in the QuickVPN Log file : Local IP address conflicts with the subnet of remote VPN Server
This Both on XP and Vista....
Any help on this issue ?
There is a bug in QuickVPN where it doesn't resolve subnets correctly. I appears to me that it's looking a substrings to determine if the networks conflict instead of really looking at the subnet. In your case, you have an endpoint lan subnet of 192.168.10.x/24 and a source subnet of 192.168.1.x/24. The software is looking at your source subnet string as "192.168.1" and comparing it to the string "192.168.10". Since your destination subnet string starts with the source subnet string then it fails. It's really stupid. You can do change your source subnet to anything but 192.168.1, 192.168.10, and 192.168.100 or change your destination subnet to anything but 192.168.1, 192.168.1x, 192.168.1xx. It's embarrassing that Linksys/Cisco has a lazy programmer that can't do a real subnet check. Even more embarrassing that this bug has been in the software for years.
In my case, my home subnet was 192.168.1.x and I couldn't connect to 192.168.121.x. If I changed my home subnet to 192.168.2.x it would work. If I changed my home subnet to 192.168.12.x it would fail ("192.168.121" starts with "192.168.12"). If I changed my home subnet to 192.168.11.x it would work. Etc.
Yes, it is a known issue with the quickvpn client and as the cisco partner replied the work around is to have the third octect start with something other than a 1 if the other client is using a 1 in the third octect. I apologize for this inconvenience and Cisco is aware of this issue.