Issue with Telneting into CISCO 851W

[jorgeflores4]

Home Net Topology

ISP/WAN > Modem > Router (linksys) >Router(CISCO 851W) > (serial cable) 2008 R2

____________________________________________________________________________________________________________________________

I have the loopback cable connected from my server to the CISCO router. The router is connected to the router in the office with a crossover cable. It is connected to Lan port 4 (Linksys) and the cable is plugged in to the WAN port(CISCO). The idea is to have the CISCO router as a test router for me to play with while using another IP subnet class where I can connect to but have internet as well (setting it's GW to linksys' IP).

When I use putty to connect to the router, nothing happens. The configurations are set correctly 9600 .etc..just need ideas as to why it does not even answer. I want it to promt:

>Router:

After which I'll be happy.

I am not sure if it used to work before. I bought it off of Ebay as "Used but in great condition" about 6 months ago (And it's an old router as it is). The lights turn on and all, and so far looks undamaged. But I am open to thoughts and your comments.

[Richard Burts]

I find the description of the problem to be confusing. Part of the time you appear to be describing a problem with telnet access to the Cisco router. And part of the time you seem to be describing a problem with access to the Cisco router via its console connection. So perhaps we can get some clarification of what is the problem?

As a start if you are using putty can you tell us whether you are using the option for telnet, for ssh, or for serial?

And can you tell us a bit more about the cable that you are using to connect from your server to the Cisco router? What kind of cable is it? And where on the Cisco router is it connected? (to the console connection, to the aux connection, to an Ethernet connection, or what)?

HTH

Rick

[jorgeflores4]

Well, hello Mr. Burts.

I do appologize for the confusion. I will do my best to answer your questions.

The cable that is connected from the CISCO router to my server computer is a

RJ-45 to DB9 cable. It is colored light blue, and it is connected from the "Console" port of the router to my computer's USB port. I am using a DB9 to USB converter (which should not make a difference).

In the server, I use putty with the current configuration:

COM1

Speed: 9600

Data bits: 8

Stop bits: 1

Flow: none

In the Session window (Putty):

Serial line: COM1

Speed 9600

and the "Serial" button is selected

The server has the features "TELNET" and "TELNET SERVER" installed.

When I select "OPEN" in putty, I get a terminal window with a blinking cursor. After 20 seconds of waiting, there is still no sign of connection.

Now let me talk about the Router. The router is a CISCO 851W series, that came out in 2006 I believe. There is currently no configuration on it, and this is my first time ever connecting it. This is severing as a secondary router that is connected to the primary router in my home office. However, regardless of it having an internet connection, it should still be able to communicate with a machine via the console port. (As I assume), but is failing to do so.

[Richard Burts · Accepted solution]

Thank you for the additional information. It is helpful and does clarify that this is an isue about console port access and is not about Telnet or SSH. So we will focus on possible issues about the console connection.

It is good that you have the light blue connecting your server and the router. This is the correct type of cable for connecting to Cisco console ports. I agree that it should not make any difference that you are using the USB converter.  And the parameters in putty seem right. As a check on the cable, and the converter, and whether COM1 is the correct port, is there any other Cisco device that you might try to connect to using your server with its cable and its copy of putty?

Also as an experiment, can you power down the 851 router, wait a short time, and power it back up. During the boot process is there any output displayed on the console session?

HTH

Rick

[jorgeflores4]

Mr. Burts, glad to see you again.

I appreciate you taking out time for this. I wish more people could join us. Anyways, no, unfortunately, that is the only CISCO product in the house. But, let's take a step back here. In your experience, just by plugging in the router's console port with the serial cable to the machine and running a terminal client. In all respect, that's it right? I mean, by doing that and of course having the correct terminal settings to allow for proper communication, it SHOULD work and get a response?

If that's the case, then something physical is faulty. If it's not software, it's hardware right Mr. Burts? So you COULD be right in saying that by testing the cable else where to see if it works or not, might just be the cause of this whole thing. Unless of course, again, its a software thing. So, unless you think there is another configuration issue, port issue, or something.. that I am missing or did not check, do you think it could be a physical issue? (I really hope not..)

When I get out of work, I'll go ahead and reboot the machine and see if I get a bootup display or anything.

Thanks sir.

[jorgeflores4]

Hey Mr. Burts,

I went into the company closet (with permission of course) and got myself 3 Console cables to test tonight. Hopefully, that'll get some results.

[jorgeflores4]

Ah, I figured it out. It was a driver issue.

[Richard Burts]

I am glad that you got it resolved. Thank you for using the rating system to mark the question as resolved. It makes the forum more useful when people can read about an issue and can know that a solution was found. Your marking has contributed to this process.

HTH

Rick