If Hyperterminal is being told to connect to COM3 and giving that message, we need to figure out what other piece of software on the system is also using COM3.
Quick thing to try: If you reboot the laptop and try re-connecting to COM3 with Hyperterminal, has the other application hogging the port gone away? I actually tried that earlier, but failed to mention it. I just did it again for a sanity check, setting the port to COM Including a restart.
Same error message. Two more quick things to try:. If you have a chance to check that and see if any applications come up, that could provide a clue …. I tend to agree with you that this is something simple that is just eluding us. If I had had this machine for some time I might suspect I downloaded something some time that is causing the problem, but it is only a few weeks old and I have not had too much of a chance to crap it up yet.
I am just getting familiar with Linux, so it could take me some time to figure out, and I am not sure how that would ultimately help in the Windows 7 environment. Like I said, neither are running unless I explicitly start them.
That will work with this adapter. But looking into it might also confirm or not if VirtualBox may be the entity already grabbing the COM port. What exactly you are trying to do? Could you please elaborate the issue? Are you in a domain network? Have you made any changes on the computer prior to this issue? What is the make and model number of your computer? Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. I'm trying to communicate to the console ports on several Cisco switches and routers.
I my computers do not have a 9pin Dconnector that will connect to a standard Cisco console cable, and the Cisco devices do not have USB.
This has worked for a while. It's running XP OS. This has been working for a year or so, and right in the middle of running it just stopped working and was hung. I get the above error message when ever I use "Putty" software to do the serial terminal emulation. I searched the internet for this, and the best advice was to manually install the com port. I tried anyway, but uninstalled when done. How does the COM3 port get built?
Should it always show available, or does it build the interface when a device is plugged in? It recognized the device and gave a "bong" and it appeared. Therefore I susspect that it is built when the device is plugged in, and torn down when it is disconnected. Not sure why it's now working I'm sure there is a logical explaination, but not any help from the MS OS Maybe the Belkin device is flakey, but unlikely due to the number of times I unplugged and replugged I then grabbed a Laptop running Windows 7 and connected to it's USB port, and running putty software, and it started working.
Your Windows question is more complex than what is typically answered in the Microsoft Answers forums.
0コメント