Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #186707
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Alternative for remote desktop connection |
| Date | 2025-08-12 12:35 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <107f8uq$37ukr$1@dont-email.me> (permalink) |
| References | (6 earlier) <107d05s$2gj2l$10@dont-email.me> <115qxw8a067va.dlg@v.nguard.lh> <107dcuf$2ooq7$1@dont-email.me> <mfuticFaqu3U1@mid.individual.net> <1bfmfv9mkw0uy.dlg@v.nguard.lh> |
On 2025-08-12 02:20, VanguardLH wrote:
>
> That could be due to where you are, and where is the public rendezvous
> Rustdesk server to which you connect. I found rs-ny.rustdesk.com
> mentioned, and my traceroute to it shows a huge jump in delay most
> likely caused by having to go over the undersea cable to connect the
> hosts across the pond.
This interpretation in the last sentence is wrong, see below ...
> tracert rs-ny.rustdesk.com
> ...
> 9 21 ms {myISP}
> 10 21 ms ae8.cr9-chi1.ip4.gtt.net [63.141.223.245]
> 11 115 ms ae2.cr2-ams13.ip4.gtt.net [141.136.106.174]
> 12 114 ms ip4.gtt.net [154.14.36.78]
> 13 * Request timed out.
> 14 * Request timed out.
> 15 115 ms 209.250.254.15.vultrusercontent.com [209.250.254.15]
Whereas for me in Scotland, using a mobile broadband connection (because
landlines around here are next to useless, and there is no FTTx in
wildest Sutherland):
11:04:08 D:\Temp>tracert rs-ny.rustdesk.com
Tracing route to rs-ny.rustdesk.com [209.250.254.15]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [anonymised]
2 23 ms 19 ms 19 ms [anonymised]
3 * * * Request timed out.
4 67 ms 90 ms 73 ms 172.26.19.1
5 * * * Request timed out.
6 * * * Request timed out.
7 86 ms 69 ms 87 ms 172.26.24.93
8 * * * Request timed out.
9 71 ms 94 ms 83 ms 172.26.3.150
10 91 ms 90 ms 102 ms 149.11.22.122
11 * * * Request timed out.
12 105 ms 71 ms 83 ms be2592.ccr42.lon13.atlas.cogentco.com
[154.54.60.245]
13 106 ms 98 ms 99 ms be12488.ccr42.ams03.atlas.cogentco.com
[130.117.51.42]
14 101 ms 104 ms 98 ms be2154.rcr22.ams06.atlas.cogentco.com
[130.117.50.206]
15 111 ms 114 ms 98 ms 149.6.0.227
16 * * * Request timed out.
17 * * * Request timed out.
18 114 ms 94 ms 97 ms 209.250.254.15.vultrusercontent.com
[209.250.254.15]
Trace complete.
Again, see below ...
> Even though the nodes on each side of the pond are with gtt.net, their
> own network spans the ocean across their data centers. GTT is global.
> The added latency impinges on every packet across the pond.
>
> You could do a traceroute on the Teamview rendezvous server to see if
> you going the other way across the pond.
>
> By the way, vultrusercontent.com resolves to 127.0.0.1. Odd it resolves
> to localhost. Likely they don't want you directly using that hostname
> since it is a frontend to redirect to their farm of actual servers.
'The pond' is crossed by optical fibres, which by definition carry
signals at the speed of light for that medium, so, at the Atlantic's
widest point of 4,600kms, signals will take 4,600/[between 300,000 (best
case of a vacuum) and 61/0.000350 = 174,286 (worst case of a deliberate
slowing down as a 'speed bump' described in the link below)] = between
0.015s theoretical best case and 0.026s as a practical worst case, so
between 15ms and 26ms. Even in the worst case, these delays are no
worse than the fastest records in the traces above, and significantly
less than most of them, so the delays are caused by other things, such
as how the intervening systems are configured and/or how busy they are
at the time.
https://physics.stackexchange.com/questions/80043/how-fast-does-light-travel-through-a-fibre-optic-cable
"Some real-world data: The IEX stock exchange routes their traffic
through 61km of wound up fiber as a speed bump for traders, which
introduces 350 µs delay. See exchange.iex.io/about/speed-bump and
youtu.be/d8BcCLLX4N4?t=159. The minimal delay from that should be 61km/c
= 204 µs.They do not specify where the additional 146 µs delay comes
from (e.g. reduced speed of light inside the fiber, longer travel
distance, maybe even delay from the electric components that send and
receive the signal). – Socowi Commented Oct 27, 2022 at 20:04"
--
Fake news kills!
I may be contacted via the contact address given on my website:
www.macfh.co.uk
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 16:11 +0200
Re: Alternative for remote desktop connection "Alan K." <alan@invalid.com> - 2025-08-01 10:28 -0400
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-01 18:19 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 12:33 -0500
Re: Alternative for remote desktop connection "Alan K." <alan@invalid.com> - 2025-08-01 13:49 -0400
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-01 21:11 +0100
Re: Alternative for remote desktop connection NY <me@privacy.net> - 2025-08-02 16:29 +0100
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 18:26 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:45 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:58 +0200
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-02 16:35 +0200
Re: Alternative for remote desktop connection Graham J <nobody@nowhere.co.uk> - 2025-08-01 16:43 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:47 +0200
Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 09:02 -0700
Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 09:13 -0700
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-01 18:41 +0200
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:49 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 12:06 -0500
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-01 20:54 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-01 15:26 -0500
Re: Alternative for remote desktop connection Michael Logies <logies@t-online.de> - 2025-08-06 15:58 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-06 18:41 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-06 12:35 -0500
Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-01 17:32 -0700
Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-02 12:15 +0100
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:57 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 15:46 +0100
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 17:30 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-02 18:32 +0100
Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-02 19:53 +0200
Re: Alternative for remote desktop connection Paul <nospam@needed.invalid> - 2025-08-02 17:53 -0400
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-03 19:43 +0200
Re: Alternative for remote desktop connection Char Jackson <none@none.invalid> - 2025-08-03 20:41 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-04 11:55 +0100
Re: Alternative for remote desktop connection Char Jackson <none@none.invalid> - 2025-08-04 23:22 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-05 20:24 +0100
Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-04 12:57 +0200
Re: Alternative for remote desktop connection T <T@invalid.invalid> - 2025-08-03 23:10 -0700
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-04 15:37 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-02 15:54 +0200
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-02 16:40 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-02 19:56 -0500
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-03 20:36 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-03 18:11 -0500
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-04 11:34 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-04 14:06 -0500
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 08:59 +0200
Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-03 21:07 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-04 11:24 +0200
Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-04 10:50 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 09:01 +0200
Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-07 11:39 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:19 +0200
Re: Alternative for remote desktop connection Zaidy036 <Zaidy036@air.isp.spam> - 2025-08-04 16:25 -0400
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-06 09:03 +0200
Re: Alternative for remote desktop connection Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-08-06 20:55 +0100
Re: Alternative for remote desktop connection Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2025-08-06 21:00 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:22 +0200
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-07 15:20 +0200
Re: Alternative for remote desktop connection Philip Herlihy <nothing@invalid.com> - 2025-08-08 11:44 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-09 12:59 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-09 13:17 -0500
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-10 18:01 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-10 18:12 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-10 19:33 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-10 19:08 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-11 09:46 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:07 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 08:19 -0500
OT: Microsoft product (and service) naming (was: Re: Alternative for remote desktop connection) "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:36 +0100
Re: OT: Microsoft product (and service) naming "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 11:06 +0200
Re: OT: Microsoft product (and service) naming "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-10-20 10:48 +0100
Re: OT: Microsoft product (and service) naming "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 13:36 +0200
Re: OT: Microsoft product (and service) naming Frank Slootweg <this@ddress.is.invalid> - 2025-10-20 12:36 +0000
Re: Alternative for remote desktop connection "Carlos E.R." <robin_listas@es.invalid> - 2025-08-10 19:57 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-10 20:42 +0200
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-11 09:44 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 14:09 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 08:53 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 15:53 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 13:03 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-11 19:31 +0100
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:11 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-12 02:00 +0100
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-13 21:21 +0200
Re: Alternative for remote desktop connection The Horny Goat <lcraver@home.ca> - 2025-10-19 23:36 -0700
OT: ageing (was: Re: Alternative for remote desktop connection) "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-10-20 08:45 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:20 -0500
Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-12 12:35 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 14:16 -0500
Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-12 21:11 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 17:24 -0500
Re: Alternative for remote desktop connection Java Jive <java@evij.com.invalid> - 2025-08-13 05:10 +0100
Re: Alternative for remote desktop connection Paul <nospam@needed.invalid> - 2025-08-12 15:29 -0400
Re: Alternative for remote desktop connection Michael Logies <logies@t-online.de> - 2025-08-11 22:40 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:06 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:35 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-12 09:01 +0100
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-12 13:23 -0500
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-13 03:45 +0100
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-13 21:28 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-13 17:09 -0500
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-14 13:27 +0200
Re: Alternative for remote desktop connection "s|b" <me@privacy.invalid> - 2025-08-11 21:03 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-11 20:39 -0500
Re: Alternative for remote desktop connection rsutton <rsutton43@comcast.net> - 2025-08-12 07:49 -0400
Re: Alternative for remote desktop connection wasbit <wasbit@REMOVEhotmail.com> - 2025-08-13 09:26 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-13 11:39 +0200
Re: Alternative for remote desktop connection "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-08-13 12:13 +0100
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-13 18:33 +0200
Re: Alternative for remote desktop connection VanguardLH <V@nguard.LH> - 2025-08-13 12:52 -0500
Re: Alternative for remote desktop connection rsutton <rsutton43@comcast.net> - 2025-08-14 08:22 -0400
Re: Alternative for remote desktop connection Fokke Nauta <fnauta@solfon.nl> - 2025-08-14 16:00 +0200
csiph-web