I need to share my Windows screen so that someone else who is only on an iPhone can operate my screen (mouse & keyboard entries for example).
For those of you who have performed that sharing task, how do you do it?
What are your suggestions for the most compatible software to do it?
Thanks!
On 11/20/2024 10:17 PM, Andrews wrote:
I need to share my Windows screen so that someone else who is only on an
iPhone can operate my screen (mouse & keyboard entries for example).
For those of you who have performed that sharing task, how do you do it?
What are your suggestions for the most compatible software to do it?
Thanks!
A google search resulted in the following and no I have not tried either
of these methods.
To remotely control a Windows PC from an iPhone, you can use the
Microsoft Remote Desktop app or Splashtop:
Microsoft Remote Desktop
1. Install the app from the App Store or iTunes
2. Open the app and give it the necessary permissions
3. Tap the plus (+) button and select Add PC
4. Type the name of the PC and add .local at the end
5. Enter the account name you want to use
6. Type a name in the Friendly Name field
7. Tap Save
8.Tap the icon for the computer you want to access
Splashtop
1. Install the Splashtop app from the App Store
2. Set up Splashtop Streamer on your computer
3. Log in to your Splashtop account
4. Open the Splashtop app on your iPhone and click on the computer you
want to access
In summary, besides the fact I still need to find a way for her to share my desktop without me having to create an account on someone's server on the Internet, I did find an interesting way to COMPLETELY TAKE OVER someone's
PC without having to create an account on someone's server on the net.
Andrew wrote:
[snip]
In summary, besides the fact I still need to find a way for her to
share my
desktop without me having to create an account on someone's server on the
Internet, I did find an interesting way to COMPLETELY TAKE OVER someone's
PC without having to create an account on someone's server on the net.
Remote Desktop is designed to take over the remote machine.˙ It is not a screen-sharing application, so it's not appropriate to your needs.
It's also designed for use in a security-conscious environment where
users have passwords.˙ It's more normal application is for users to gain access to a Microsoft Server, where several users can access the server simultaneously and each has their own working environment.˙ Ordinarily
the Remote Desktop service is only available on the Professional or Enterprise versions of Microsoft's desktop operation systems.
What you appear to need is a Screen-Sharing application.˙ These are available from several sources, called generically Virtual Network Connection.˙ Names like RealVNC, TightVNC, and UltraVNC come to mind.
For your application, the server component is installed on the Windows
PC (any flavour of Windows), you open a port in your router to allow the incoming connection and you need a static public IP address or a Dynamic
DNS registration; and your internet connection must not involve GCNAT.
The client device - the smartphone - has the client component installed.
˙As you have found, the various app stores may give the client
misleading names - others here may be able to say what names are
actually used.˙ The logic of using a smartphone with a tiny screen to
see a typical large screen of a desktop PC beats me; but where the
client is another desktop PC with a big screen it works well.
Each flavour of VNC may have strange limitations.˙ Most often
encountered is that the connection stops when the host PC pops up a UAC (User Access Control) window so the user at that PC has to "OK" the
prompt before the connection resumes.˙ But for screen sharing with a
user who is present and watching the activity it is not a real problem.
It does become a real problem where VNC is used for remote access to an unattended PC - typically when you are away from home and require access
to something on your PC at home.
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud.˙ There no need to open any special ports in
your router.˙ So the Teamviewer company knows what you are doing and
when.˙ I used this in the past when it was free to home users for
occasional use, but now it has stopped working for me.˙ There is an expensive paid-for version which is more realistically priced for a
computer support business.˙ It's clearly used by the scammers who claim
to be from Microsoft while they empty your bank account.
In summary, besides the fact I still need to find a way for her to share my >> desktop without me having to create an account on someone's server on the
Internet, I did find an interesting way to COMPLETELY TAKE OVER someone's
PC without having to create an account on someone's server on the net.
Remote Desktop is designed to take over the remote machine. It is not a screen-sharing application, so it's not appropriate to your needs.
It's also designed for use in a security-conscious environment where
users have passwords. It's more normal application is for users to gain access to a Microsoft Server, where several users can access the server simultaneously and each has their own working environment. Ordinarily
the Remote Desktop service is only available on the Professional or Enterprise versions of Microsoft's desktop operation systems.
What you appear to need is a Screen-Sharing application. These are available from several sources, called generically Virtual Network Connection. Names like RealVNC, TightVNC, and UltraVNC come to mind.
For your application, the server component is installed on the Windows
PC (any flavour of Windows), you open a port in your router to allow the incoming connection and you need a static public IP address or a Dynamic
DNS registration; and your internet connection must not involve GCNAT.
The client device - the smartphone - has the client component installed.
As you have found, the various app stores may give the client
misleading names - others here may be able to say what names are
actually used. The logic of using a smartphone with a tiny screen to
see a typical large screen of a desktop PC beats me; but where the
client is another desktop PC with a big screen it works well.
Each flavour of VNC may have strange limitations. Most often
encountered is that the connection stops when the host PC pops up a UAC (User Access Control) window so the user at that PC has to "OK" the
prompt before the connection resumes. But for screen sharing with a
user who is present and watching the activity it is not a real problem.
It does become a real problem where VNC is used for remote access to an unattended PC - typically when you are away from home and require access
to something on your PC at home.
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud. There no need to open any special ports in
your router. So the Teamviewer company knows what you are doing and
when.
I used this in the past when it was free to home users for
occasional use, but now it has stopped working for me. There is an expensive paid-for version which is more realistically priced for a
computer support business. It's clearly used by the scammers who claim
to be from Microsoft while they empty your bank account.
[snip]
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud. There no need to open any special ports in
your router. So the Teamviewer company knows what you are doing and
when.
I used this in the past when it was free to home users for
occasional use, but now it has stopped working for me. There is an >expensive paid-for version which is more realistically priced for a
computer support business. It's clearly used by the scammers who claim
to be from Microsoft while they empty your bank account.
Graham J wrote on Mon, 25 Nov 2024 08:37:30 +0000 :
Thanks for explaining that Microsoft Remote Desktop (which is now named "Windows App Mobile" on the Apple App Store and "Remote Desktop" on the Google App Store) is mostly for the security-conscious environments.
Since I don't live in the slums, I don't put passwords or biometrics on anything since I happen to not be afraid of the people living with me.
I never understood why so many people live in such constant abject fear of everyone around them that they feel they need constant biometric locking.
For your application, the server component is installed on the Windows
PC (any flavour of Windows), you open a port in your router to allow the
incoming connection and you need a static public IP address or a Dynamic
DNS registration; and your internet connection must not involve GCNAT.
Hmm... I have Windows 10, and while I'm no router expert, there's a section for "port forwarding" on my router, and I have a static IP address from my WISP, and, um... er... GCNAT? I have to look that up. Gimme a sec....
<https://duckduckgo.com/?va=d&t=hc&q=what+is+gcnat&ia=web>
Carrier-grade NAT
Carrier-grade NAT, also known as large-scale NAT, is a type of
network address translation used by ISPs in IPv4 network design.
<https://en.wikipedia.org/wiki/Carrier-grade_NAT>
I have no idea if my tiny WISP has Carrier-grade NAT but I sent an email asking them so I'll let you know if they do use carrier grade NAT on WISP.
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud. There no need to open any special ports in
your router. So the Teamviewer company knows what you are doing and
when.
Ah! I was wondering *WHY* I had to do port forwarding on my router to use Microsoft Remote Desktop. I guess what you're explaining is that if I do
port forwarding, the server company doesn't know what I'm doing - but if I don't have to do port forwarding on my router, then the sharing company
does know what I'm doing. Is that right?
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic >>cop) facility in the cloud. There no need to open any special ports in >>your router. So the Teamviewer company knows what you are doing and
when.
FYI, if you use TeamViewer within a LAN, the traffic stays within the LAN and doesn't go to/from the TeamViewer server. That could be important to someone.
On Mon, 25 Nov 2024 08:37:30 +0000, Graham J <nobody@nowhere.co.uk> wrote:
[snip]
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud. There no need to open any special ports in
your router. So the Teamviewer company knows what you are doing and
when.
FYI, if you use TeamViewer within a LAN, the traffic stays within the LAN and doesn't go to/from the TeamViewer server. That could be important to someone.
We are not afraid of the people we
live with, but of the strangers that may pass by one day, and of those
on the cloud.
Surely you lock your car on the street in NY, or your house door on a city.
I have no idea if my tiny WISP has Carrier-grade NAT but I sent an email
asking them so I'll let you know if they do use carrier grade NAT on WISP.
You don't have to ask. You just find out by looking at your computer
and/or your router, or your phone.
If the internet address on your router, or your internet facing machine,
is a private address, like 10.*.*.*, you are on GNAT.
Ah! I was wondering *WHY* I had to do port forwarding on my router to use
Microsoft Remote Desktop. I guess what you're explaining is that if I do
port forwarding, the server company doesn't know what I'm doing - but if I >> don't have to do port forwarding on my router, then the sharing company
does know what I'm doing. Is that right?
That's a secondary effect, not the reason.
On 2024-11-26 01:19, Char Jackson wrote:
On Mon, 25 Nov 2024 08:37:30 +0000, Graham J <nobody@nowhere.co.uk> wrote: >>
[snip]
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic
cop) facility in the cloud. There no need to open any special ports in
your router. So the Teamviewer company knows what you are doing and
when.
FYI, if you use TeamViewer within a LAN, the traffic stays within the LAN and
doesn't go to/from the TeamViewer server. That could be important to someone.
In theory, you only need the server to initiate the conversation. After >that, the conversation might be P2P.
On Tue, 26 Nov 2024 02:41:45 +0100, "Carlos E.R." <robin_listas@es.invalid> wrote:
On 2024-11-26 01:19, Char Jackson wrote:
On Mon, 25 Nov 2024 08:37:30 +0000, Graham J <nobody@nowhere.co.uk> wrote: >>>
[snip]
Another screen-sharing app is TeamViewer, and this will work through
CGNAT since both client and server component talk to a central (traffic >>>> cop) facility in the cloud. There no need to open any special ports in >>>> your router. So the Teamviewer company knows what you are doing and
when.
FYI, if you use TeamViewer within a LAN, the traffic stays within the LAN and
doesn't go to/from the TeamViewer server. That could be important to someone.
In theory, you only need the server to initiate the conversation. After
that, the conversation might be P2P.
I've seen that suggestion before, but I don't know how that would work. It seems
like you'd be back to needing port forwarding.
Carlos E.R. wrote on Tue, 26 Nov 2024 02:39:02 +0100 :
We are not afraid of the people we
live with, but of the strangers that may pass by one day, and of those
on the cloud.
I am using the word "slums" to make a point about WHY people lock their devices when it means they're deathly afraid of everyone around them.
I care about privacy as much as the next person cares about privacy.
And I care about security too.
But I don't lock my devices because I'm not afraid of the people who have physical access to them. Only people who live in abject fear lock them.
Surely you lock your car on the street in NY, or your house door on a city.
NY is the slums. So, sure, I'll lock my car in NY but at home, I don't live in the slums so when my car is parked in my driveway, the windows are open.
Only people who live in slums need to lock their computers every second. That's because they don't trust anyone who lives in their own home.
I have no idea if my tiny WISP has Carrier-grade NAT but I sent an email >>> asking them so I'll let you know if they do use carrier grade NAT on WISP. >>You don't have to ask. You just find out by looking at your computer
and/or your router, or your phone.
If the internet address on your router, or your internet facing machine,
is a private address, like 10.*.*.*, you are on GNAT.
Thanks. I never heard of CGNAT before but my IP address is not a private address so I guess I'm normal - although I'm on a WISP but it's the same.
Ah! I was wondering *WHY* I had to do port forwarding on my router to use >>> Microsoft Remote Desktop. I guess what you're explaining is that if I do >>> port forwarding, the server company doesn't know what I'm doing - but if I >>> don't have to do port forwarding on my router, then the sharing company
does know what I'm doing. Is that right?
That's a secondary effect, not the reason.
Thanks.
Back to the topic, I installed TeamViewer but there are so many variations, I'm not sure which variation is the one for what I want to do with my PC.
All I want to do is share my PC with someone on a mobile device such that
the person on the mobile can see my screen & operate the cursor & keys.
Which TeamViewer is that?
https://www.teamviewer.com/en-us/download/windows/
1. TeamViewer QuickSupport (If you want to receive support:)
2. TeamViewer full client (If you want to provide support)
3. TeamViewer Host (If you want to set up unattended access to a device)
4. TeamViewer MSI Package (If you want to mass deploy TeamViewer)
5. TeamViewer Meeting (If you want to join or start a meeting)
Which of those allows a mobile device to see my screen and operate the
mouse and keyboard so that they can do stuff with an account on my PC?
Only people who live in slums need to lock their computers every second.
That's because they don't trust anyone who lives in their own home.
Your usual rhetoric. Again, we are not afraid of the people that live
with us, but of those that don't.
And then, keeping privacy can be absolute. NO ONE, including those in
our houses, need to pry what we do.
And then, you forget that one may live alone, and yet follow recommended security and privacy practices. We consider silly not to use login/pass
even at home. Security in computing is multilayered, any expert will
tell you that. You don't rely solely on the house key.
Thanks. I never heard of CGNAT before but my IP address is not a private
address so I guess I'm normal - although I'm on a WISP but it's the same.
It would be rare in the USA for an ISP to use CGNAT, because the USA reserved a huge pool of IPv4 addresses. A small cheap provider might use
it, though. On countries where the pool is scarce (and instead of using IPv6) they would have to use CGNAT.
Which TeamViewer is that?
https://www.teamviewer.com/en-us/download/windows/
1. TeamViewer QuickSupport (If you want to receive support:)
2. TeamViewer full client (If you want to provide support)
3. TeamViewer Host (If you want to set up unattended access to a device)
4. TeamViewer MSI Package (If you want to mass deploy TeamViewer)
5. TeamViewer Meeting (If you want to join or start a meeting)
Which of those allows a mobile device to see my screen and operate the
mouse and keyboard so that they can do stuff with an account on my PC?
It has been some time since I looked. The problem is finding out what
they call client and what server.
You want to be "supported", ie, you want your computer to be used by
someone (so 1). The person in the phone connects to you and manipulates
your computer, ie, gives support (so 2).
I would also suggest googling "alternatives to teamviewer". Teamviewer
is the best known, but there are others. I can not recommend any of them from personal experience, though.
Carlos E.R. wrote on Tue, 26 Nov 2024 13:33:33 +0100 :
It would be rare in the USA for an ISP to use CGNAT, because the USA
reserved a huge pool of IPv4 addresses. A small cheap provider might use
it, though. On countries where the pool is scarce (and instead of using
IPv6) they would have to use CGNAT.
Thanks for the information about Carrier-Grade NAT as I had never heard of
it before someone mentioned it and I looked it up to see what it was.
My IP address comes over the air from a few miles away and is static.
On 2024-11-26 04:05, Char Jackson wrote:
On Tue, 26 Nov 2024 02:41:45 +0100, "Carlos E.R." <robin_listas@es.invalid> >> wrote:
On 2024-11-26 01:19, Char Jackson wrote:
On Mon, 25 Nov 2024 08:37:30 +0000, Graham J <nobody@nowhere.co.uk> wrote: >>>>
[snip]
Another screen-sharing app is TeamViewer, and this will work through >>>>> CGNAT since both client and server component talk to a central (traffic >>>>> cop) facility in the cloud. There no need to open any special ports in >>>>> your router. So the Teamviewer company knows what you are doing and >>>>> when.
FYI, if you use TeamViewer within a LAN, the traffic stays within the LAN and
doesn't go to/from the TeamViewer server. That could be important to someone.
In theory, you only need the server to initiate the conversation. After
that, the conversation might be P2P.
I've seen that suggestion before, but I don't know how that would work. It seems
like you'd be back to needing port forwarding.
I don't know (remember) exactly how it works, but it is done with VoIP too.
<https://www.reddit.com/r/HomeNetworking/comments/d6r0h0/how_do_apps_like_teamviewer_get_around_port/>
<https://en.wikipedia.org/wiki/UDP_hole_punching>
<https://en.wikipedia.org/wiki/NAT_traversal>
Troll, you get
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 4 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 190:28:23 |
| Calls: | 62 |
| Files: | 21,500 |
| Messages: | 70,957 |