• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 789
  • Last Modified:

Problems telneting to Cisco 827

I'm having problems telneting to my Cisco 827 using the public IP address (the ATM interface).  I have a fixed IP address assigned by my ISP.

I can telnet to the ethernet interface (192.168.1.1) just fine.  I can ping the WAN ip number from both the inside and outside.  But when I attempt to telnet to the WAN ip number, from either inside or outside, I get a "connection refused" error.

Here is the configuration for my router (with sensitive information blocked):

Current configuration : 1421 bytes
!
version 12.1
no service single-slot-reload-enable
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname CiscoADSL
!
no logging rate-limit
enable secret 5 XXXXXXXXXXXXXXXXXXXXXX
!
ip subnet-zero
no ip finger
!
no ip dhcp-client network-discovery
!
!
!
interface Ethernet0
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
!
interface ATM0
 no ip address
 ip nat outside
 no atm ilmi-keepalive
 pvc 0/100
  encapsulation aal5mux ppp dialer
  dialer pool-member 1
 !
 bundle-enable
 dsl operating-mode auto
 hold-queue 224 in
!
interface Dialer0
 ip address negotiated
 ip nat outside
 encapsulation ppp
 dialer pool 1
 dialer-group 1
 ppp authentication chap callin
 ppp pap sent-username XXXXXXX password 7 XXXXXXXXXXXXXXX
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
no ip http server
!
ip nat inside source list 1 interface Dialer0 overload
ip nat inside source static udp 192.168.1.45 20 XX.XX.97 20 extendable
ip nat inside source static tcp 192.168.1.45 22 XX.XX.97 22 extendable
ip nat inside source static tcp 192.168.1.45 20 XX.XX.97 20 extendable
ip nat inside source static tcp 192.168.1.45 21 12.XX.XX.97 21 extendable
access-list 1 permit 192.168.1.0 0.0.0.255

dialer-list 1 protocol ip permit
!
line con 0
 transport input none
 stopbits 1
line vty 0 4
 password XXXXXXXXX
 login
!
scheduler max-task-time 5000
end



0
netboss1
Asked:
netboss1
  • 2
  • 2
1 Solution
 
ZoidlingCommented:
I think your line 'transport input none' is the issue.  Try changing it to 'transport input telnet'.

0
 
netboss1Author Commented:
Sorry, that didn't solve the problem.  Still can't connect.  Thanks for trying.
0
 
netboss1Author Commented:
I would have never believed it, but rebooting the router solved the problem.  Thanks to Zoidling for his suggestion about the "transport" statement.
0
 
ZoidlingCommented:
Cool.  Glad it worked out for you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now