Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem pinging across the network

Status
Not open for further replies.

Sniffer2112

IS-IT--Management
Mar 10, 2009
67
US
**I'm trying to get computerA to be able to ping computerB**

Set up:
computerA - switchA - routerA - routerC - routerB - switchB - computerB

Each switch has a Vlan set up... vlanA...vlanB

The three routers are connected via serial WIC-1Ts. I do have static routing on each router for all networks.

If I am on routerA, I can ping all the way to vlanB and computerB.
If I am on routerB, I can ping all the way to vlanA but not computerA.
If I am on computerA, I can ping to routerA(gateway) but can not ping to the serial IP address that goes to routerC.

My thought is that somewhere in switchA there is the issue.

switchA is connected at FA0/7(computerA) and at FA0/24(routerA).
By doing switchA#show ip interface brief....
Interface IP Address OK? Method Status Protocol
FA 0/7 unassigned YES unsent up up
FA 0/24 unassigned YES unsent up up

I'm guessing that it's the IP address being "unassigned". I'm still very new to this but quickly learning.

If you need more information, just let me know and I'll post it.
 
what are your lan and wan ip's?

Do you have a static route on both routers example:
RTR_A(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.1 <--next hop

RTR_B(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.2

The LAN can be something like this
RTR_A---192.168.2.1 255.255.255.0
PC 192.168.2.2 255.255.255.0 GW 192.168.2.1

RTR_B ---192.168.3.1 255.255.255.0
PC_B 192.168.3.2 255.255.255.0 GW 192.168.3.1



[americanflag] Go Army!
Tek-TIP Member 19,650
 
My vlanA is 10.8.4.6/23 and vlanB is 10.8.10.6/23

Wans are 10.8.4.0 / 10.8.6.0 / 10.8.8.0 / 10.8.10.0 each with a 255.255.254.0 subnet

Static routes are on each router.
routerA can ping all the way to routerB and vice versa. So I think that would mean that all the static routes work. I do have each router set up that to reach each network, it points to the first hop in that direction.

computerA has an ip address of 10.8.4.100/23 with the gateway as 10.8.4.1(routerA FA port)

computerB has an ip address of 10.8.10.100/23 with the gateway as 10.8.10.1 (routerB FA port)

Does anything in the Switch ip interface brief show anything that could be the problem? Like why the routers can ping across the network but when I try from a computer, I get stopped at the default gateway.

I should mention (just noticed this) that computerA has a DNS of 192.168.1.68 which was something I had going on with my real internet connection. Not sure if that would cause this issue.
 
I should mention (just noticed this) that computerA has a DNS of 192.168.1.68 which was something I had going on with my real internet connection. Not sure if that would cause this issue."
nope, not in this case

"My vlanA is 10.8.4.6/23 and vlanB is 10.8.10.6/23"

that are host addresses
what shows swA#sh vlan

can u post the running config of swA pls.
what default gateway is set on swA?

why did u set the wan subnets to 255.255.254.0 (255.255.255.252 would do the job)

M. Knorr

MCSE, MCTS, MCSA, CCNA
 
You might want to give a traceroute output from workstation a to workstation b.
 
Couple things for you. From router B, do an extended ping, and choose the WAN connection as the source interface. Then try it again with your LAN connection as the source interface?

How about from router C, can you ping the LAN side of both routers B and A? Again try the extended pings so you can "force" the source interfaces.

You may want to consider downsizing your design too...remove router C and put router B and A back to back. See if you can make that work first, then add in router C.

Also if you can post your static routes for each router would help.
 
Thank you for your replies everyone!

To Lemon13: I used 255.255.254.0 subnet just because I was told that Cisco recommended no more than 500 users per subnet and that subnet allowed for that. Other than that, there was no other reason. I'll post my swA#sh vlan and the running-config too at the end of this post.
Thanks for answering my DNS though. I didn't think it would matter but then I am not that familiar with DNS yet.

My vlanA is 10.8.4.6/23 and the host computer: 10.8.4.88/23
My vlanB is 10.8.10.6/23 and the host computer: 10.8.10.100/23

Thanks Lerdalt. Completely forgot about the traceroute command. I'll give that a try.

Here is my swA#sh vlan
switchA#show vlan

VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
Fa0/21, Fa0/22, Fa0/23, Fa0/24
Gi0/1, Gi0/2
10 VLAN0010 active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
10 enet 100010 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0

Remote SPAN VLANs
------------------------------------------------------------------------------


Primary Secondary Type Ports
------- --------- ----------------- ------------------------------------------

switchA#show run
Current configuration : 2370 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname switchA
!
enable secret 5 $******.
enable password ******
!
clock timezone CST -5
clock summer-time CDT recurring
ip subnet-zero
no ip domain-lookup
!
!
spanning-tree mode pvst
spanning-tree extend system-id

!
interface FastEthernet0/7
no ip address
duplex full
speed 100
!
interface FastEthernet0/24
no ip address
duplex full
speed 100
!
interface GigabitEthernet0/1
no ip address
!
interface GigabitEthernet0/2
no ip address
!
interface Vlan1
ip address 10.8.4.6 255.255.254.0
!
ip default-gateway 10.8.4.1
ip classless
ip http server
!
!
!
line con 0
exec-timeout 30 0
password ******
login
line vty 0 4
exec-timeout 30 0
password ******
login
line vty 5 15
password ******
login
!
end

Note--- I took out most of the FA #/# interfaces to save space. I have computerA(10.8.4.88/23) connected to FA0/7 and routerA (10.8.4.1/23 FA port) connected to port FA0/24 on the switch.
 
I see why i can't ping across the network...
Here is my tracert to routerC (10.8.6.2) which is the first stop across the network..

C:\>tracert 10.8.6.2

Tracing route to 10.8.6.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.

I do have my home internet (192...) hooked up to this computer as well.
 
Where did you source your traceroute from? ComputerA or computerB?
 
ok..gotcha. I'm betting if you did a route print on computer a, you will see that the default gateway is out the internet, and that you only have a route for 10.8.4.0/23.

2 options:
1.) unplug the internet connection and see if it works.
2.) create a static route in windows for the 10.8.0.0/16 network to go out your local 10.8.4.x interface.

 
This is the #show run for routerA

Current configuration : 1551 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname routerA
!
boot-start-marker
boot-end-marker
!
enable secret 5 ********
enable password ********
!
no aaa new-model
memory-size iomem 15
clock timezone CST -5
clock summer-time CDT recurring
no network-clock-participate slot 1
no network-clock-participate wic 0
ip cef
!
no ip domain lookup
ip domain name camarilla.local
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
interface FastEthernet0/0
description LAN PORT TO switchA
ip address 10.8.4.1 255.255.254.0
speed 100
full-duplex
!
interface Serial0/0
description Serial to routerC
ip address 10.8.6.1 255.255.254.0
encapsulation ppp
!
router rip
version 2
network 10.0.0.0
!
ip forward-protocol nd
ip route 10.8.8.0 255.255.254.0 10.8.6.2
ip route 10.8.10.0 255.255.254.0 10.8.6.2
!
!
no ip http server
no ip http secure-server
!
control-plane
!
!
dial-peer cor custom
!
line con 0
exec-timeout 30 0
password ********
logging synchronous
login
line aux 0
line vty 0 4
exec-timeout 30 0
password ********
logging synchronous
login
!
!
end

routerA#
 
RIP may be auto-summarizing at the boundaries as a 16 bit mask, or even an 8 bit mask. Also, why the 23 bit mask in the static routes?

Burt
 
In one post you show Computer A's default gateway as 192.168.1.254 yet the Router A ethernet interface is configured as 10.8.4.1? What am I missing?
 
I did disconnect the cable to my home netowrk (192...) and now I am able to ping across the network (test lab).

computerA has two LAN connections. One was going to my test lab (10....) and the other was connected to my home internet (192....)

Burtsbee, I used the 23 bit mask only because I read that Cisco recommends no more than 500 users per network. And the 23 bit subnet mask allows for that. Other than that, no other reason. Is there a reason why a 23 bit mask is odd? You are the second person to mention that. I don't mean to sound rude or anything. Just curious and always eager to learn more.

Thanks everyone for responding!!
 
i go with lerdalt tip, set the default gateway on computerA to
10.8.4.1 255.255.254.0 and it should work.

this looks like a lab setup, what do u wanne achieve


M. Knorr

MCSE, MCTS, MCSA, CCNA
 
Actually I don't like having more that 150+ hosts on a single network segment. You can't have 2 default gateways on a windows box and expect it to work correctly.
 
Lemon13, yes, this is a lab set up. Going for my CCNA. My first post shows the lab set up. I was trying to be able to ping from one computer to the other across a WAN set up.

Brianinms, didn't know about the gateway thing. The only reason why I had computerA hooked up to my home internet was to be able to go out to the web and do some research and post here on tek-tips. I'm still on the look out for a NW-1E card so I can hook up one of the routers to home internet but that's not as important right now.

In the mean time I can just unhook the cable to my home internet and keep my test lab isolated.
 
from the show vlan output computerA is in vlan 1 (default), if the lab is for vlan u missed several things in ur configs

good luck with ur ccna

M. Knorr

MCSE, MCTS, MCSA, CCNA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top