Link to home
Start Free TrialLog in
Avatar of Dilan77
Dilan77

asked on

Cisco router 803 ping issue

Hi there

I have an old Cisco 803 router and I'd like to backup the IOS to a TFTP server as practise.

I am accessing the router via Hyperterminal console on a PC. A laptop, which I am going to use as the TFTP server, is connected to the e0 interface of the router.

The laptop has been assigned as static IP address of 192.168.1.65/24.  The e0 interface on the router has been assigned an IP address of 192.168.1.66/24, and they are connected via x-over cable.

Strangely, I can ping 192.168.1.66 from the laptop, but cannot ping 192.168.1.65 from the router.

Config posted below>>>

Router1#sh run
no service password-encryption
!
hostname Router1
!
!
!
ip subnet-zero
!
!
!
!
interface Ethernet0
 ip address 192.168.1.66 255.255.255.0
 no ip directed-broadcast
!
interface BRI0

>>> show version below

IOS (tm) C800 Software (C800-G3-MW), Version 12.0(3)T1,  RELEASE SOFTWARE (fc1)

Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 08-Mar-99 15:10 by cmong
Image text-base: 0x000E9000, data-base: 0x0053D000

ROM: TinyROM version 1.2(2)
Router1 uptime is 1 hour, 28 minutes
System restarted by power-on
System image file is "flash:c800-g3-mw.120-3.T1"

Cisco C803 (MPC850) processor (revision 1) with 43512K bytes of virtual memory.
Processor board ID JAD04082OIS
CPU part number 33
Bridging software.
Basic Rate ISDN software, Version 1.1.
1 Ethernet/IEEE 802.3 interface(s)
1 ISDN Basic Rate interface(s)
4M bytes of physical memory (DRAM)
8K bytes of non-volatile configuration memory
8M bytes of flash on board (4M from flash card)

Configuration register is 0x2102

Is there anything glaringly obvious that I'm doing wrong?

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Don Johnston
Don Johnston
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
Avatar of Dilan77
Dilan77

ASKER

Cheers - it was the Windows firewall blocking ICMP.