Re: OT: telnet to a router from anywhere - wireless!!! [7:22218]

2001-10-05 Thread Patrick Ramsey

I couldn't imagine using one of thosepalm tops are bad enough...and my
typing skills do not help the matter.  It would take me 5 minutes to type in
one command!  :)

>>> "Brad Ellis"  10/04/01 11:06PM >>>
Fellow geeks need to check this out, it just looks too cool (wireless telnet
access):

http://www.airstreamws.com/ourproducts/sshtelnet.html 

I just bought a RIM 957, so I'll let everyone know how well it works.

thanks,
-Brad Ellis
CCIE#5796
Network Learning Inc
[EMAIL PROTECTED] 
used Cisco:  www.optsys.net




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=22218&t=22218
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



OT: telnet to a router from anywhere - wireless!!! [7:22166]

2001-10-04 Thread Brad Ellis

Fellow geeks need to check this out, it just looks too cool (wireless telnet
access):

http://www.airstreamws.com/ourproducts/sshtelnet.html

I just bought a RIM 957, so I'll let everyone know how well it works.

thanks,
-Brad Ellis
CCIE#5796
Network Learning Inc
[EMAIL PROTECTED]
used Cisco:  www.optsys.net




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=22166&t=22166
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Telnet to a Router

2001-03-05 Thread Kevin Wigle

h, I have 2 BEFSR41s (one for adsl and one for cable) and all port
forwarding works ok also.

You say that you can remotely access an NT server. I take it that is by
Telnet?

So, then you also try to telnet the router?  I'm wondering if you're allowed
to have a single port (port 23) forwarded to different inside
addresses. which is what it sounds like you're trying to do.

Define only one end address for port 23 (the router) and try that.

For all my port forwarding I have only one destination for each defined
port/range.

Kevin Wigle

- Original Message -
From: "Mark Rose" <[EMAIL PROTECTED]>
To: "Cisco@Groupstudy. Com (E-mail)" <[EMAIL PROTECTED]>
Sent: Monday, 05 March, 2001 12:28
Subject: Telnet to a Router


>
> I am trying to telnet to a 2514 router from work. I have a Linksys BEFSR41
> ethernet/dsl router on my incoming cable line. I have enabled port
> forwarding for telnet (port 23) on this router. I have also set up vty on
> the 2514. When I try to telnet to the wan interface of the Linksys
forwarded
> to the ethernet interface on the 2514 I get the message "Could not open a
> connection to host: Connection failed". But if I remote access an NT
server
> inside my home net (on internal address space), from there I can telnet
(on
> the private address space) to the same ethernet interface and connect.
>
> Since I can remote access my NT box, port forwarding on the Linksys router
> is working. Also the 2514 should be set properly since I can telnet in
from
> within my lan. I must be overlooking something but I cannot figure it out.
>
> I would appreciate any ideas or assistance.
>
> TIA
> Mark
>
>
>
> _
> 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]



RE: Telnet to a Router

2001-03-05 Thread Timothy Metz

I have a Netgear and have to specify a default host for a given port. Do you
have something similar? My default host for port 23 is my access layer 2501
and I can telnet in from outside of my LAN.

Tim

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Mark Rose
> Sent: Monday, March 05, 2001 6:28 PM
> To: Cisco@Groupstudy. Com (E-mail)
> Subject: Telnet to a Router
>
>
>
> I am trying to telnet to a 2514 router from work. I have a Linksys BEFSR41
> ethernet/dsl router on my incoming cable line. I have enabled port
> forwarding for telnet (port 23) on this router. I have also set up vty on
> the 2514. When I try to telnet to the wan interface of the
> Linksys forwarded
> to the ethernet interface on the 2514 I get the message "Could not open a
> connection to host: Connection failed". But if I remote access an
> NT server
> inside my home net (on internal address space), from there I can
> telnet (on
> the private address space) to the same ethernet interface and connect.
>
> Since I can remote access my NT box, port forwarding on the Linksys router
> is working. Also the 2514 should be set properly since I can
> telnet in from
> within my lan. I must be overlooking something but I cannot figure it out.
>
> I would appreciate any ideas or assistance.
>
> TIA
> Mark
>
>
>
> _
> 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]



RE: Telnet to a Router

2001-03-05 Thread Albert Lu

Hi Mark,

Could it be that the router doesn't know where to send packets it is trying
to reply to? Try adding a static route to your gateway, so packets coming in
will know where to go (your gateway) once it arrives.

ip route 0.0.0.0 0.0.0.0 e0

That is one way of doing it. Please make suggestions if there is better way.
Of course you could use a routing protocol, but thats abit complicated when
all you want to do is telnet in.

Regards,

Albert

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Mark Rose
> Sent: Tuesday, 6 March 2001 4:28
> To: Cisco@Groupstudy. Com (E-mail)
> Subject: Telnet to a Router
>
>
>
> I am trying to telnet to a 2514 router from work. I have a Linksys BEFSR41
> ethernet/dsl router on my incoming cable line. I have enabled port
> forwarding for telnet (port 23) on this router. I have also set up vty on
> the 2514. When I try to telnet to the wan interface of the
> Linksys forwarded
> to the ethernet interface on the 2514 I get the message "Could not open a
> connection to host: Connection failed". But if I remote access an
> NT server
> inside my home net (on internal address space), from there I can
> telnet (on
> the private address space) to the same ethernet interface and connect.
>
> Since I can remote access my NT box, port forwarding on the Linksys router
> is working. Also the 2514 should be set properly since I can
> telnet in from
> within my lan. I must be overlooking something but I cannot figure it out.
>
> I would appreciate any ideas or assistance.
>
> TIA
> Mark
>
>
>
> _
> 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]



Telnet to a Router

2001-03-05 Thread Mark Rose


I am trying to telnet to a 2514 router from work. I have a Linksys BEFSR41
ethernet/dsl router on my incoming cable line. I have enabled port
forwarding for telnet (port 23) on this router. I have also set up vty on
the 2514. When I try to telnet to the wan interface of the Linksys forwarded
to the ethernet interface on the 2514 I get the message "Could not open a
connection to host: Connection failed". But if I remote access an NT server
inside my home net (on internal address space), from there I can telnet (on
the private address space) to the same ethernet interface and connect.

Since I can remote access my NT box, port forwarding on the Linksys router
is working. Also the 2514 should be set properly since I can telnet in from
within my lan. I must be overlooking something but I cannot figure it out.

I would appreciate any ideas or assistance.

TIA
Mark



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