cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
339
Views
0
Helpful
3
Replies

PC-Switch-Router connection/1st time-newb

coolboarderguy
Level 1
Level 1

Hi All,

this is my 1st time to connect a switch, c1900, to a Router, c2600. Pinging the switch from the PC is successful and vice versa, but, pinging the router is not. I've set the PC IP to 192.168.168.200, Switch = 192.168.168.199. The Routers configs are below, including ping results from the router. Naturally, I used x cable for the switch to router and pc to router, respectively. What am I not doing correctly here..? Cheers.

Router>en

Router#copy startup-conf running-config

Destination filename [running-config]?

909 bytes copied in 1.24 secs (909 bytes/sec)

StatusMark#

00:00:50: %SYS-5-CONFIG: Configured from by show running-conf

Building configuration...

Current configuration:

!

version 12.0

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname StatusMark

!

enable secret xxxx

enable password xxx

!

!

!

!

!

ip subnet-zero

no ip routing

!

!

!

process-max-time 200

!

interface FastEthernet0/0

ip address 192.168.168.1 255.255.255.0

no ip directed-broadcast

no ip route-cache

no ip mroute-cache

shutdown

speed 10

!

interface Serial0/0

no ip address

no ip directed-broadcast

no ip route-cache

no ip mroute-cache

shutdown

!

interface FastEthernet0/1

ip address 192.168.168.2 255.255.255.0

ip directed-broadcast

no ip route-cache

no ip mroute-cache

shutdown

!

interface Serial0/1

no ip address

no ip directed-broadcast

no ip route-cache

no ip mroute-cache

shutdown

!

ip classless

no ip http server

!

!

line con 0

transport input none

line aux 0

line vty 0 4

password xxx

login

!

no scheduler allocate

end

StatusMark#ping 192.168.168.1

Type escape sequence to abort.

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

.....

Success rate is 0 percent (0/5)

StatusMark#ping 192.168.168.2

Type escape sequence to abort.

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

.....

Success rate is 0 percent (0/5)

StatusMark#

FastEthernet0/1 is administratively down, line protocol is down

Hardware is AmdFE, address is 0007.0ec0.3a61 (bia 0007.0ec0.3a61)

Internet address is 192.168.168.2/24

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output never, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

0 packets input, 0 bytes

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast

0 input packets with dribble condition detected

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

3 Replies 3

sevans1979
Level 4
Level 4

Two things that really stick out to me. The "no ip routing" statement in the config and also the fact that both your fastethernet interfaces are shutdown.

For the "no ip routing" fix. Type in "ip routing" in Enable global config mode

StatusMark#conf t

StatusMark(config)#ip routing

Then for the ethernet interfaces. Do the following

StatusMark#conf t

StatusMark(config)#interface fastethernet 0/0

StatusMark(if-config)#no shutdown

and then do the same for interface 0/1

The try your pings again.

Hope this helps..if so please rate this reply.

Scott

Also...Dont forget to save your config.

StatusMark#copy run start

Scott

Kevin Dorrell
Level 10
Level 10

You say "Naturally, I used x cable for the switch to router and pc to router, respectively." I presume you mean switch to router and PC to switch"?

But I think that is actually one of your problems: unless the Cat1900 is different from all the other switches (which it might be, because it is different in other respects as well) the cables should all be straight cables, not crossed. Yes, even the switch to router cable.

The best way to check is show int on your router should say "FastEthernet0/1 is administratively up, line protocol is up." I don't know what the equivalent command is on the Cat1900 (which has a different command set from everthing else), but you should see both ports up.

The other thing I notice is that your F0/0 and F0/1 are on the same subnet, and this is not allowed. You should not be able to bring both up at the same time.

Kevin Dorrell

Luxembourg

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: