Remotely control a Mac
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
Why do you need a client? Same question as with the server. Mac has everything that you need included. What's the purpose of replacing the built in and supported VNC client with a third party one?
I'm trying to remotely control a Mac with Windows. Microsoft's RDP client from the App Store didn't seem to work. Even after enabling screen sharing on the Mac, I couldn't use Microsoft RDC from my Windows workstation. But after downloading TightVNC, I could use that to control the Mac after enabling screen sharing.
-
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
Oh, so the issue is that you want Windows to have the VNC protocol handled natively. That's a Windows failing, not a Mac one. It's Windows lacking the client to connect to EVERYTHING that isn't Windows.
Macs come with the server, client AND the client for attaching to Windows, too. Apple actually does everything right here, it is Windows alone that is lacking.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
use vnc://x.x.x.x between Macs... I guess I just need to download an open source VNC client and see if that works...
Why do you need a client? Same question as with the server. Mac has everything that you need included. What's the purpose of replacing the built in and supported VNC client with a third party one?
I'm trying to remotely control a Mac with Windows. Microsoft's RDP client from the App Store didn't seem to work. Even after enabling screen sharing on the Mac, I couldn't use Microsoft RDC from my Windows workstation. But after downloading TightVNC, I could use that to control the Mac after enabling screen sharing.
Right, because an RDP client talks to RDP servers, not to VNC servers. Enabling VNC on the Mac would not be expected to make an RDP client see it.
-
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Which ones are you referring too? Most VNC is free not just free for personal use..
I'm saying why does it have to me the native Mac one? Tight VNC etc are open source (not sure if they have a Mac version) but I'm sure there are ones for mac
-
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
Oh, so the issue is that you want Windows to have the VNC protocol handled natively. That's a Windows failing, not a Mac one. It's Windows lacking the client to connect to EVERYTHING that isn't Windows.
Macs come with the server, client AND the client for attaching to Windows, too. Apple actually does everything right here, it is Windows alone that is lacking.
Now I see where you're talking about the failing... You can connect from a Mac with RDC because it knows how to handle a Windows PC. But you can't connect with RDC to a Mac because Microsoft's RDP program doesn't know how to handle an Apple PC.
Now I see.
-
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Which ones are you referring too? Most VNC is free not just free for personal use..
I'm saying why does it have to me the native Mac one? Tight VNC etc are open source (not sure if they have a Mac version) but I'm sure there are ones for mac
There were two parts... I didn't realize that Microsoft was at fault here, not Apple, since Apple has VNC natively built in but Microsoft RDC can't connect to Unix-like/Linux workstations.
I was hoping to use the Microsoft RDC tool to connect to the OSX workstations/servers after enabling screen sharing, since that is the tool all the other admins use (I use Terminals, used to use nRemoteNG). Too many remote tools on my workstation. Just trying to consolidate where I can.
-
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Which ones are you referring too? Most VNC is free not just free for personal use..
I'm saying why does it have to me the native Mac one? Tight VNC etc are open source (not sure if they have a Mac version) but I'm sure there are ones for mac
There were two parts... I didn't realize that Microsoft was at fault here, not Apple, since Apple has VNC natively built in but Microsoft RDC can't connect to Unix-like/Linux workstations.
I was hoping to use the Microsoft RDC tool to connect to the OSX workstations/servers after enabling screen sharing, since that is the tool all the other admins use (I use Terminals, used to use nRemoteNG). Too many remote tools on my workstation. Just trying to consolidate where I can.
Terminals has a native VNC client built-in.
-
@Kelly said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@aaronstuder said in Remotely control a Mac:
@BBigford If you know the right people the price is the same
I'm sure there are people just loading up VNC (free) and using it for business... we finally got all licensed compliant.
Just frustrating that Microsoft gives away their RDP client to Apple for free, but nothing that goes the other way for businesses to stay compliant.
There are free VNC tools, I would think some of the freebie VNC servers would work on macs and not just the apple built in server
There's Free, Personal (small scale business), and Enterprise (large scale business)... Free is for "individual, personal use", I'm guessing we wouldn't be allowed to use that because it's being used in a business setting.
It doesn't even have to have a wide range of functionality. I just need to be able to remotely connect and launch OSX Server (rarely).
Which ones are you referring too? Most VNC is free not just free for personal use..
I'm saying why does it have to me the native Mac one? Tight VNC etc are open source (not sure if they have a Mac version) but I'm sure there are ones for mac
There were two parts... I didn't realize that Microsoft was at fault here, not Apple, since Apple has VNC natively built in but Microsoft RDC can't connect to Unix-like/Linux workstations.
I was hoping to use the Microsoft RDC tool to connect to the OSX workstations/servers after enabling screen sharing, since that is the tool all the other admins use (I use Terminals, used to use nRemoteNG). Too many remote tools on my workstation. Just trying to consolidate where I can.
Terminals has a native VNC client built-in.
That is good to know. I had forgotten about that. I've only ever used it for RDP/Telnet/SSH. Hadn't even thought to check.
-
RoyalTS is a million times better than terminals. I think I paid $40 for it
-
@Jason said in Remotely control a Mac:
RoyalTS is a million times better than terminals. I think I paid $40 for it
Well I can't get the VNC protocol in Terminals working so I won't fight you on that one. Can't connect out to this stupid Mac via VNC in Terminals no matter what settings I input.
Error log in Terminals says: VncSharp.VncProtocolException: Unable to connect to the server. Error was: No connection could be made because the target machine actively refused it 192.168.70.173:5900
But the Mac doesn't have the firewall enabled.
-
@BBigford said in Remotely control a Mac:
@Jason said in Remotely control a Mac:
RoyalTS is a million times better than terminals. I think I paid $40 for it
Well I can't get the VNC protocol in Terminals working so I won't fight you on that one. Can't connect out to this stupid Mac via VNC in Terminals no matter what settings I input.
Error log in Terminals says: VncSharp.VncProtocolException: Unable to connect to the server. Error was: No connection could be made because the target machine actively refused it 192.168.70.173:5900
But the Mac doesn't have the firewall enabled.
Got it working... but there is some weirdness going on.
-
@BBigford said in Remotely control a Mac:
@scottalanmiller said in Remotely control a Mac:
@BBigford said in Remotely control a Mac:
@scottalanmiller I was just trying to get around having to load another program on my Windows workstation, and instead just run the mstsc program for everything.
Oh, so the issue is that you want Windows to have the VNC protocol handled natively. That's a Windows failing, not a Mac one. It's Windows lacking the client to connect to EVERYTHING that isn't Windows.
Macs come with the server, client AND the client for attaching to Windows, too. Apple actually does everything right here, it is Windows alone that is lacking.
Now I see where you're talking about the failing... You can connect from a Mac with RDC because it knows how to handle a Windows PC. But you can't connect with RDC to a Mac because Microsoft's RDP program doesn't know how to handle an Apple PC.
Now I see.
Exactly. Windows has an RDP server, Apple and most Linux have VNC servers (as do KVM, Xen and other tools.) Windows has an RDP client. Mac and Linux come with RDP, VNC and X clients.
-
@BBigford said in Remotely control a Mac:
There were two parts... I didn't realize that Microsoft was at fault here, not Apple, since Apple has VNC natively built in but Microsoft RDC can't connect to Unix-like/Linux workstations.
Well, pretty much all Linux desktops will do RDP servers. You don't normally because it's not that great of a protocol. But if you want it, it's one command line instruction away. I've used RDP to manage Linux desktops plenty of times. It's Mac alone that doesn't build it in, it's only that Linux doesn't turn it (or VNC) on by default because X has been there for three decades already.
