05-10-2016 10:34 AM - edited 03-08-2019 05:41 AM
Hi all, I have a Cisco switch 3750 with this configuration: on Fast ethernet 0 I have configured this network:
interface FastEthernet0
ip address 10.41.105.198 255.255.255.192
this interface is connected to a remote site (remote site address is 10.41.105.1)
then I have configured:
interface GigabitEthernet1/0/1
switchport access vlan 101
and
interface Vlan101
ip address 45.100.11.1 255.255.255.0
now I have a PC connected to GigabitEthernet1/0/1 and this is the configuration:
IP: 45.100.11.10
Subnet: 255.255.255.0
GW: 45.100.11.1
Now the situation is:
ping from SWITCH 3750 to remote site 10.41.105.1 is OK
ping from PC to 45.100.11.1 (GW) is OK
ping from PC to 10.41.105.198 (FastEthernet0) is OK
ping from PC to remote site 10.41.105.1 is NOT OK (Reply timeout)
why I'm not able to ping remote site on 10.41.105.1 ? I have already tried to set:
ip routing
...
ip route 10.41.105.1 255.255.255.255 FastEthernet0
ip route 45.100.11.0 255.255.255.0 vlan 101
but is still not working and the answer is the same (Reply timeout); please help me.
Thank you.
Solved! Go to Solution.
05-10-2016 12:40 PM
Hi!
Then you should not be able to ping from remote site to 45.100.11.1.
This could be caused by a routing problem in the remote site with no route to 45.100.11.1/24.
Hope it helps, best regards!
JC
05-10-2016 11:09 AM
Hi!
Can you ping to 10.41.105.1 from the switch?
Regards!]
JC
05-10-2016 11:13 AM
Yes ping from SWITCH 3750 console to remote site 10.41.105.1 is OK
05-10-2016 11:19 AM
Hi,
ip route 10.41.105.1 255.255.255.255 FastEthernet0
try this:
ip route 10.41.105.192 255.255.255.192 FastEthernet0
and test again.
HTH
05-10-2016 12:09 PM
No sorry, absolutely not working
05-10-2016 12:01 PM
Hi!
Can you ping 10.41.105.198 from PC?
Regards!
JC
05-10-2016 12:09 PM
Yes, as I reported on my post those are the results:
ping from SWITCH 3750 to remote site 10.41.105.1 is OK
ping from PC to 45.100.11.1 (GW) is OK
ping from PC to 10.41.105.198 (FastEthernet0) is OK
ping from PC to remote site 10.41.105.1 is NOT OK (Reply timeout)
05-10-2016 12:40 PM
Hi!
Then you should not be able to ping from remote site to 45.100.11.1.
This could be caused by a routing problem in the remote site with no route to 45.100.11.1/24.
Hope it helps, best regards!
JC
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide