Odd problem connecting to the CLI

[TKD2]

We're using a windows server2003 machine to try and connect to the CLI (via COM1) on a 2950 and some 3500-XL's. The wierd problem is that when we 'physically' sit at the machine and try and do it, hyperterminal will never get to the CLI, it just hangs with the cusor on the screen - should we do the exact same proccess via remote desktop then there are no problems what-so-ever.
The same is true of windowsXP, if we connect using this OS then the CLI appears immediately.

I guess the fault here is an over-restrictive 2003 server setting, but we can't find any information on what that may be, and ideas?

 

[eurobadger]

TKD2

You say remote desktops get in...should I assume you are using telnet for this access?

Try the desktop direct to your console. My suspects are data rate on hyperterminal, flow control set to something other than 'none', or the wrong sort of cable.

Of course if the desktop works with the same cable and settings..........

EB

 

[TKD2]

by remote desktop i mean we are using mstsc to take control of the server desktop, then using hyperterminal to get to the cli. Telnet is not involved here.
Logging on with the same user/pass when 'physically' sitting at the server prevents cli access, whereas remote desktoping to it (with that user/pass) is fine.
Obviously, my this analogy - the baud, flow control etc. are the same in both scenarios.