cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
2125
Views
0
Helpful
20
Replies

1700 does not route

james.curran
Level 1
Level 1


Having trouble with a 1700 routing in production.

In the initial test bed I had a Desktop set at 192.9.100.250  connected to port4 of the layer 2 switch on the 1700. The Vlan1 of the switch is set at 192.9.100.194.

The FastEthernet0 port of the router is set at 156.52.42.194 and was connected to a desktop set at 156.52.42.10.

I could ping from the 192.9.100.250 desktop to the 156.52.42.10 desktop across the router without problem. Ping in the other direction also worked.

Note:  System does not need internet access. It is an internal router only. Connection bridges from an 0vation swtch 192.x.x.x to a Hirschman Ethernet switch .152.x.x.x

When placed into production it looks like this

Hirschman Ethernet Switch 156.9.52.42.10 --->media converter---->| 1700 Router FastEthernet0 (156.52.42.194) <==> Vlan1 port 4 (192.9.100.194) | -------> Cisco 2820 (192.9.100.117 concentrator ---> Cisco Bridge PCC Ovation 192.9.100.250

From the switch (Hyperterminal)  I can ping in either direction. From the Hirschman (156.x.x.x) I can ping to the FE0 Side but not to Port 4 of the interior switch (192.9.100.194).

I started to set up NAT in the Lab but since I was successful without using it left the inside/Outside statements off.

using ping 192.9.100.194 source 156.52.42.194 is successful

using ping 156.52.42.194 source 192.9.100.194 is successful.

Ping either direction from the outside returns only reachs the associated port on the router ether Port4 vlan or FE0 but does not continue to the other side.

Any assistance would be appreciated. Router is located in a remote location (Incinerator) so trips to it are difficult.

20 Replies 20

Thats because it came out in the late 90's! (which is why I rememebered it)

VLAN1 has an ip on the 1700, but its not associated with any phyiscal interface.

Fastethernet1,2,3,4 ports are assigned to VLAN1 The ip assigned to the VLAN1 is 192.9.100.194/24

The ports are layer two so no IP can be assigned to them  (drats)

FE0 has been assigned 152.52.42.194/24 which goes thru a media converter to connecto to 152.52.42.194

I built a lab before installing into production

192.9.100.250 (Desktop) -----> | 192.9.100.194 vlan1 port 4 <===> 152.52.42.194  FE0 |  152.52.42.10 (Desktop

                                                                           ( Cisco 1711 )

I could ping from desktop to desktop in either direction.  This does not work in production.  When logged to the 1711 you can ping in both directions without an issue.  You can also ping out to each segment.

ping 192.9.100.44 source 192.9.100.194 works

ping 192.9.100.44 source 152.52.42.194 is a no go

same for reverse direction.

I made an error

ping 192.9.100.44 source 192.9.100.194 works

ping 192.9.100.44 source 156.52.42.194 is a not correct

should be

ping 152.52.42.194 source 192.9.100.194 works

ping 192.9.100.194 source 156.52.42.194 works

Ping 152.52.42.10 from 192.9.100.194 does not work

ping 192.9.100.194 from 156.52.42.10 does not work

check your static routes. is .0 really the next hop?

ever thought of a dynamic protocol for this/ RIPII would be pretty easy

Tried RIP but no gold.

router rip

network 152.52.42.0

network 192.9.100.0

still could not see other side.  ping 192.9.100.250 source 156.52.42.194 unsuccessful

Review Cisco Networking for a $25 gift card