I'm trying to connect my XP PC to a switch through the serial port,
using SecureCRT.

On PC A I've got SecureCRT 5.5.0
It connects just fine

On PC B (the one I would rather use) I've got SecureCRT 6.1.0 (I woudl
rather not downgrade versions)
I've set it up the same way as the other one (Protocol: Serial,
settings: 9600, 8, none, 1)
When I try to connect I get-
Connection to session Serial-Com1 failed, Unable to open seial port
Com1, Access is denied.

On version 6.1.0 there is an extra part (not found in the older
version) under Properties labled SSH2, that shows Port:22, Firewall:
None.

I've looked under device manager and looked at the com1 port, says
everything is fine. Is there something else I need to do to open this
port?

Check the Interrupt (Int) number on both PCs,
are they the same or different?

Is anything else also using/sharing the same Interrupt on PC B?

--
JS
http://www.pagestart.com


"alice" <alice@fearofdolls.com> wrote in message
news:7bb3112e-ec71-43d4-923b-1f4a74f4bed3@f1g2000prb.googlegroups.com...
> I'm trying to connect my XP PC to a switch through the serial port,
> using SecureCRT.
>
> On PC A I've got SecureCRT 5.5.0
> It connects just fine
>
> On PC B (the one I would rather use) I've got SecureCRT 6.1.0 (I woudl
> rather not downgrade versions)
> I've set it up the same way as the other one (Protocol: Serial,
> settings: 9600, 8, none, 1)
> When I try to connect I get-
> Connection to session Serial-Com1 failed, Unable to open seial port
> Com1, Access is denied.
>
> On version 6.1.0 there is an extra part (not found in the older
> version) under Properties labled SSH2, that shows Port:22, Firewall:
> None.
>
> I've looked under device manager and looked at the com1 port, says
> everything is fine. Is there something else I need to do to open this
> port?
>

On May 4, 10:40*pm, alice <al...@fearofdolls.com> wrote:
> I'm trying to connect my XP PC to a switch through the serial port,
> using SecureCRT.
>
> On PC A I've got SecureCRT 5.5.0
> It connects just fine
>
> On PC B (the one I would rather use) I've got SecureCRT 6.1.0 (I woudl
> rather not downgrade versions)
> I've set it up the same way as the other one (Protocol: Serial,
> settings: 9600, 8, none, 1)
> When I try to connect I get-
> Connection to session Serial-Com1 failed, Unable to open seial port
> Com1, Access is denied.
>
> On version 6.1.0 there is an extra part (not found in the older
> version) under Properties labled SSH2, that shows Port:22, Firewall:
> None.
>
> I've looked under device manager and looked at the com1 port, says
> everything is fine. Is there something else I need to do to open this
> port?

What's a serial port? Com1?

Kidding... I did a little Googling and other people with similar
errors found their problem/solution in the BIOS in the Peripheral
section.

Hard to say what your BIOS is going to look like and they sure don't
say what theirs look like, but that error was resolved in several
cases through a BIOS adjustment. Maybe look at PC A and PC B if they
happen to have the same BIOS or check out the Peripheral section in PC
B and tinker there.

I used to like to use a loopback plug - just jumper Tx to Rx and some
free comm software just to see if characters would echo back to be
sure the ports at least worked by echoing back the character I typed.

On May 4, 9:15*pm, "JS" <@> wrote:
> Check the Interrupt (Int) number on both PCs,
> are they the same or different?
>
> Is anything else also using/sharing the same Interrupt on PC B?
>
> --
> JShttp://www.pagestart.com
>
> "alice" <al...@fearofdolls.com> wrote in message
>
> news:7bb3112e-ec71-43d4-923b-1f4a74f4bed3@f1g2000prb.googlegroups.com...
>
>
>
> > I'm trying to connect my XP PC to a switch through the serial port,
> > usingSecureCRT.
>
> > On PC A I've gotSecureCRT5.5.0
> > It connects just fine
>
> > On PC B (the one I would rather use) I've gotSecureCRT6.1.0 (I woudl
> > rather not downgrade versions)
> > I've set it up the same way as the other one (Protocol: Serial,
> > settings: 9600, 8, none, 1)
> > When I try to connect I get-
> > Connection to session Serial-Com1 failed, Unable to open seial port
> > Com1,Accessisdenied.
>
> > On version 6.1.0 there is an extra part (not found in the older
> > version) under Properties labled SSH2, that shows Port:22, Firewall:
> > None.
>
> > I've looked under device manager and looked at the com1 port, says
> > everything is fine. Is there something else I need to do to open this
> > port?- Hide quoted text -
>
> - Show quoted text -

The settings in device manager where different it turned out, but even
after changing them it does not work. Haven't checked the BIOS yet,
seems like something I shouldn't have to mess with to get a com port
to work.
How do I tell if something else is using IRQ4?

On May 9, 1:03*pm, alice <al...@fearofdolls.com> wrote:
> On May 4, 9:15*pm, "JS" <@> wrote:
>
>
>
> > Check the Interrupt (Int) number on both PCs,
> > are they the same or different?
>
> > Is anything else also using/sharing the same Interrupt on PC B?
>
> > --
> > JShttp://www.pagestart.com
>
> > "alice" <al...@fearofdolls.com> wrote in message
>
> >news:7bb3112e-ec71-43d4-923b-1f4a74f4bed3@f1g2000prb.googlegroups.com...
>
> > > I'm trying to connect my XP PC to a switch through the serial port,
> > > usingSecureCRT.
>
> > > On PC A I've gotSecureCRT5.5.0
> > > It connects just fine
>
> > > On PC B (the one I would rather use) I've gotSecureCRT6.1.0 (I woudl
> > > rather not downgrade versions)
> > > I've set it up the same way as the other one (Protocol: Serial,
> > > settings: 9600, 8, none, 1)
> > > When I try to connect I get-
> > > Connection to session Serial-Com1 failed, Unable to open seial port
> > > Com1,Accessisdenied.
>
> > > On version 6.1.0 there is an extra part (not found in the older
> > > version) under Properties labled SSH2, that shows Port:22, Firewall:
> > > None.
>
> > > I've looked under device manager and looked at the com1 port, says
> > > everything is fine. Is there something else I need to do to open this
> > > port?- Hide quoted text -
>
> > - Show quoted text -
>
> The settings in device manager where different it turned out, but even
> after changing them it does not work. Haven't checked the BIOS yet,
> seems like something I shouldn't have to mess with to get a com port
> to work.
> How do I tell if something else is using IRQ4?

I would look at the BIOS first. Unless something is really haywire,
the IRQs are probably okay.

Windows will want to use IRQ4 for COM1 and IRQ3 for COM2 by default.
According to Windows, I only have a COM1 configured on my box but I
never use it.

Look in Device Manager, Ports, Communications Port (COM1), Properties
the Resources tab. If it is NOT IRQ4, we should figure out how it got
changed.

Hi Guys,

Thanks for your communication about this issue, I just read your post, and I found that the only way - and it worked - is to go and change the port number to be COM 1, even if it is states "used".

Tx,
Cheers