Ssh "remote desktop"

Hi, so I've spent 5 days straight trying to figure this out...
Presently I have an authentication key set up and it works perfectly locally. I have followed these tutorials all with the same results:
http://mac101.net/content/how-to/secure-remote-access-to-your-mac-using-ssh-part -1/
http://www.g-loaded.eu/2005/11/10/ssh-with-keys/
http://www.panix.com/help/sw.macosx-ssh.html
and a few more...
I can login locally just fine.
I type ssh [email protected]
hit enter, then I get the warning banner and the publickey somehow logs me in.
When I login using the IP address dynamically assigned by my ISP I get this:
*XXXXs-MacBook-Pro:~ XXXX$ ssh -p 22 [email protected]*
*DD-WRT v24 mini (c) 2008 NewMedia-NET GmbH*
*Release: 07/27/08 (SVN revision: 10011)*
*Permission denied (publickey).*
I think I should be getting the WARNING banner message before I get the passcode prompt (like it does when I login locally) but I don't -- I just the passphrase prompt. I type that in and it says something about DD-WRT (my router) and says "Permission denied (publickey)"
I've set up everything in the router to be port 22 just for testing. I've got port forwarding on. I've got the public key set in the router...
I know I should be doing this with an IP statically defined by ISP, but I can still set this up once for a few days to test with a dynamic IP, right?
I'm really stumped.

Camelot:
Ah yes. I did have [email protected] for the user originally but was trying anything to see if that was the problem -- thanks for the clarification.
edclange:
That's it. I found that earlier, but wasn't sure what to do with it. Thanks!
Of course, I've got a new reason not to be able to log on. I will look into it and post my findings.
new err:
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX.
Please contact your system administrator.
Add correct host key in /Users/XXXX/.ssh/known_hosts to get rid of this message.
Offending key in /Users/XXXX/.ssh/known_hosts:4
RSA host key for [XX.XXX.XX.XXXX]:2222 has changed and you have requested strict checking.
Host key verification failed.
_I've gotta go teach kids how to swim now but I'll be back this evening... disabling ssh services til then..
This has been a huge help so far THX!

Similar Messages

Remote Desktop 3.3 update breaks SSH connectivity

Since updating to Remote Desktop Admin 3.3, I am no longer able to use ARD over a SSH tunnel.
This is a serious bug - especially since there is no easy way to rollback to the previous version.
I would strongly recommend against running this update if you ever need to work in this way.

This is since the screen sharing port was set to 5900 in the update. Changed it to my desired port and all is well!

Rdp://full%20address=s: IP or DNS Name is not user friendly... Can rdp:// IP or DNS Name be assumed as the full address in Microsoft Remote Desktop?

We would like to request Microsoft Remote Desktop (MRD) to behave the same as the open source CoRD.app on OS X with respect URL resolution.
Example:MRD will resolve from Terminal rdp://full%20address=s:<IP or DNS Name>, but not rdp://<IP or DNS Name>
As the OS will respect any of the following protocols in Terminal or browser:
afp://<username>@<IP or DNS Name>
cifs://<username>@<IP or DNS Name>
ftp://<username>@<IP or DNS Name>
ftps://<username>@<IP or DNS Name>
http://<username>@<IP or DNS Name>
https://<username>@<IP or DNS Name>
smb://<username>@<IP or DNS Name>
ssh://<username>@<IP or DNS Name>
vnc://<username>@<IP or DNS Name>
(<username> can be omitted to force authentication at connection) it seems slightly redundant to force "full%20address=s:" in the URL.
Can Version 8.0.1.6 be modified address this request?
What is the proper way to report an enhancement request or bug?
Thank you for your consideration.

Hi,
From your description it appears that you want to modify the pattern for assigning the rdp full address but this doesn’t support as per your requirement. That is the default string which we need to have for passing full address.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to configure CISCO ASA 5510 for internal remote desktop ?

Helo,I have a client that want to install new ASA (5510) in their network.
and then I did some experiment to implement it. the topology is like this :
--------configuration---------
2800 router :
interface FastEthernet0/0
ip address 172.16.1.1 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 192.168.11.3 255.255.255.0
duplex auto
speed auto
ip route 192.168.12.0 255.255.255.0 172.16.1.2
1841 router :
interface FastEthernet0/0
ip address 172.16.1.2 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 192.168.12.1 255.255.255.0
duplex auto
speed auto
ip route 0.0.0.0 0.0.0.0 172.16.1.1
ASA 5510 :
: Saved
: Written by enable_15 at 19:21:31.639 UTC Mon Sep 13 2010
ASA Version 8.2(1)
hostname ciscoasa
enable password **** encrypted
passwd ***** encrypted
names
name 192.168.12.0 Branch
dns-guard
interface Ethernet0/0
shutdown
no nameif
no security-level
no ip address
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.11.1 255.255.255.0
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
interface Management0/0
shutdown
no nameif
no security-level
no ip address
management-only
boot system disk0:/asa821-k8.bin
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list inside_access_in extended permit ip 192.168.11.0 255.255.255.0 Branch 255.255.255.0
access-list inside_access_in extended permit ip 192.168.11.0 255.255.255.0 any
access-list inside_access_in extended permit ip Branch 255.255.255.0 192.168.11.0 255.255.255.0
tcp-map mssmap
synack-data allow
invalid-ack allow
seq-past-window allow
urgent-flag allow
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-621.bin
asdm location Branch 255.255.255.0 inside
no asdm history enable
arp timeout 14400
static (inside,inside) 192.168.11.2 192.168.11.2 netmask 255.255.255.255
static (inside,inside) 192.168.12.2 192.168.12.2 netmask 255.255.255.255
access-group inside_access_in in interface inside
route inside Branch 255.255.255.0 172.16.1.1 1
timeout xlate 3:00:00
timeout conn 10:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 0.0.0.0 0.0.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username ***** password ***** encrypted
class-map mymap
match access-list inside_access_in
class-map inspection_default
match default-inspection-traffic
policy-map global_policy
class inspection_default
inspect ftp
inspect h323 h225
inspect h323 ras
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
policy-map myPolicy
class mymap
set connection advanced-options mssmap
service-policy global_policy global
service-policy myPolicy interface inside
prompt hostname context
Cryptochecksum:a605d94f29924e5267644dd0f4476145
: end
I can successfully ping from host 192.168.12.2 to 192.168.11.2, but I can't do remote desktop from those host.
then I use wireshark to capture packet in my computer and it says that TCP ACKed Lost Segment.
"1373","164.538081","192.168.11.2","192.168.12.2","TCP","47785 > ms-wbt-server [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=2"
"1374","164.538993","192.168.12.2","192.168.11.2","TCP","[TCP ACKed lost segment] ms-wbt-server > 47785 [RST, ACK] Seq=1 Ack=1407706213 Win=0 Len=0"
I can guarantee that both computers are remote desktop enabled and all firewall have been disabled.
please help, any suggest would be great .
thanks .
sincerley yours
-IAN WIJAYA-

ear Ian_benderaz,
Thank god i am not alone on this ,
Me too having the exact same problem , i can ping to the host ,but no remote desktop .
Somebody please help me on this , how enable remote desktop on asa 5505
Thanks

How can I remotely access my computer from a different location on Apple Remote Desktop?

I downloaded Apple Remote Desktop and am trying to access our computer at our church that is in the auditorium and work on slides for ProPresenter from my office which is on a different network. The Mac Pro, which is in the auditorium, is connected to a Netgear wireless router. I would also want to be able to have access to observe and control the screen on the Mac Pro whether I am in my office or at my house. I have tried everything from going to portforward.com, followed those instructions, did port forwarding, used ipchicken.com to get my external IP and made sure that the Mac Pro had a static internal IP address and made sure the computer had access for remote management. Any help to resolve this issue would be greatly appreciated! Works fine when it is on the same wireless network, but I need access being on a different wireless network. Thanks!

Hi austinmac14,
So the steps listed bellow assume some things. They assume that the Airport Extreme Router your configuring is connected directly to the internet connection. And that the Airport Extreme is the only router between your computers and the internet.
That means we're talking about say a DSL modem plugged directly into the Airport Extreme, or a cable modem. in ether case, this assumes that said modem, is not acting as an internet router.
If your modem has multiple ethernet ports on it, or has a little antenna sticking out of it, then your modem is probable also a router, and these steps listed bellow will probable not work.
Also these steps are so one person, can connect to one computer at your work.
Open Airport Utility:
go to the dock
Click on the finder
go to the menu bar
Click on the "Go" menu
Chose "Utilities" from the "Go" Menu
double Click on "AirPort Utility"
Access the Base Station:
Double Click on your Airport Extreme BaseStation that is your internet connection router.
a new window should pop up with your Airport Base Station as the Window Name
Configure Static Address for the computer you want to connect to via ARD:
Click on the internet Icon from the toolbar
Click on the "DHCP" tab
For "DHCP Reservations:" Click on the "+" button
For the "Description" put "ARD"
For "Reserve Address by:" set "DHCP Client ID"
Click the "Continue" button
For "DHCP Client ID:" set "ARD"
write down the number in "IPv4" address field
Click the "Done" Button
Configure routing to ARD computer:
Click on the "Advanced" icon from the tool bar.
Click on the "Port Mapping" tab
Click on the "+" button
for "Service:" Chose "Apple Remote Desktop"
for "Private IP Address:" copy the exact IP address you wrote down in step "3. 8)"
Click the "Continue" button
Click the "Done" button
Click the "+" button
For the pulldown menu "Service:" Chose "Remote Apple Events"
for "Private IP Address:" copy the exact IP address you wrote down in step "3. 8."
Click the "Continue" button
Click the "Done" button
Click the "+" button
For the pulldown menu "Service:" Chose "Remote Login - SSH"
for "Private IP Address:" copy the exact IP address you wrote down in step "3. 8."
Click the "Continue" button
Click the "Done" button
Click the "Update" button.
wait for the Airport Extreme to update, and for your computer to reconnect to the airport extreme. (make sure you can load and browse websites.)
Configure the ARD computer to use the correct IP address:
Go to the computer you want to be able to remotely connect to
On that computer, Go to the menu bar
Chose the "Apple" menu bar
Chose "System Preferences…"
Click on the "Show All" button
Click on the "Network" icon
For the active network connection, (the connection on the left side with the green dot), click on it
Clock on the "Advanced…" button
Click on the "TCP/IP" tab
for the "DHCP Cient ID: field put "ARD".
Click the "OK" button
Click the "Apply" buttonNOTE: Under "Status" you should see "(connection name) is connected to (airport base station name) and has the IP address (IP address)." the "(IP address)" address displayed should match the IP address you wrote down in step "3. 8."
Find out what your public internet IP address is.
On the computer you wish to connect to over the internet, gotohttp://whatismyipaddress.com/
when the web page loads, you should see "IP Information:" fallow by a number like 192.168.0.1, write down what ever number it is.
At this point you should be able to connect to the computer remotely
connect to the internet from another location.
open Apple Remote Desktop
go to the file menu
chose connect to computer using ip address
set the address to the address to the IP address you wrote down for step 6. 2.
use the same password as you used to connect to the computer at work using ARD.
So here the catch. If your router gets reset... well then your going to have to configure it again. Also all the same rules you have to connect to the computer at work, also apply to connecting to the computer from over the local network. That means your computer need to be on or sleeping. And if it's sleeping it need to be configure to wake for network access.
Also some network connections change. When it comes to internet connections, some connections are static IP, while other connections are DHCP. If your connection is static... great! if it's DHCP, your address may change. If it dose.. well then your ability to connect will break. And then you'd have to do step 6 & 7 again.
Of corse there are ways around this. But that's kind of another conversation.
Some internet locations may block your ability to connect to your computer at work. This is very common at schools, and companies. Basically any place that tries to control your ability to browse the internet, may block remote access to computers; because a remote computer would completely by pass their web filter.
ALSO there is an easier option. As far as setup. There are programs designed to make remotely accessing your mac as easy as possible. For instance there is LogMeIn or Slack. With both of these programs, it's simple. make sure your computer is always on. Then install the software. Create an account with the service. And then you can connect to the computer almost any where by going to their website.
This option requires no router configuration. It handles DHCP. It's designed to work in as many locations as possible.

How can I deploy my AAMEE without Apple Remote Desktop?

Hi everyone,
I created a build for Adobe CS6 Production Premium for Mac with the serial number embedded, along with the current updates. All is well with that; however, this is the issue that I am having:
I have tried to test the build on a local machine (the computer I created the build on) and was able to install the package with no issues; however, when I try to deploy build onto a networked machine, it doesn't work.
I have read through the AAMEE Reference Guide and have read (if I am not mistaken) that for CS6, you can only deploy an AAMEE build through Apple Remote Desktop onto multiple machines. I have also read that you would need Apple Remote Desktop on all of the machines you want the build to deploy on.
If that is case, if I have read the guide correctly, what is the point of deploying the build through a network if you have to still install ARD onto all the machines you want the software one? How can you get around this to be able to deploy your AAMEE successfully onto a network on machines?
When I tried it last night on one network Mac with ARD, I received the error message for "Validating packages...". I'm not sure what that means because the build works perfectly on local machine.
Any ideas would help as far as deploying the build on a network without using ARD, or really, just a simpler alternative that works?
PLEASE HELP.
Thanks.

Hi,
You can deploy package using any of these tools - ARD, SSH, Casper suite, Absolute manage, Land desk..and may be more but we have only tried these.
We have mentioned ARD as an example, but other standard tools can be very well used for deploying package. and there is no need to have ARD installed on all machines where you want to deploy the package, but only on admin machine.
can you please let me know - which client OS are you trying to deploy the package and whether the client machine is logged or logged in? please forward install.log if you are facing the error.
thanks,
Rahul | [email protected]

Remote Desktop and the various VNCs

I've used VNC and Remote Desktop on Windows for a while and love them dearly. I was ecstatic when I picked up my mini in August and found that Tiger's ARD included VNC support.
But it's driving me up the bloody wall.
My laptop is a windows machine, so I've used VNC and TightVNC to connect to it. TightVNC is much faster but either one will eventually choke and then I can't reconnect until I physically disable/enable remote desktop access on the Mac.
Are any companies out there developing a true windows client? Past research has shown zip in that regard, but it would be wonderful to have accelerated desktop access.
Fingers crossed

Hi Rafael,
Thanks for the reply. I've decided to go that route as well. With Hamachi ( www.hamachi.cc ) coming out for the Mac shortly (console version just came out, GUI version coming soon) it will make for secure sessions that anyone in the family can use. I won't even dare try to explain SSH to family members.
I'd still love to see an Aqua-accelerated remote desktop solution that runs on Windows though.

Reset (stop and start) Apple Remote Desktop

Log in SSH to my xServe, I want to reset (stop and start) the Apple Remote Desktop service of the sharing system preferences of my server. I'm looking for a command: systempsetup -set...

kickstart can do this and much much more.
http://docs.info.apple.com/article.html?artnum=108030

Distribute Adobe Air Runtime via Apple Remote Desktop

I've be researching whether or not it's possible to distribute the Adobe Air framework via Apple Remote Desktop, but I haven't found any solutions. The Adobe Air Admin guide has this to say:
Enterprise deployment
IT administrators can install Adobe AIR and AIR applications silently using standard desktop deployment tools. IT administrators can deploy the following:
•Silently install Adobe AIR using tools such as Microsoft SMS, IBM Tivoli, or any deployment tool that allows silent installations that use a bootstrapper
No mention of Apple Remote Desktop, or any other Apple-related Enterprise deployment methods. Is this possible, or must Mac software vendors bundle the Adobe Air framework with their pkgs (and jump through the necessary licensing hoops) in order for clients to get an Adobe Air app and all it's dependencies (i.e. the Adobe Air framework) distributed to a network of Apple machines.
Thanks!

Thanks for the interest in AIR. You are correct that you would have to wrap everything (runtime and application) up in a .pkg for installation via ARD. Another alternative would be to get the AIR Runtime installer on to the remote system, and then execute it via ssh.
Chris

IMac at work, iMac at home. (Latest Yosemite and Apple Remote Desktop updates installed) Need to work from home at night. I don't know how to set my permissions so that I can just control my iMac at work.

iMac at work, iMac at home. (Latest Yosemite and Apple Remote Desktop updates installed) Need to work from home at night. I don't know how to set my permissions so that I can just control my iMac at work.

If they have set up port forwarding for you already then that is different. In that case, then you could be experiencing the bug with the most recent release of ARD (3.7.2) and in particular ARD 3.7.2 and Yosemite ARD version 3.8 clients. It has been reported numerous times in the forums and to Apple that since 3.7.2, clients are frequently unavailable to connect to despite there being no network issue between the remote computer and client computer. I have not seen anyone report it who was working from outside the LAN to inside the LAN, but I have the same issue with a number of my own computers that are simply on a different subnet, so it stands rot reason that it would happen from a port forwarding location.
I am sometimes able to resolve the issue locally by SSH connecting into the client computer using Terminal on my admin machine and restarting or relaunching the ARD agent on the remote device, then trying to connect to it again after about 30 seconds.
The Terminal commands for this procedure are as follows, though you might need to include a port number from outside the LAN:
First:
ssh ipaddress -l adminusername
(example: ssh 192.168.1.1 -l macadmin)
Second:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -restart -agent
After that, waiting about 30 seconds and trying to observe or control usually works, though the computer may still fail to show an online or lit-up status indicator.

Apple Remote Desktop issues in Mavericks

After upgrading to Mavericks from Snow Leopard on my MacBook Air, Apple Remote Desktop skewed all my lists. I can no longer control any of my client machines (even after I updated to clients to 3.7.1) and the overall performance is choppy at best. I am able to control client machines that have a static IP i.e. Servers etc., but ARD does not see any DHCP clients when scanning ethernet or wireless and will not let me control or view any existing clients that I maintained prior to installing Mavericks. Anybody else experiencing problems with ARD in Mavericks?

You might try to turn off the firewall on the client. Yes, this appears to be a bug. If you can connect to the client thru SSH you can use this:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate
That should return:
Firewall is enabled. (State = 1)
Then you can run:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --setglobalstate off
That should return:
Firewall is disabled. (State = 0)

Apple Remote Desktop version 3.5.1. to version 3.5.2

I originally purchased Apple Remote Desktop version 3.5.1 from the App Store. Apparently Apple Remote Desktop version 3.5.2 has been released. Guess what??? The App Store does not have the update for version 3.5.2. I downloaded the update from the Apple Support Downloads page and installed. Guess what??? Apple Remote Desktop is still at version 3.5.1.
I originally recommended to my mother to purchase a MacBook Pro and I could remote to her computer to undo anything that she has done...laugh. At almost 70 years old, it's a challenge... I was able to remote to her computer for a while and now can't. I guess version 3.5.2 was supposed to fix this issue. She has ARD version 3.5.2 on her computer. We both have Lion version 10.7.3 installed as well.
How am I supposed to get the update for verson 3.5.2 installed? Why doesn't the App Store have the update? Am I not doing something correctly?
Any suggestions would be helpful and I thank you in advance.

If your mom had any kind of issue with her internert connection, Her ISP might have her reset the modem. Some times a power outage can cause a modem to revert to default settings. And any time it a modem is reset to defaults the modem has to be re-configured for ARD.
ARDAgent is the OS built-in tool for remote viewing / controlling the screen. If you want to SSH in, you need enable remote Management Login on your moms computer. (it's in system prefrences, sharing) If you do SSH, ARDAgent can be access from the command line to start/stop/restart and reconfigure ARDAgent. But just like ARD, you need the right ports open on your moms firewall/router to make the connection.
You could check to make sure the firewall is off on your moms computer. (system prefrences, securty, firewall tab) you could have her uncheck Remote Management and recheck it to restart the ARDAgent service. (system prefrences, sharing)
If your moms IP address changes frequently. You could look into a subscription service like DYNdns. It requires software on your moms computer, but basicaly it report to the DYNdns server what ever your mom's current IP address is. And in turn give you a DNS address you can use to contact your moms firewall. some thing like mom.dyndns.com. Even with DYNdns, you may find you need to delete and re-add your moms computer from ARD to connect.
logmein dosen't require DYNdns or port configuration. Because it reports into the logmein servers so there no ports need to be opened.
If you talk to your moms ISP. They would need to open the ports 5900 for UDP and TCP. Along with 3283 for UDP and TCP. MAlong with 22 for TCP (SSH and file transfer). And of corse when they open the ports they need to route to your moms computer consistently.
I'm surprised they would help you with this. I don't think my ISP would be as acomidating.

Apple Remote Desktop, 2010 Mac Pro, and six displays

Under 10.8, we were able to operate a 2010 Mac Pro (MacPro5,1) with 2 x HD5770 video cards and 6 x LED Cinema Displays (the mini DisplayPort models, two of them via IUSB-powered Atlona DVI Dual-Link-to-mDP adapters, via Apple Remote Desktop.
Under 10.9 (currently 10.9.2), all the displays still work, but ARD is having significant heartburn: if it is able to connect with the ARD agent on the display syste, the display arrangement is incorrect, and no amount of swapping mDP cables, moving the displays around in the Displays System Preference pane, and/or rebooting appears to help. Oh, and the most recent end state, when I finally managed to get the menu bar on one of the displays on the top (physical) row (we have them arranged 2 x 3, in order to display 4096 x 4096 pixel movies of spacecraft data), flummoxed ARD completely --- it simply refused to connect with the display machine at all. (I can ssh into the display system and use a cabled keyboard and mouse as well, but that's not a long-term solution: we have to be able to operate remotely, as we did under 10.8.) Oddly, ARD works OK, if not perfectly every time, with the target system when it's only connected to four or fewer displays (regardless of whether they're connected to mDP ports or via the Atlona devices). The host ARD system is another MacPro5,1 with 24 Gbyte of RAM; the target has 96 Gbyte.
Reading the release notes for ARD 3.7.2, it sounded as though all our issues would be addressed, but alas, it is not so: we're still stuck with ARD trying to but unable to open a "Control" connection to the display system.
Does anyone have any experience, positive or negative, with a similar setup under 10.9 and ARD 3.7.2?
Is there any way to clear all the settings in ARD? I can't find any .plist files with client system-by-system info in them, and I suspect they are (appropriately) encrypted because they can contain passwords, or at least store the hashed passwords in encrypted fields.
Thanks in advance for any clues for the clueless.

Mac Pro
Date introduced
Original Mac OS X included
(see Tips 1 and 3)
Later Mac OS X included
(see Tip 1)
Mac OS X Build(s)
(see Tip 2)
Mac Pro (Mid 2012)
Jun 2012
10.7.3
10.8
11D2001, 12A269
Mac Pro (Mid 2010)
Aug 2010
10.6.4
10.7, 10.7.2, 10.7.3
10F2521, 10F2554, 11A511a, 11C74, 11D2001
Mac Pro with Mac OS X Server (Mid 2010)
Aug 2010
10.6.4
10.7, 10.7.2, 10.7.3 (Server)
10F2522, 11A511a, 11C74, 11D2001 (Server)
Mac Pro (Early 2009)
Mar 2009
10.5.6
10.6
9G3553, 10A432
Mac Pro (Early 2008)
Jan 2008
10.5.1
10.5.2, 10.5.4
9B2117, 9C2031, 9E25
Mac Pro
Aug 2006
10.4.7
10.4.8, 10.4.9, 10.4.10, 10.5
8K1079, 8N1430, 8N1250, 8K1124, 8P4037, 8R3032, 8R3041, 9A581, 9A3129
I expect your Hardware is essentially unchanged since the 2010 model, and should run the custom 10.6.4 they provided, or 10.6.5.
The "Full Retail" 10.6.3 is only 10D575, so it will not suffice.

Achieving remote desktop, like in Windows. Is it possible?

I've been googling abit on this subject but can't find a good answer it seems.
I want to set up a remote desktop on my server where users can connect remotely (starting at gdm, kdm or what ever display manager that works) and log in to their desktop on a session of their own. E.g. the same way that remote desktops in windows works where multiple users can log in and do work simultaneously. Is there a reasonably easy way to do this in Linux?
The closest I've seen is using x11vnc but I'm not sure that it will work the way I want. Or will it?

antis wrote:
zhiwlin wrote:Or you can download rdesktop (http://www.rdesktop.org) and compile (./configure, make, make install, make clean), then download tsclient (http://sourceforge.net/projects/tsclient) and compile (./configure, make, make install, make clean). Then run tsclient (I think the default is in /usr/local/bin folder).
But rdesktop is only a client for accessing windows terminal server... isn't it? Or is there a linux server available as well, because that is really what I'm looking for?
xrdp: http://aur.archlinux.org/packages.php?ID=14654
seems strange to me thou. i stick to good old ssh X-forwarding or port-forwarding + vnc.
€: btw you don't need to compile rdesktop, its in the arch repos.
Last edited by mcover (2009-01-13 22:31:18)

Can not use any remote desktop like VNC after installing Oracle Linux 6.3

Hi
I just installed OL 6.3 on a HP Proliant ML380 g7. Now I want to connect to the server using any Remote Desktop tools but I can not!
I've activated system>pref>Remote Desktop
But I can not access any of servers from:
- a Mac using, Mac server sharing screen, VNC viewer or Microsoft Remote connection which is in a same subnet
- Other Server Using KRDC, Remote Desktop Viewer, terminal server client or tiger VNC viewer
Also I tried to connect to servers after activating krfb
but it always says no rout to server/ server not found/ connection closed
and remote desktop viewer can not find any host when I try to use option "find"
Please Advise
Thank you in advance

Make sure to enable "require a password..." in the Remote Desktop Preference on the Linux system. Some clients won't work unless this is set. Unfortunately the Remote Desktop Preferences panel on the Linux side does not show you the port it is listening on, but you can get it by clicking on the IP or name that it shows as a link. The first user or vnc server is usually listening on port 5900, then 5901, and so on.
Your problem is probably the firewall on your Linux system. You can disable the firewall on the Linux system:
service iptables stop
However, probably a better idea, simply tunnel the connection through SSH as following:
On the Mac, open the Terminal application from the Applications/Utilities folder. Then type the following:
<pre>
ssh -L local_port:localhost:remote_port -N -f -l username server_address
</pre>
local_port = port on your Mac that does not conflict with any of your own screen-sharing or other services, e.g. 5555
remote_port = vnc server port on your Linux system
username = user for which you have enabled remote desktop sharing
server_address = ip address or FQDN of your Linux system.
For instance:
<pre>
ssh -L 5555:localhost:5900 -N -f -l root 10.0.1.2
</pre>
The trick is now to connect to a local port on your Mac, instead using the address of your Linux server. The communication will be encrypted using ssh going over tcp port 22, which is normally enabled in the firewall.
The Mac screen sharing application is working fine. On your Mac, select "Go>Connect to Server" from the Finder menu and type:
vnc://localhost:5555

Ssh "remote desktop"

Similar Messages

Maybe you are looking for