CANNOT ACCESS ROUTER THROUGH SSH, TELNET AND WEB UI

[wanumet]

Hi I am failing to access the router through Web UI, SSH and Telnet on both LAN and WAN port

Bellow is the config

Attention!
Authorized Access only.

Yumbe-Hospital>
*Jan 17 15:08:27.991: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: ] [Source: LOCAL] [localport: 0] at 18:08:27 UTC Mon Jan 17 2022
Yumbe-Hospital>en
Password:
Yumbe-Hospital#term len 0
Yumbe-Hospital#sh run
Building configuration...

Current configuration : 7032 bytes
!
! Last configuration change at 17:58:26 UTC Mon Jan 17 2022
!
version 17.3
service timestamps debug datetime msec
service timestamps log datetime msec
service call-home
platform qfp utilization monitor load 80
no platform punt-keepalive disable-kernel-core
platform hardware throughput level 75000
!
hostname Yumbe-Hospital
!
boot-start-marker
boot system flash bootflash:isr4200-universalk9_ias.17.03.03.SPA.bin
boot-end-marker
!
!
enable secret 9 $14$VEUi$63B51/zhnPAjE.$c5G/o5Ol0AKKHXg9RaGS0hGGxQV8GgxLY9TCoZ.6MuM
!
aaa new-model
!
!
!
!
!
!
!
!
aaa session-id common
clock timezone UTC 3 0
!
!
!
!
!
!
!
ip name-server 154.72.192.21 8.8.8.8
ip domain name www.yumbehospital.go.ug
!
!
!
login on-success log
!
!
!
!
!
!
!
subscriber templating
!
!
!
!
!
!
multilink bundle-name authenticated
no device-tracking logging theft
!
!
!
!
!
crypto pki trustpoint TP-self-signed-4009722129
 enrollment selfsigned
 subject-name cn=IOS-Self-Signed-Certificate-4009722129
 revocation-check none
 rsakeypair TP-self-signed-4009722129
!
crypto pki trustpoint SLA-TrustPoint
 enrollment pkcs12
 revocation-check crl
!
!
crypto pki certificate chain TP-self-signed-4009722129
 certificate self-signed 01
  30820330 30820218 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
  31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
  69666963 6174652D 34303039 37323231 3239301E 170D3232 30313134 31333433
  32305A17 0D333030 31303130 30303030 305A3031 312F302D 06035504 03132649
  4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 30303937
  32323132 39308201 22300D06 092A8648 86F70D01 01010500 0382010F 00308201
  0A028201 0100CDD6 EE880F11 C4B004BB 05C98D3C F587F3E7 164DD1F7 308895E1
  989DC1A6 C63CA21E 13812B49 5F97452A 4546864D CB066106 8284C8FF 342042CC
  47B9AB51 4843430F 1B74E4D5 5DCEF687 4427EA79 1F855054 C62315F8 EA5CCE40
  65DFC742 CD1E87CA CEE5D9E8 A53907B7 19D4318B EAAFF902 BAD94256 2550E912
  A0CC576F C6F84614 71B47698 A99D92CA 4E0312F3 2597CD11 C6D987C1 C6ADAA52
  373E08E7 2BBB1197 3D3CFE30 7A9E54D9 10B8EDD8 D5C79D40 8ABA253E FFEA2DFB
  A93AC068 B36A1A1C AA93FF53 367BE8FB 6D96D8FB 6467729C D1AED177 65F765FA
  D726A664 C4826A4E 669F119C B5F03384 B1C35EA0 EA660B71 4FAFD191 8D4303D8
  C3F2E957 7D1F0203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF
  301F0603 551D2304 18301680 148091AE 1AA32EE3 6C0B3DDB 977D9BF5 B1DF63E7
  4E301D06 03551D0E 04160414 8091AE1A A32EE36C 0B3DDB97 7D9BF5B1 DF63E74E
  300D0609 2A864886 F70D0101 05050003 82010100 5609A963 F4730A8A 7130E110
  BD85674A 5D0D1563 1ED7FDFD E994D474 433E47EC 2D10634A 7709096B CA1DD1E8
  571903A2 D06F1D8F 607C54B5 8509333C 209D5E6A B0311419 74243527 B066FC4E
  E3B1E9D2 C1F8284B F31BBC16 D94472BD 866DF8B5 520C44B6 784A3AB6 93926E7E
  76847BD7 F97C9BB3 C2E14595 EB7134E7 120059BC B3E77FC1 BFDFAF85 F1E07FB3
  6C982D14 51EB562A 7BD6AB3A 667E6100 0B10F4E2 755E3945 492D9ACE 80EAB99C
  C3E4545D E8B93BF6 552BF792 A072121F E18DF83B AEF69150 3AD0CB3B DC3EE1F0
  1CE4CBA4 935BA4F0 E8F0D210 CDB58127 37A2B56E 8B8B7CB1 8EF7954F CB738F19
  DF620C47 4971D1A8 AF1B8A03 294F268C 8CA1A2C1
        quit
crypto pki certificate chain SLA-TrustPoint
 certificate ca 01
  30820321 30820209 A0030201 02020101 300D0609 2A864886 F70D0101 0B050030
  32310E30 0C060355 040A1305 43697363 6F312030 1E060355 04031317 43697363
  6F204C69 63656E73 696E6720 526F6F74 20434130 1E170D31 33303533 30313934
  3834375A 170D3338 30353330 31393438 34375A30 32310E30 0C060355 040A1305
  43697363 6F312030 1E060355 04031317 43697363 6F204C69 63656E73 696E6720
  526F6F74 20434130 82012230 0D06092A 864886F7 0D010101 05000382 010F0030
  82010A02 82010100 A6BCBD96 131E05F7 145EA72C 2CD686E6 17222EA1 F1EFF64D
  CBB4C798 212AA147 C655D8D7 9471380D 8711441E 1AAF071A 9CAE6388 8A38E520
  1C394D78 462EF239 C659F715 B98C0A59 5BBB5CBD 0CFEBEA3 700A8BF7 D8F256EE
  4AA4E80D DB6FD1C9 60B1FD18 FFC69C96 6FA68957 A2617DE7 104FDC5F EA2956AC
  7390A3EB 2B5436AD C847A2C5 DAB553EB 69A9A535 58E9F3E3 C0BD23CF 58BD7188
  68E69491 20F320E7 948E71D7 AE3BCC84 F10684C7 4BC8E00F 539BA42B 42C68BB7
  C7479096 B4CB2D62 EA2F505D C7B062A4 6811D95B E8250FC4 5D5D5FB8 8F27D191
  C55F0D76 61F9A4CD 3D992327 A8BB03BD 4E6D7069 7CBADF8B DF5F4368 95135E44
  DFC7C6CF 04DD7FD1 02030100 01A34230 40300E06 03551D0F 0101FF04 04030201
  06300F06 03551D13 0101FF04 05300301 01FF301D 0603551D 0E041604 1449DC85
  4B3D31E5 1B3E6A17 606AF333 3D3B4C73 E8300D06 092A8648 86F70D01 010B0500
  03820101 00507F24 D3932A66 86025D9F E838AE5C 6D4DF6B0 49631C78 240DA905
  604EDCDE FF4FED2B 77FC460E CD636FDB DD44681E 3A5673AB 9093D3B1 6C9E3D8B
  D98987BF E40CBD9E 1AECA0C2 2189BB5C 8FA85686 CD98B646 5575B146 8DFC66A8
  467A3DF4 4D565700 6ADF0F0D CF835015 3C04FF7C 21E878AC 11BA9CD2 55A9232C
  7CA7B7E6 C1AF74F6 152E99B7 B1FCF9BB E973DE7F 5BDDEB86 C71E3B49 1765308B
  5FB0DA06 B92AFE7F 494E8A9E 07B85737 F3A58BE1 1A48A229 C37C1E69 39F08678
  80DDCD16 D6BACECA EEBC7CF9 8428787B 35202CDC 60E4616A B623CDBD 230E3AFB
  418616A9 4093E049 4D10AB75 27E86F73 932E35B5 8862FDAE 0275156F 719BB2F0
  D697DF7F 28
        quit
!
!
no license feature hseck9
license udi pid ISR4221/K9 sn FGL2518LU5C
license accept end user agreement
license boot suite FoundationSuiteK9
license boot level appxk9
memory free low-watermark processor 67153
!
diagnostic bootup level minimal
!
spanning-tree extend system-id
!
username YH secret 9 $14$C7/o$gt6cihTBv2MBkE$He96/Td0WrPE..yM5z0UQ4j3yPhBKVDzT9tb4kJx7wU
!
redundancy
 mode none
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface GigabitEthernet0/0/0
 ip address 172.16.0.1 255.255.254.0
 ip nat inside
 negotiation auto
!
interface GigabitEthernet0/0/0.2
 description vlan 2
 encapsulation dot1Q 2
 ip address 172.16.2.1 255.255.255.0
 ip nat inside
!
interface GigabitEthernet0/0/1
 ip address 154.72.215.230 255.255.255.252
 ip nat outside
 media-type rj45
 negotiation auto
!
ip http server
ip http port 8080
ip http authentication local
ip http secure-server
ip http secure-port 8081
ip forward-protocol nd
ip nat inside source static tcp 172.16.0.254 80 154.72.215.230 80 extendable
ip nat inside source list 1 interface GigabitEthernet0/0/1 overload
ip route 0.0.0.0 0.0.0.0 154.72.215.229
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/1
!
!
ip access-list extended Web_acl
 10 permit ip any any
!
ip access-list standard 1
 10 permit 172.16.0.0 0.0.1.255
!
!
!
!
!
!
control-plane
!
banner login ^C
Welcome!
YUMBE HOSPITAL^C
banner motd ^C
Attention!
Authorized Access only.
^C
!
line con 0
 password MyBDis317
 transport input none
 stopbits 1
line aux 0
 stopbits 1
line vty 0 4
 password MyBDis317
 transport input ssh
!
call-home
 ! If contact email address in call-home is configured as sch-smart-licensing@cisco.com
 ! the email address configured in Cisco Smart License Portal will be used as contact email address to send SCH notifications.
 contact-email-addr sch-smart-licensing@cisco.com
 profile "CiscoTAC-1"
  active
  destination transport-method http
ntp server time.google.com prefer
!
!
!
!
!
!
end

[marce1000]

 - This seems to be a fully configured device. Is this a new/recent problem or was the problem  there since 'eternity' ?

 M.

[wanumet]

it is a new problem. I reset the router and with the new config am facing this problem

[marce1000]

 - Try to track what was changed and revert back. it is always advisable to work in steps. If needed and there is an externally saved config, factory reset, configure initial setup and restore a config that was working.

 M.

[Flavio Miranda]

Hi

 To get helped you need to provide more then this.  Can you even ping this router from another device?  If you dont, you may need to fix connectivity first. If you can ping it but you have no access, then, we can thing something else.

 Make sure you dont have a firewall in between.

[balaji.bandi]

From what device you trying to access ?where is this Router connected ? switch ?

From the device you trying access this Router? what is the IP address ? can you able to ping the Router ?

interface GigabitEthernet0/0/0
 ip address 172.16.0.1 255.255.254.0
 ip nat inside
 negotiation auto
!
interface GigabitEthernet0/0/0.2
 description vlan 2
 encapsulation dot1Q 2
 ip address 172.16.2.1 255.255.255.0
 ip nat inside
!

is this was working config before ?