08-29-2016 09:06 AM - edited 03-08-2019 07:12 AM
I have a clinic across town that I'm connecting to our hospital via Metro-E and I'd like to segment them off. We use a 10.1.0.0/22 scheme for our hospital. I'd like to segment the clinic into a class C using a Cisco 2600. It does hand out DHCP addresses, but the clients are unable to connect/ping to the network/Internet. Could someone help me troubleshoot?
Router config:
!
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname PMG
!
enable secret 5 $1$6jKZ$E1eOuodUjWxV/BUiE.1k9.
!
username offnet password 7 0307521805007518
username PMG password 7 1066480D151A545A
ip subnet-zero
ip cef
!
!
no ip domain lookup
ip dhcp excluded-address 192.168.10.2
!
ip dhcp pool PMG
network 192.168.10.0 255.255.255.192
default-router 192.168.10.1
dns-server 10.1.2.40 10.1.2.56
lease 14
!
!
!
!
!
!
!
!
!
!
!
!
mta receive maximum-recipients 0
!
!
!
!
interface FastEthernet0/0
description WAN_Port
ip address 10.1.1.2 255.255.252.0
duplex auto
speed auto
!
interface FastEthernet0/1
description LAN_port
ip address 192.168.10.1 255.255.255.192
duplex auto
speed auto
!
ip default-gateway 10.1.2.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.2.1
no ip http server
!
!
access-list 1 permit any
!
call rsvp-sync
!
!
mgcp profile default
!
!
!
dial-peer cor custom
!
!
!
!
line con 0
login local
line aux 0
line vty 0 4
login local
!
!
end
Solved! Go to Solution.
08-31-2016 12:31 AM
Hi,
I believe reverse route is missing from other side.
The device which is connected on the fa0/0 should have reverse route to reach 192.168.10.X network.
So in this case you can follow bellow any one of the setps.
1) You need to add the static route "ip route 192.168.10.0 255.255.255.192 10.1.1.2" at the other side of the device.
2) You need to enable the natting (nat on pat) to the interface ip (10.1.1.2).
So the source ip will convert from 192.168.10.X -------> 10.1.1.2. Then when it replies, it will reply to 10.1.1.2 as it knows that the destination is directly connected.
08-29-2016 10:00 AM
Hi
DHCP works fine because the router is acting as DHCP server. To see why users behind router don't get any other access, you need to perform some tests:
Are you able to ping from users behind router these IP addresses:
- 10.1.2.40
- 10.1.2.56
- 10.1.2.1
The router interface f0/0 is connected physically to which device that have which IP address?
Thanks
PS: Please don't forget to rate and mark as correct answer if this answered your question
08-29-2016 11:19 AM
Hello.
f0/0 is plugged into a Catalyst 2960 switch on our network (IP is 10.1.2.103).
f0/1 is plugged into a laptop for testing (received 192.168.10.6).
I cannot ping any of the addresses from the laptop.
I can ping 10.1.1.2 (f0/0) from a different computer on our network.
08-29-2016 11:33 AM
The other end interface connected to your f0/0 is a routed interface or L2 interface?
from your computer behind the router, are you able to ping your f0/0 ip address?
Just to be sure, what is your computer IP address?
From the router, are you able to ping all Ip addresses I said on my previous post by sourcing the ping from interface f0/0?
Thanks
PS: Please don't forget to rate and mark as correct answer if this answered your question
08-29-2016 11:54 AM
f0/0 is plugged into a L2 switch (I am testing this internally before moving it to the clinic).
I can ping f0/0 successfully from the laptop.
The laptop address is 192.168.10.6.
I can ping 10.1.2.1, 10.1.2.40, 10.1.2.56 and 192.168.10.6 from the router (using f0/0 source).
08-29-2016 12:05 PM
Ok do the same ping with f0/1 as source please
08-29-2016 12:08 PM
Ping failed to the addresses when using 192.168.10.1 (f0/1) as a source.
08-30-2016 11:34 PM
Hi,
can you please give us a network desing of your network?
thanks
08-31-2016 04:35 AM
Ok. If the ping sourced from f0/1 doesn't work then it seems to be the route backnto this network not configured on the other end device.
Please add:
ip route 192.168.10.0 255.255.255.192 10.1.1.2
let us know
thanks
PS: Please don't forget to rate and mark as correct answer if this answered your question
08-31-2016 12:31 AM
Hi,
I believe reverse route is missing from other side.
The device which is connected on the fa0/0 should have reverse route to reach 192.168.10.X network.
So in this case you can follow bellow any one of the setps.
1) You need to add the static route "ip route 192.168.10.0 255.255.255.192 10.1.1.2" at the other side of the device.
2) You need to enable the natting (nat on pat) to the interface ip (10.1.1.2).
So the source ip will convert from 192.168.10.X -------> 10.1.1.2. Then when it replies, it will reply to 10.1.1.2 as it knows that the destination is directly connected.
08-31-2016 06:13 AM
Thank you!
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