Link to home
Start Free TrialLog in
Avatar of Tercestisi
TercestisiFlag for United States of America

asked on

Cannot access ASA 5510 via SSH or Telnet | Syslog shows connection being rejected

I am trying to access the ASA vis SSH or Telnet on interface Ethernet0/0; I cannot figure out why it is being denied as shown by the syslog:

Inbound TCP connection denied from 192.168.1.145/58456 to 192.168.1.9/22 flags SYN  on interface inside
Inbound TCP connection denied from 192.168.1.145/58310 to 192.168.1.9/23 flags SYN  on interface inside

Posted below is my config.
ASA Version 8.0(4)
!
hostname asa
domain-name domain.local
enable password XXXXX encrypted
passwd XXXXX encrypted
names
dns-guard
!
interface Ethernet0/0
 nameif inside
 security-level 0
 ip address 192.168.1.9 255.255.255.0
!
interface Ethernet0/1
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Ethernet0/2
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Ethernet0/3
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Management0/0
 shutdown
 nameif management
 security-level 100
 ip address 10.1.100.2 255.255.255.0
 management-only
!
ftp mode passive
dns server-group DefaultDNS
domain-name domain.local
access-list inside_temp_in extended permit ip any any
access-list inside_temp_out extended permit ip any any
pager lines 24
logging enable
logging asdm informational
mtu management 1500
mtu inside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-615.bin
no asdm history enable
arp timeout 14400
access-group inside_temp_in in interface inside
access-group inside_temp_out out interface inside
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
virtual telnet 192.168.1.9
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh 192.168.1.9 255.255.255.255 inside
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
username admin password XXXXX encrypted
!
class-map inspection_default
 match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
 parameters
  message-length maximum 512
policy-map global_policy
 class inspection_default
  inspect dns migrated_dns_map_1
  inspect ftp
  inspect h323 h225
  inspect h323 ras
  inspect rsh
  inspect rtsp
  inspect esmtp
  inspect sqlnet
  inspect skinny
  inspect sunrpc
  inspect xdmcp
  inspect sip
  inspect netbios
  inspect tftp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum: XXXXX

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland 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
And no one can telnet?
Add the following
telnet 192.168.1.0 255.255.255.0 inside
ssh192.168.1.0 255.255.255.0 inside
Also you might need to run
crypto key generate rsa
 
to generate the certificate before SSH will work.
^^^ this allows management from the entire inside network, to lock it to an individual IP give it the IP and a 32 bit mask
ie
telnet 192.168.1.1 255.255.255.255 inside
ssh192.168.1.1 255.255.255.255 inside  
Avatar of Tercestisi

ASKER

Oh, I thought the ssh command was to define what port on the ASA would accept connections... silly me - thanks!
Hmm... I added the entire 192.168.1.0 network and rebuilt the key but I am getting the same response in my syslog.