able to ping server from user gateway but user is not able to ping server

[mahesh18]

hi all,

i have a problem here.

user is on vlan140 with ip address.

user is unable to ping server from his pc.

i am able toping server from user gateway.but when i do extended ping using source ip as user vlan then ping does not work

any help

[mahesh18]

hi jon i did that what u said above

log on to each router.

from last router 172.31.51.9 i was unable to ping vlan140

ping 192.168.140.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.3, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

this router is server gateway.

what should i do on this router

[mahesh18]

Hi john,

also from server--gateway router 172.31.51.9

i am able to ping user gateway and IP address

and also vlan 140 now but from user gateway still same thing

ping 192.168.140.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.3, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms

txhoucorr1#exit

[Connection to 172.16.100.2 closed by foreign host]

oktulesfr2#ping

Protocol [ip]:

Target IP address: 172.31.41.82

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan140

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.31.41.82, timeout is 2 seconds:

Packet sent with a source address of 192.168.140.3

.....

Success rate is 0 percent (0/5)

[Jon Marshall]

Try using an extended ping with vlan 140 as the source IP address and ping each of the hops in your traceroute above. When the ping fails that is where the routing needs to be sorted out.

Jon

[mahesh18]

ok let me check

thanks

[mahesh18]

hi jon thi sresult

oktulesfr2#ping

Protocol [ip]:

Target IP address: 192.168.253.13

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan140

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.253.13, timeout is 2 seconds:

Packet sent with a source address of 192.168.140.3

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

oktulesfr2#ping

Protocol [ip]:

Target IP address: 172.16.128.9

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan140

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.128.9, timeout is 2 seconds:

Packet sent with a source address of 192.168.140.3

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

oktulesfr2#ping

Protocol [ip]:

Target IP address: 172.16.100.2

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan140

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.100.2, timeout is 2 seconds:

Packet sent with a source address of 192.168.140.3

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16 ms

oktulesfr2#

oktulesfr2#ping

Protocol [ip]:

Target IP address: 172.16.51.9

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan140

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.51.9, timeout is 2 seconds:

Packet sent with a source address of 192.168.140.3

.....

Success rate is 0 percent (0/5)

ping does not work to server gateway ip

[JORGE RODRIGUEZ]

Is this problem on a single user on that vlan 40, can other users on that same vlan able to reach the server? if only one user make sure tcpip settings are properly configured with right gateway and mask, it is possibly the user do not have proper IP settings configured, could you check that.

Rgds

-Jorge

[mahesh18]

Hi all,

also from user gateway i am able toping user IP address

ping 192.168.140.6

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.6, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

[mahesh18]

Hi Jorge,

so far we know all users on vlan 140 can not access otehr users on different vlan can access the server

[JORGE RODRIGUEZ]

I walked away for 5 minutes and see this developement, I'll let Jon take over, but prety much your trace route from vlan140 dies

@ 172.16.128.9, there you would need to check that there is a route back as Jon indicated to network 192.l168.140.0/24 VLAN140, connect to that 172.16.128.9 router and do show ip route 192.168.140.0 to see if it is in routing table.

One thing to take note, is this something that just broke or was it working before?

1 [192.168.140.3]

2 [192.168.253.5]

3 [172.16.128.9] ( check here )

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

Rgds

-Jorge

[mahesh18]

Hi jorge

i logonto router 172.16.128.9 and did

show ip route 192.168.140.0

Routing entry for 192.168.140.0/24

Known via "eigrp 64555", distance 170, metric 3328, type external

Redistributing via eigrp 64555

Last update from 172.16.128.14 on Port-channel14, 1w3d ago

Routing Descriptor Blocks:

* 172.16.128.10, from 172.16.128.10, 1w3d ago, via Port-channel13

Route metric is 3328, traffic share count is 1

Total delay is 30 microseconds, minimum bandwidth is 1000000 Kbit

Reliability 255/255, minimum MTU 1500 bytes

Loading 7/255, Hops 2

172.16.128.14, from 172.16.128.14, 1w3d ago, via Port-channel14

Route metric is 3328, traffic share count is 1

Total delay is 30 microseconds, minimum bandwidth is 1000000 Kbit

Reliability 255/255, minimum MTU 1500 bytes

Loading 13/255, Hops 2

[JORGE RODRIGUEZ]

issue on that same router show ip route for the server IP address as well or ping the server IP address from it.

[mahesh18]

Sorry for last post

i am stil inable to ping from server gateway to user vlan140 or user gateway ip

txhoudisr1#ping 192.168.140.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.1, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

txhoudisr1#ping 192.168.140.6

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.6, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

txhoudisr1#ping 192.168.140.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.140.3, timeout is 2 seconds:

..

[JORGE RODRIGUEZ]

From the server gateway where 172.31.51.9 resides could be where the problem is, that router doesn't know how to get to 192.168.140 network.

Do you have any other vlans beside VLAN 140 that you can try pinging from the server gateway, if you can ping from the server gateway any other VLANS residing in core/switch where VLAN140 is, find out how by what method the server gateway is learning those routes if by static routes or dynamic etc...