Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Newsgroups | uk.comp.homebuilt, comp.misc, uk.comp.misc |
| Subject | Re: Remote desktop Protocol issue. |
| Followup-To | comp.misc |
| Date | 2023-03-03 10:24 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnu03ioi.buj.dan@djph.net> (permalink) |
| References | (3 earlier) <tto549$o2f$1@dont-email.me> <k6a7tsFe3snU1@mid.individual.net> <slrnu01ih8.9it.fos@ma.sdf.org> <ttseko$1hk7$1@news.cyber23.de> <ttsfih$1hk7$2@news.cyber23.de> |
Cross-posted to 3 groups.
Followups directed to: comp.misc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ["Followup-To:" header set to comp.misc.] On 2023-03-03, SH wrote: > [...] > P.S. on a hunch, I rdp'ed into a win10 box from the Win7 box and did a > netstat -anb as I knew the IP address and port no of teh win10 box... > > > The result is > > TCP 192.168.0.110:49213 192.168.0.233:3389 ESTABLISHED > mstsc.exe > > so it seems the win7 box is using port 49213 and the process mstsc.exe > for RDP? mstsc is "Microsoft Terminal Service Client" (i.e. the remote desktop client software). In addition, nearly all client applications will ask for a random source port when initiating a connection, which is managed by your OS' underlying network stack. I forget the exact range for Windows (might be 30,000 - 50,000); but suffice to say that in general terms any currently free port in that range is fair game at some point. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmQByxEACgkQbWVw5Uzn KGA/fBAAo3NgdvR5ntZAywkElKThSUXvszXzgiRIPLnDLp78nKSfgBUa9PbQQxao 8c7QDhQs7T8qdvZxbEdUpF0O+zd2WAy6tWKe+xYD5RT9C1/Pfr/qamXHIgRUWVpq ShpCVj2eLOoeb7kA6j7endkSU3rkwwgsorVwDB561zbIJMVUGdzTATfLmvKNjNZc l9SpDLiAGjys9aB7JupH1bLNTy7BNRist3yGjJajZknT8T6uR4JW7ccrhtDaqt0W NpbygOF2nrhgKtXNvp+F9qnFauBZVuGBBPf4Hq4iZE2BGTRQS0jBqPmojuz6FD09 4e0CUmlOTHjf5GNvVt01+z4Zr8/6+TsycVQ/Llj3zC7I4betGz0KZdjLJs5+1EJx Yo/RcpL66kOQbOKYZkcKzB0W5miCHzKsyAKId7DMzMstNtJ71CI1WdEz4jHy2AS/ YpPoH3+GsCZz2pIT5cmg9zfWsDym/u57TgOEpwHxRwsTt26Lg55FTFgtGswUdeVY ZVGpB+0SFn8yljuXb+5o5Vmq1N132dBXPYUMz9STTSBXWmnCK06tBiqcYPcmvHkq luYhGTaXSzKk4YPfGrZp6CXCTsqhmiHj8mwhvSODtOxGu3hCbGyHKmw63PGDJxrx wmuk3CCYYk0J6P4SnvoiHTwwvpA6KMKiYEd1s6YBN8yYxaCIxns= =Wrpq -----END PGP SIGNATURE----- -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
Back to uk.comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Remote desktop Protocol issue. SH <i.love@spam.com> - 2023-02-27 23:18 +0000
Re: Remote desktop Protocol issue. "Jeff Gaines" <jgnewsid@outlook.com> - 2023-02-28 08:39 +0000
Re: Remote desktop Protocol issue. Adrian Caspersz <email@here.invalid> - 2023-02-28 10:24 +0000
Re: Remote desktop Protocol issue. SH <i.love@spam.me> - 2023-02-28 18:55 +0000
Re: Remote desktop Protocol issue. SH <i.love@spam.com> - 2023-03-01 18:22 +0000
Re: Remote desktop Protocol issue. Sylvia Else <sylvia@email.invalid> - 2023-03-02 11:11 +1100
Re: Remote desktop Protocol issue. fos@sdf.org - 2023-03-02 16:09 +0000
Re: Remote desktop Protocol issue. Sylvia Else <sylvia@email.invalid> - 2023-03-03 11:57 +1100
Re: Remote desktop Protocol issue. SH <i.love@spam.me> - 2023-03-03 09:28 +0000
Re: Remote desktop Protocol issue. SH <i.love@spam.me> - 2023-03-03 09:44 +0000
Re: Remote desktop Protocol issue. SH <i.love@spam.me> - 2023-03-03 09:48 +0000
Re: Remote desktop Protocol issue. Sylvia Else <sylvia@email.invalid> - 2023-03-03 22:57 +1100
Re: Remote desktop Protocol issue. David <wibble@btinternet.com> - 2023-03-05 15:28 +0000
Re: Remote desktop Protocol issue. Dan Purgert <dan@djph.net> - 2023-03-03 10:24 +0000
Re: Remote desktop Protocol issue. Bruce Horrocks <07.013@scorecrow.com> - 2023-03-04 12:39 +0000
Re: Remote desktop Protocol issue. Adrian Caspersz <email@here.invalid> - 2023-03-02 07:55 +0000
Re: Remote desktop Protocol issue. Raj Kundra <raj@kundracomputers.co.uk> - 2023-03-02 13:34 +0000
Re: Remote desktop Protocol issue. scott@alfter.diespammersdie.us - 2023-03-03 18:00 +0000
csiph-web