Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Terminal Server over WAN ping time.

Posted on 2004-09-16
2
Medium Priority
?
465 Views
Last Modified: 2013-11-21
hello,

we currently have a win2k3 std server, with terminal server setup.
We have several remote clients (all based in Australia) that access TS via WAN.
We are looking to setup a second server and are deciding on two options.

1) we lease a high performance (dual xenium) dedicated server in a US datacenter
   ie theplanet.com and benefit from the cheaper data and better servers but have to
   deal with a slower connection time as all clients are in Australia (ping time is
   approx 280ms).

or

2) we lease an average performace (p4) dedicated server here in Aus and benefit from the
   faster connection. (ping time is approx 25-48ms) but deal with the higher data costs and
   Poorer server performance.

we have an average of 25 client machines logging via remote access and using MS office 2003
and several intranet sites hosted on that machine.

how slow can a TS connection be ?

0
Comment
Question by:servb2b
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 5

Assisted Solution

by:netspec01
netspec01 earned 1000 total points
ID: 12076170
TS can work over dial-up connections.  Depending on your applications/users, 280ms delay may be excessive.  When delay exceeds 150-200 ms the end users will definitely "feel" it.  If users are on dial-up this could be really, really slow.

You didn't say how much bandwidth was available either at the hosting end or at the user end.  At ThePlanet bandwidth wouldn't be an issue.  Make sure bandwidth is also adequate at the AU site.

For each location that will be connecting to the TS see what bandwidth is available.  The amount of activity/usage per TS connection + number of clients should be examined on a site by site basis.  

I would try to stay at 15 users per T1 equivalent (1.5Mb) for heavy use.  I'd try to keep line latency under 150Mms.

And don't foget to adeqautely size you server resources!

0
 

Accepted Solution

by:
kevinf99online earned 1000 total points
ID: 12076815
I second what netspec01 said above.  Additionally - memory is important.

Since you already lease from both locations - testing is your best option.  We don't know how your applications are written, how your users use Office 2003 and what type of content your intranets have on them - nor how often your users are accessing that data.  For example - frequent access to large chunks of data will work better on your larger scaled system, even with larger latency (assuming you have sufficient bandwidth).  But frequent access to small pages, small bits of data, lots of typing, etc... will likely work better on the smaller system with lower latency.

There is an excellent article by MS at http://www.microsoft.com/windowsserver2003/techinfo/overview/tsscaling.mspx.  Download the document titled TermServScaling.doc located on the right of the page.  It has guidelines to testing your application, as well as some sample tests provided, showing server usage per user and such.

If I had to take a shot in the dark - with only 25 users, your P4 with lower latency (assuming it has enough memory and bandwidth is equal to the other system) will be your best system.  But it costs more, and perhaps you're overloading it with the type of usage.  In which case, you'll like the lower cost/higher latency solution.

But without research on your part - there is no definitive way to answer your question.  You should set up a pilot test.

Test.  Test.  Test.

Did I say testing is best?

Kevin
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question