When I use Absolute Telnet Client to connect to Windows Telnet Server that is configured and running on Windows XP Professional, certain control characters, such as ^C, do not pass through correctly. This happens when I use a Unix telnet client also, so this is clearly not a problem with Absolute Telnet. Still, I wondered if you had any insight into this issue. Do you know of any pointers for additional information on Windows Telnet Server? Logging that I may enable? Tips or tricks?

Thanks!

[size=1][ December 03, 2003, 01:22 PM: Message edited by: Brian T. Pence ][/size]

As you can imagine, Microsoft doesn't have a whole lot of desire to make command line stuff work well. It's not in their business plan. I'm sure if they thought they could kill the old DOS command window, they would!!

Many Windows telnet servers operate by running a DOS window in the background and screen-scraping the Window and sending the data across to the telnet client.

I've not used the XP pro telnet server, but I have used the Ataman products (www.ataman.com) for telnet on NT, and I can also recommend WinSSHD (www.bitvise.com) for an SSH server in a Windows environment.

Using WinSSHD and AbsoluteTelnet, I've even gotten full-color full-screen DOS apps (such as edit.com) to work, including alt-key menu dropdowns and such...