VTY virtual terminal NOT ACCESSIBLE.....

Hyperterm is a telnet client.  So what is the other telnet client you are using?

Have you tried configuring hyperterm so that it presents itself as a VT100 type terminal?

The Hyper terminal I am talking about is from Start-programs-Accessories-communication-Hyper terminal

The telnet I am talking about here is through the RUN command
TELNET IP ADDRESS

yes. it's VT100

an easier workaround is to use another terminal, just like PuTTY:
-------------
http://www.chiark.greenend.org.uk/~sgtatham/putty/
-------------

hope it helps.

Thanx kanlue. But you didn't tell me why Hyper terminal is not working? I think it's supposed to work with CISCO router.

Hi wuitsung, sorry that i missed that part.

yes, the 'HyperTerminal' is just a telnet client application, it should work with any telnet servers including cisco routers.

did you try to use the same HyperTerminal to telnet to other telnet servers like your linux, cisco equipments? if you did get the same issue here, i would think that the HyperTerminal application is not working properly, and it needs to be fixed.

hope it helps.

You may want to do a packet capture.  I use hyperterm to Cisco equipment all of the time and have never had an issue.

thank you giltjr. How do I use the packet capture and what do you look inside?

Well I use wireshark (http://wwww.wireshark.org) you capture the packets, then look to see if the router is sending back data.

For the server (domain controller ) that was not able to VTY the router. I take the cable and connect the router directly to the server. Still the Hyper terminal not able to do anything with the router. (I also changed the configuration to com port). I am able to see the bootup process, btu after that, no matter what I do, it still stay there.

I also reinstall the hyper terminal on the server, it still doesn't fix the problem.

I used the windows network monitor, I did see some traffic from the router 10.0.1.254. Here is the screenshot.

I am wondering that is that there is a conflict with domain controller ?
nm.JPG

If "CISCO 37A954" is the router, it is sending a ARP to find the MAC address for the device with the IP address of 10.0.1.254.  Do yo know what device that is?

Why do you think there is a conflict with the domain controller?

Run the packet capture again, but this time filter so that only traffic between your computer and the router is captured.  You can capture the data with netmon, but I would still suggest that you get wireshark.  Wireshark can look at data caputed with netmon and Wireshark is a lot easier to use to filter traffic.

Hi giltjr, Thank you very much.
10.0.1.254 is the ip address of the router. The other side of the router is 10.0.2.254. My DC has the ip address 10.0.1.1

I tried Wireshark, indeed, it looks better than netmon. thank you. But I am not sure if I configured the right setting. I went to Capture/Capture filters/New/
I created the filter string : host 10.0.1.254

And here is the result I got (screenshot) and more detail in txt file. Thank you again.


cisco.JPG
cisco.txt

I also saw this at later time when I capture all traffic without filtering.

Source: Cisco_37:a9:54
Destination: CDP/VTP/DTP/PAqP/UDLD
Protocol: CDP
Info: Device ID: Router Port ID: Ethernet 0

*The DC is directly connected to the router.

Hi wuitsung, you mentioned that you can 'telnet 10.0.1.254'  successfully through command line in the SAME server. then why not do that again while you are capturing the packet by using 'Wireshark'. that way, you will get some data in the result.

if both 'telnet 10.0.1.254' and 'HyperTerminal' are not working in your server, maybe your server block the traffic.

Hi giltjr, I tried what you said, but I see nothing there.

And as kanlue suggested, I I captured the tcp port 23 traffic, here is the result in attachment.
Telnet is working. I am able to access my router.
telnet.txt

And I just tried one more thing. I tried to use the hyper terminal from other server (VTY). And it's WORKING.... I really have no idea why it's not working on my DC. I already uninstalled it and reinstalled...

strange. you may try to check the following although it sounds not that right:
is there any anti-virus application running in your server?
it might block outgoing telnet traffic; or your server firewall settings block it?
just a thought.

No firewall or antivirus installed on my DC

I am wondering if the com port is defective.. but if I can see the output, I think it's not...

And I haven't restarted my DC yet.. I will do it.

It's fixed now after I restarted my DC! and reinstall the hyper terminal. Thank you for everyone here.

And for the wireshark, how can I specify other protocol to filter? I noticed that there are not many choices in Capture filter, less than windows network monitor.

The capture filter is based on tcpdump, so if you look at examples of how to run tcpdump you can them.  There are basically TONS of stuff you can do.  Examples:

   ip host www.someplace.tdl

will only capture traffic to/from the ip address that the name www.someplace.tdl resloves to.  The  filter

   tcp port 23

will only trap traffic that has a source or destination port of tcp port 23 and:

   ip host www.someplace.tdl and tcp port 23

will only capture traffic that is to/from the address that www.someplace.tdl resloves to and is also to from tcp port 23.

Now the view filters in wireshark are totally different from tcpdump.