> >> networked (via GB Ethernet ?) > This is very unnecessary, each RDP client only requires 256Kbps so 10Meg
The GB Ethernet would be between our Server App and the Clients running on the TS machine only. The TS machine would then need a (10meg!) pipe to the internet to connect to branches. > >> TS machine might use IP networking > > Absolutely, no other option I mean 'IP networking' as a telecom product as opposed to TCP/IP. Would Walker Wireless be an alternative ? > you prob want to limit to 256 colours and no annoying animations! Our App runs OK in 256 colours, few animations and progress bars. In our testing we are using Win 2000 server which seems to only give us the option of 256 colours anyway. Rob Software engineer Wild Software Ltd Ph 03 338-1407 ----- Original Message ----- From: "Neven MacEwan" <[EMAIL PROTECTED]> To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]> Sent: Thursday, December 12, 2002 11:01 AM Subject: Re: [DUG]: Terminal Services > Rob > > >> networked (via GB ethernet ?) > > This is very unnessary, each RDP client only requires 256Kbps so 10Meg > would satify 40 Clients 100Mb 400!, RDP is a lot thinner than X and this is > the main advantage of TS (at the moment!) though there is now a lot more > interest > in these type of platforms for Linux see > http://eltoday.com/article.php3?ltsn=2002-12-11-001-15-NW > > What I'd like to see is an RDP Server for Linux > > >> TS machine might use IP networking > > Absolutely, no other option > > >> TS just knowing that we can setup printers at the > >> client end that can be printed to by our Server application is sufficient > > The only limit would be 'noisy' print jobs on a modem link also > you prob want to limit to 256 colours and no annoying animations! > > Neven > > > ----- Original Message ----- > From: "Robert Martin" <[EMAIL PROTECTED]> > To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]> > Sent: Thursday, December 12, 2002 10:35 AM > Subject: Re: [DUG]: Terminal Services > > > > Thanks very much Neven, your response answers some of the many questions > > that I had not even got around to asking. > > > > Our plan may be to run our server app on one machine and have a TS machine > > networked (via GB ethernet ?) to it. This machine would run our client > App > > for 30 -35 users. The clients will use Jetstream to connect (modem for > > backup), the TS machine might use IP networking (or some other guaranteed > > service, suggestions?). Re printing, I had hoped to setup network shares > > that our server could print to. Since we wont be doing the actual install > > and configuration of TS just knowing that we can setup printers at the > > client end that can be printed to by our Server application is sufficient. > > > > > > Rob > > > > Software engineer > > Wild Software Ltd > > Ph 03 338-1407 > > ----- Original Message ----- > > From: "Neven MacEwan" <[EMAIL PROTECTED]> > > To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]> > > Sent: Wednesday, December 11, 2002 1:37 PM > > Subject: Re: [DUG]: Terminal Services > > > > > > > Robert > > > > > > We run probaly half a dozen Terminal Servers with remote connections wia > > > Modem and ADSL > > > Quickly the points I'd make follow > > > > > > A 56K Modem is marginal at 800x600, JetStart 128K is OK, at 256K (Walker > > > Wireless etc) > > > I remotely design reports using Crystal > > > > > > To support adhoc connections we use a VPN server under Linux (cause the > M$ > > > VPN security is crap) > > > and the Windows VPN Client, Though we have recently installed a snapgear > > > router pair for a client > > > > > > The VPN has the advantage of printers being shared at a network level. > the > > > downside > > > is you cant route it (so for a remote site with multiple clients its not > > > really and option, though > > > you can run one VPN Client on a win2K+ machine and route thru that), > > > and it can be unreliable on connection. The main 'gotcha' > > > with TS Client Printing is though a session will share your local > printers > > > the name is randomly generated each > > > connection so it is impossible to persist printer configs. Hence a > better > > > solution is to use LPD > > > printing with some form of client on the workstation (Moccha) or share > at > > > Windows Network level > > > (ie you share the local printer on the client and configure a printer on > > the > > > TS to print to it) > > > > > > 2 other options to consider for a rollout are the xtra ADSL based VPN > > > Service or Static IP's for > > > server and client site and packet filtering for security (for the TS > > client > > > protocol and LPD) > > > > > > As for testing, if it works locally it will work remotely (I wouldn't > > > recommend 56K modems, maybe citrix > > > is called for, the ICA protocal being more efficient than RDP). And > > testing > > > printing. you have to be careful > > > of is the size of the print jobs, This can of course vary with 'soft' > (non > > > printer fonts) etc > > > > > > HTH > > > > > > Neven > > > > > > > > > ----- Original Message ----- > > > From: "Robert Martin" <[EMAIL PROTECTED]> > > > To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]> > > > Sent: Wednesday, December 11, 2002 9:16 AM > > > Subject: [DUG]: Terminal Services > > > > > > > > > > Hi All > > > > > > > > Not really a Delphi question but I note that there are some people > with > > TS > > > > experience on the list so here goes. We are testing our application > on > > TS > > > > for a client, we have it all running on our network here and want to > > trail > > > > it over jetstream and modem. Do we need a fixed IP address for the TS > > > > machine? If so how do we set this up, what's the best way (remember > > this > > > is > > > > only a short term test). > > > > > > > > TIA > > > > Rob > > > > > > > > Software engineer > > > > Wild Software Ltd > > > > Ph 03 338-1407 > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > - > > > > New Zealand Delphi Users group - Delphi List - > [EMAIL PROTECTED] > > > > Website: http://www.delphi.org.nz > > > > To UnSub, send email to: [EMAIL PROTECTED] > > > > with body of "unsubscribe delphi" > > > > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > > > > > > > > > > -------------------------------------------------------------------------- > > - > > > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > > > Website: http://www.delphi.org.nz > > > To UnSub, send email to: [EMAIL PROTECTED] > > > with body of "unsubscribe delphi" > > > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > > > > > > > > -------------------------------------------------------------------------- > - > > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > > Website: http://www.delphi.org.nz > > To UnSub, send email to: [EMAIL PROTECTED] > > with body of "unsubscribe delphi" > > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > > > -------------------------------------------------------------------------- - > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > Website: http://www.delphi.org.nz > To UnSub, send email to: [EMAIL PROTECTED] > with body of "unsubscribe delphi" > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
