2nd problem: The router is on the 192.168.2.x subnet. For it to communicate with the 192.168.1.x subnet, it needs a route.
Main Topics
Browse All TopicsI have two offices (A and B) with Cisco 1811 VPN routers and a configured VPN tunnel.
Office B can ping every resource in office A except for two computers. Both of these computers have two NIC Cards. I've attached a route map of one of these computers.
The following are the settings for one of the computers with multiple NIC's
LAN A: IP address 192.168.2.10, 255.255.255.0, 192.168.2.1 dns 192.168.2.10
LAN B: IP address 192.168.1.10, 255.255.0.0, 192.168.1.10, blank default gateway dns 192.168.1.10
It is LAN A that should be reachable from the tunnel. The router address is 192.168.2.1
I have not given the credentials for the other side of the tunnel. I am certain that my problem resides in my route map and/or ip address selection of LANB. If I disable LANB, my tunnel works.
What should be the IP address of LANB, so that LANA and LANB appear on separate routes. Right now they appear on the same route. I cannot use the route change command. I keep getting a network does not exist error.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Subnet mask is different from subnet.
Currently, they are considered to be on the same subnet, because the subnet mask on 192.168.1.x NIC is incorrect.
Example:
192.168.
Looking at the route table, the 192.168.1.10 NIC has a higher metric for the 192.168.x.x subnets than the 192.168.2.10 NIC. Therefore, the box receives a packet on the 192.168.2.10 NIC, and tries to reply using the 192.168.1.10 NIC.
So, to fix the problem you have to fix the subnet mask for the 192.168.1.10 NIC.
Business Accounts
Answer for Membership
by: asavenerPosted on 2009-01-19 at 08:47:17ID: 23412166
1st problem: 192.168.2.10 255.255.255.0 overlaps 192.168.1.10 255.255.0.0
Each NIC should be on a separate, non-overlapping subnet.
(I suspect the subnet for the 192.168.1.x NIC should be 255.255.255.0).