Telnet with a Windows 2003 server

[GCC Consulting]

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Brian K. White
> Sent: Tuesday, November 27, 2007 4:48 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: Telnet with a Windows 2003 server
> 
> 
> ----- Original Message -----
> From: "Bob Rasmussen" <ras at anzio.com>
> To: "GCC Consulting" <gccconsulting at comcast.net>
> Cc: "'Filepro-List at Lists. Celestial. Com'" 
> <filepro-list at lists.celestial.com>
> Sent: Friday, November 23, 2007 9:22 PM
> Subject: RE: Telnet with a Windows 2003 server
> 
> 
> > On Fri, 23 Nov 2007, GCC Consulting wrote:
> > 
> >> Would Anzio connecting using telnet run faster?
> > 
> > It should, due to less data going across the line.
> > 
> >> 
> >> Would printing using Anzio's built in printwizard to local 
> printers work?
> > 
> > I don't know that yet.
> 
> One thing to be aware of and watch out for,
> The built in telnet client in nt/2k/xp*, connecting to the 
> built-in telnet server in nt/2k/xp does not work in a 
> streaming mode, it works by periodic screen updates (or 
> something), where data is lost from one refresh to the next, 
> and so, I very much doubt passthrough print would work 
> reliably if at all there. In any event, does the windows 
> version of fp even allow for passthrough? There is no termcap 
> nor terminal type for win32 console. How would fp know what 
> sequences to send? You'd have to do all your printing to temp 
> files and do the passthrough yourself with system() commands 
> or pfpostprint or maybe show raw, etc.
> 
> It is possible the terminal server telnetd is better and acts 
> more like a unix telnetd just for this kind of reason. I 
> never used it or tested for this effect. Similarly any other 
> 3rd party telnet server. It's definitely something to look out for.
> 
> ... Ah, ok mystery solved there, the xp tenetd can be 
> configured for either console or streaming mode.
> 
> http://www.windowsitpro.com/Articles/ArticleID/37559/37559.html?Ad=1
> 
> ---snip---
> 
> Q: How can I switch my Telnet server to use Stream mode 
> instead of Console mode in Windows XP?
> 
> A: Non-Windows clients that connect to a Windows Telnet 
> server might work better if the Telnet server is in Stream 
> mode rather than Console mode. To change your server to use 
> Stream mode, go to the command prompt and type 
>     tlntadmn config mode=stream
> 
> To check your current mode under Windows XP, type 
>     tlntadmn
> 
> Windows will display the mode under Mode of Operation. For example, 
> 
> Alt Key Mapped to 'CTRL+A' : YES
> Idle session timeout : 1 hours
> Max connections : 2
> Telnet port : 23
> Max failed login attempts : 3
> End tasks on disconnect : NO
> Mode of Operation : Stream
> Authentication Mechanism : NTLM, Password
> Default Domain : TRINITY
> State : Stopped
> 
> ---snip---
> 
> Brian K. White    brian at aljex.com    http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!

Filepro has a problem with terminal server as one does not know what the
terminal server session # is for the printer.  Theresore pfpostprint along
with printwizard would work by redirecting the print job to the default
windows printer for that session.

Richard