Hello Ken,
Yes, Mark is correct. RDC is short (in my book anyway) for Remote Desktop Control aka Terminal Services or Citrix etc…
Yes, I subscribe to www.wunderground.com for my weather information. The $5 a year it costs is well worth the money IMO (in my opinion). <grin>
Pulling current, animated radar images over my Sprint DATA card has not given me any trouble. Speed test confirmation from www.testmy.net :
:::.. Download Stats ..::: Download Connection is:: 654 Kbps about 0.65 Mbps (tested with 579 kB) Download Speed is:: 80 kB/s Tested From:: http://testmy.net/ (Server 1) Test Time:: 2006/09/18 - 4:26pm Bottom Line:: 11X faster than 56K 1MB Download in 12.8 sec Tested from a 579 kB file and took 7.25 seconds to complete Download Diagnosis:: 90% + Okay : running at 96.04 % of your hosts average (spcsdns.net) D-Validation Link:: http://testmy.net/stats/id-814GRHMXW
I’ve seen well over 1Mbps before, but even then 654Kbps isn’t that bad. Latency typically looks like this:
Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=163ms TTL=237 Reply from 4.2.2.2: bytes=32 time=173ms TTL=237 Reply from 4.2.2.2: bytes=32 time=188ms TTL=237 Reply from 4.2.2.2: bytes=32 time=172ms TTL=237 Reply from 4.2.2.2: bytes=32 time=239ms TTL=237 Reply from 4.2.2.2: bytes=32 time=170ms TTL=237 Reply from 4.2.2.2: bytes=32 time=185ms TTL=237 Reply from 4.2.2.2: bytes=32 time=167ms TTL=237 Reply from 4.2.2.2: bytes=32 time=155ms TTL=237 Reply from 4.2.2.2: bytes=32 time=368ms TTL=237 Reply from 4.2.2.2: bytes=32 time=151ms TTL=237 Reply from 4.2.2.2: bytes=32 time=165ms TTL=237 Reply from 4.2.2.2: bytes=32 time=179ms TTL=237 Reply from 4.2.2.2: bytes=32 time=200ms TTL=237 Reply from 4.2.2.2: bytes=32 time=162ms TTL=237 Reply from 4.2.2.2: bytes=32 time=180ms TTL=237 Reply from 4.2.2.2: bytes=32 time=181ms TTL=237 Reply from 4.2.2.2: bytes=32 time=160ms TTL=237 Reply from 4.2.2.2: bytes=32 time=175ms TTL=237 Reply from 4.2.2.2: bytes=32 time=159ms TTL=237 Reply from 4.2.2.2: bytes=32 time=146ms TTL=237 Reply from 4.2.2.2: bytes=32 time=185ms TTL=237 Reply from 4.2.2.2: bytes=32 time=143ms TTL=237
Ping statistics for 4.2.2.2: Packets: Sent = 23, Received = 23, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 143ms, Maximum = 368ms, Average = 181ms
Tracert looks like this:
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2] over a maximum of 30 hops:
1 171 ms 157 ms 162 ms 68.28.177.69 2 * * * Request timed out. 3 191 ms 183 ms 190 ms 68.28.187.54 4 326 ms 162 ms 156 ms 68.28.187.6 5 * * * Request timed out. 6 * * * Request timed out. 7 162 ms 158 ms 164 ms 68.28.187.97 8 168 ms 153 ms 160 ms 68.28.187.18 9 194 ms 162 ms 157 ms sl-gw11-atl-0-1.sprintlink.net [144.223.140.69] 10 171 ms 161 ms 157 ms sl-bb22-atl-5-0.sprintlink.net [144.232.12.85] 11 161 ms 159 ms 188 ms sl-bb25-atl-9-0.sprintlink.net [144.232.12.38] 12 173 ms 193 ms 189 ms sl-bb22-fw-15-0.sprintlink.net [144.232.8.21] 13 186 ms 186 ms 184 ms sl-bb27-fw-12-0.sprintlink.net [144.232.11.33] 14 180 ms 183 ms 187 ms sl-st20-dal-13-0.sprintlink.net [144.232.20.83] 15 384 ms 173 ms 167 ms interconnect-eng.Dallas1.Level3.net [64.158.168.73] 16 166 ms 193 ms 206 ms so-1-2-0.bbr1.Dallas1.Level3.net [209.244.15.16] 17 180 ms 183 ms 192 ms ge-11-0.core1.Dallas1.Level3.net [4.68.122.40] 18 423 ms 224 ms 199 ms vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.
As with most things YMMV. (Your Mileage May Vary) <grin>
Best,
Brad
-----Original Message-----
Remote Desktop Connection I would suspect…
Mark McElvy From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of [EMAIL PROTECTED]
Two questions. What is RDC? Is the data rate for the Sprint card high enough to download color weather radar images quickly? Ken Chipps
|
-- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/