With lots of lab work with a 2509 and a 2611 with 16 async ports, lately
I've noticed that sometimes "clear line x" isn't enough.

Try "disconnect x" to really kill the line/session.

Kevin Wigle


----- Original Message -----
From: "Brian Lodwick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, February 19, 2001 10:29 AM
Subject: Re: % Connection refused by remote host


> Most likely the issue is with the config on the terminal server. Take a
look
> at the line with "show line" and see if there is a * next to the line you
> have plugged into the firewall. If there is try clearing the line "clear
> line _" then show the line again. If this fixes it, but the issue keeps
> occuring you may want to add "no exec" to the line config.
>
> >>>Brian
>
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: % Connection refused by remote host
> >Date: Mon, 19 Feb 2001 15:28:48 +0100 (MET)
> >
> >Hi,
> >
> >I'm playing with 2511 terminal server and plugged a router and a firewall
> >on
> >the async ports. But when I try to connect to the fire wall with 2001 I
get
> >an error msg  "% Connection refused by remote host", I can ping it and I
> >can
> >telnet to it via cross-over cable!!??.
> >
> >Any device.
> >
> >Regards,
> >
> >Tarry
> >
> >--
> >Sent through GMX FreeMail - http://www.gmx.net
> >
> >_________________________________
> >FAQ, list archives, and subscription info:
> >http://www.groupstudy.com/list/cisco.html
> >Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to