Building the optimal host PC for remote access
Posted on 2010-11-10
I've recently joined an out of state firm and am working remotely via Terminal Services. My connection is at times painfully slow and we're trying to resolve this issue. I connect with an XP Pro client (Fuji Lifebook 4220 tablet with 4 gig ram) to an XP Pro Host (Xeon, 2 gig ram, 1 gig NIC) via TS and am the only session running. On client end I have consistent 6-9 meg both up and down speeds via 7 bonded T1s in my Executive Suite. Host end uses Comcast with supposedly 30 meg down (don't know about upload). Pinging from the host to 220.127.116.11 gives fairly consistent 100+ ms access averages. Pinging from my local client yields consistent 22 ms averages. The host TS connects to a LAN running a SQL database that I access to work.
The (contracted/part-time) tech on their end has tried various things (not sure what) and then brought in his box to try (off the TS) with Win7, a Pentium D and 2 gig ram. Connection to this box via RDP was slower. Connection to this box via Radmin was marginally faster than the TS Host. One side note: I can't figure out why but a Speakeasy speedtest outbound from the personal box yield MUCH faster speeds than the TS Host box, like 30 meg down vs. 12meg.
Anyway, since I have no control over what they do on their end, I would like to take the hardware on the host end completely out of the equation by building a box designed specifically for remote use and then shipping to them to install on the network. They will allow this and I will be the only one using this machine. My budget is $2,000 max.
I would like suggestions on the components/configuration to build the box with. I know i want lots of ram, discrete video/ram and a solid state drive. What else would make the box the optimal host PC for remote access?