Acess Server issues

I just installed an NM-16A in my 2620 and configured it as an access-server. Problem is, it doesnt work.

Here's the config [I find it wierd that it is lines 33 48]:

line 33 48
exec-timeout 0 0
logging synchronous
transport input telnet
flowcontrol hardware

Loopback interface is configured as well:

interface Loopback0
ip address 172.10.10.1 255.255.255.255

The host entry is:

ip host R1 2001 172.10.10.1

Every time I try and connect I get this:
AccessServer#R1
Trying R1 (172.10.10.1, 2001)...
% Connection refused by remote host

Any ideas? I've been googling for hours and have gotten no where.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

tiersten

It isn't port 2001 since your lines start at 33. It is 33 because the NM is in slot 1.

phantasm

tiersten wrote: »

It isn't port 2001 since your lines start at 33. It is 33 because it is slot 1.

Explain please? I thought it was always 200 then the cable number.

tiersten

phantasm wrote: »

Explain please? I thought it was always 200 then the cable number.

No. It is done by the line number. What line number gets assigned is based on what slot it is in. If you have a 3640 which has multiple NM slots, how would you tell it which line you wanted if you put multiple NM-32As into it?

show line
show diag

phantasm

tiersten wrote: »

No. It is done by the line number. What line number gets assigned is based on what slot it is in. If you have a 3640 which has multiple NM slots, how would you tell it which line you wanted if you put multiple NM-32As into it?

show line
show diag

So what is the correct line number then? 3301?

tiersten

phantasm wrote: »

So what is the correct line number then? 3301?

2000 + line number

phantasm

tiersten wrote: »

2000 + line number

I'm not getting it. I've tried 2033, 2034, 2035 and still get the same message.

tiersten

phantasm wrote: »

I'm not getting it. I've tried 2033, 2034, 2035 and still get the same message.

Paste the output of "show line"

phantasm

tiersten wrote: »

Paste the output of "show line"

AccessServer#sh line
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
0 CTY - - - - - 1 0 0/0 -
* 33 TTY 9600/9600 - - - - - 0 30 0/0 -
* 34 TTY 9600/9600 - - - - - 0 0 0/0 -
35 TTY 9600/9600 - - - - - 0 0 0/0 -
36 TTY 9600/9600 - - - - - 0 0 0/0 -
37 TTY 9600/9600 - - - - - 0 0 0/0 -
38 TTY 9600/9600 - - - - - 0 0 0/0 -
39 TTY 9600/9600 - - - - - 0 0 0/0 -
40 TTY 9600/9600 - - - - - 0 0 0/0 -
41 TTY 9600/9600 - - - - - 0 0 0/0 -
42 TTY 9600/9600 - - - - - 0 0 0/0 -
43 TTY 9600/9600 - - - - - 0 0 0/0 -
44 TTY 9600/9600 - - - - - 0 0 0/0 -
45 TTY 9600/9600 - - - - - 0 0 0/0 -
46 TTY 9600/9600 - - - - - 0 0 0/0 -
47 TTY 9600/9600 - - - - - 0 0 0/0 -
48 TTY 9600/9600 - - - - - 0 0 0/0 -
65 AUX 9600/9600 - - - - - 0 0 0/0 -
* 66 VTY - - - - - 3 0 0/0 -
67 VTY - - - - - 0 0 0/0 -
68 VTY - - - - - 0 0 0/0 -
69 VTY - - - - - 0 0 0/0 -
70 VTY - - - - - 0 0 0/0 -

Line(s) not in async mode -or- with no hardware support:
1-32, 49-64

tiersten

clear line 33
clear line 34

You should be able to just telnet to 2033 on your access server from another machine BTW. You don't need to connect first and then tell it what you want.

phantasm

Those commands cleared ok but I still can't connect.

tiersten

Post the rest of your config

phantasm

I can telnet to 2034 which is another router. Butr 2033 is still a no go.

version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname AccessServer
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$ryCW$o5GjayM0lr1xTsCb01TYt1
!
memory-size iomem 15
no aaa new-model
ip subnet-zero
ip cef
!
!
ip host R1 2033 172.10.10.1
ip host R2 2034 172.10.10.1
!
ip audit po max-events 100
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 172.10.10.1 255.255.255.255
!
interface FastEthernet0/0
ip address 192.168.0.5 255.255.255.0
duplex auto
speed auto
!
ip http server
no ip http secure-server
ip classless
!
!
!
!
!
!
!
!
line con 0
logging synchronous
line 33 48
exec-timeout 0 0
logging synchronous
transport input telnet
flowcontrol hardware
line aux 0
line vty 0 4
password cisco
login
!
!
end

tiersten

Your config looks okay to me at first glance apart from one thing. Why have you enabled flowcontrol?

phantasm

One of the config sights I was reading mentioned enabling it... I didn't understand why either but I did. Is it not needed?

At this point I'm thinking it's that cable as every other one works fine.

phantasm

Quick question. I know the 2610 only has an ethernet port while the 2620 has a fast ethernet port. Since the Access Server connects up to the network would it be best to use the 2620 with the NM-16A? Right now the 2610 is configured as the access server and I notice it is a bit punchy on the CLI.

Also, T1 cards; they show up as another serial interface?

mamono

I don't believe that telnet and SSH traffic will carry enough bandwidth to warrant fast ethernet. If you use an NM-8A/S as a frame relay switch, you'll want to use the 2620 for that, IMHO. Keep the NM-16A into the 2610, that's probably the better choice.

jason_lunde

do a "transport input all" on your console port

mikej412

phantasm wrote: »

line 33 48
exec-timeout 0 0
logging synchronous
transport input telnet
flowcontrol hardware

add a no exec to your configuration.

I just do a transport input all on my terminal server -- and don't have any flow control defined.

You may just want to initially use the resume command until you get a hang of the short cuts when you CTRL^x back to the access server. I usually just use the connection # or just the enter key to return to the last open connection.