Link to home
Start Free TrialLog in
Avatar of samjud
samjud

asked on

Cisco 2600 - Can't ping routers own IP address

I have a new Cisco 2600
I've configured FastEthernet0/0 with correct IP address and mask.
I can't even ping the address I've assigned it, forget about pinging anything outside.
What may I be doing wrong?
Thanks
Avatar of yasirirfan
yasirirfan
Flag of Saudi Arabia image

what about the interface is it shutdown or not
interface fastethernet 0/0
ip address 10.0.0.1 255.255.255.0
no shutdown
exit

Cheers

Yasir
Avatar of samjud
samjud

ASKER

Protocol is up and line is up
Thanks, I was aware of that,
no go. I also for the heck of it reloaded the router.
Avatar of samjud

ASKER

Router#sh int fast0/0
FastEthernet0/0 is up, line protocol is up
  Hardware is AmdFE, address is 0011.923d.da80 (bia 0011.923d.da80)
  Internet address is x.x.x.x/30
  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)
  Full-duplex, 100Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:27, output 00:00:07, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     195 packets input, 11700 bytes
     Received 195 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog
     0 input packets with dribble condition detected
     685 packets output, 72211 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 babbles, 0 late collision, 0 deferred
     6 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
Avatar of Don Johnston
How long was the router up when you issued the "show interface" command above?

6 lost carriers, 3 interface resets.

If these stats were accumulated over a couple minutes, that would be a good starting point.
Avatar of samjud

ASKER

It has not been up too long at all. I rebooted it within the past hour or so.
The Interface i did a shut and no shut even more recently then that.
I would start with a different cable and see what happens.
Avatar of samjud

ASKER

OK I'll try, but shouldn't I be able to ping from the router the IP I assigned to the router? Even if the cable is bad?
Avatar of samjud

ASKER

Thanks for all the help but I got from the T1 company bad IP information. I got the correct info, and all is working as advertised.
That's a neat trick. Ethernet to T-1.

:-)
Avatar of samjud

ASKER

Is there something wrong with that?
>Is there something wrong with that?

Only that it's impossible to connect an ethernet port to a T-1 line.
cisco routers have by default an ACL permiting only 10.10.10.xx networks assigned on the ethrnet interface. It usually has number 23.Check your config to see if this acl is applied to your incoming port. You can see that form show run command , check if acce
>cisco routers have by default an ACL permiting only 10.10.10.xx networks assigned on the ethrnet interface. It usually has number 23.Check your config to see if this acl is applied to your incoming port. You can see that form show run command , check if acce

Cisco routers have NO access-lists by default.
Want to bet donjohnston????? Check a new one!!

Three days ago I set up a new 2821 and it had that access list exactly as I describe to you!!
Also they have a default ip address of 10.10.10.1 on their network interface
Not really. I am talking about the default conf of a new router. It has a DHCP enabled with a lease up to 10.10.10.7 and an ACL permitting hosts only from this range. As I told I had this problem a few days ago. I've log from console , change the ip and no shut the network interface and also gave the comands login local and password on the vty interfaces. When I tried to connect I had no reply as my network was on a 192.168.1.xx subnet. I've checked the configuration and I 've seen the acl we are talking about.

When I turned off the acl everything worked fine. Please check it when you have a new router.
ASKER CERTIFIED SOLUTION
Avatar of Computer101
Computer101
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial