Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

New VLan can't access remote network

I created a new vlan (3) (172.18.1.0), but I can't seem to access our remote network. Attached is the routing table from our core switch. I've done an extended ping and the vlan can ping the local router connecting both sites (10.1.1.25), but it can't ping the router @ the remote network (10.2.1.25).

172.17.0.0/16 [1/0] via 10.1.1.25

172.16.0.0/16 is variably subnetted, 4 subnets, 2 masks

172.16.2.4/30 is directly connected, Vlan202

172.16.1.0/24 is directly connected, Vlan200

172.16.2.0/30 is directly connected, Vlan201

172.16.3.0/30 [1/0] via 172.16.2.2

172.18.0.0/24 is subnetted, 1 subnets

172.18.1.0 is directly connected, Vlan3

10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

10.2.1.0/24 [1/0] via 10.1.1.25

10.1.2.0/30 is directly connected, Vlan2

10.2.2.0/24 [1/0] via 10.1.1.25

10.1.1.0/24 is directly connected, Vlan1

10.100.1.0/24 [1/0] via 10.1.2.2

192.168.255.0/30 is subnetted, 1 subnets

192.168.255.0 [1/0] via 10.1.1.25

192.168.0.0/24 is directly connected, Vlan8

192.168.168.0/24 is directly connected, Vlan168

192.168.3.0/24 [1/0] via 10.1.1.25

0.0.0.0/0 [1/0] via 10.1.2.2

any ideas would be great.

3 REPLIES
Purple

Re: New VLan can't access remote network

Do you have to add a static route on the 10.2.1.25 pointing back for this subnet ? I don't see a dynamic routing protocol being used. Check to see if you need one the 10.1.1.25 also.

New Member

Re: New VLan can't access remote network

I bet that is it

New Member

Re: New VLan can't access remote network

That was it, thanks for the help.

329
Views
5
Helpful
3
Replies
CreatePlease login to create content