Remote desktop / screen sharing / VPN questions

Hi all-
OK, I am trying to set up our all-mac environment to do something in particular - but I am only 'novice' level at VPN stuff and 'noob' to the Apple Remote Desktop and Screen Sharing stuff. I already have screen sharing set up, and also have back to my mac set up - but these both seem to be 'whole computer' control methods, where the remote user takes over the entire target machine. I have a different need, but don't know what terms to use to describe it or how I might achieve it.
Environment overview:
2014 iMac, 2009 13" MacBook Pro, 2009 17" MacBook Pro - all running Yosemite.
2013 AirPort Extreme handling the LAN, both wired and wireless. iMac is wired, MacBooks are wireless.
iMac: Two users (UserA and UserB, both admins).
MPB13: Two users (UserB as admin and UserC as standard).
MBP17: Two users (UserA as admin and UserD as standard).
I am wondering if this is possible to do, and if so - HOW? :
UserB sits at the iMac, and is using it. UserA sits at MBP17 and wants to get something done on the iMac, so UserA logs into MBP17 as UserA then remotes into the iMac as UserA and does what they need to do in UserA's iMac account - without making UserB (who is still sitting at the iMac and using it) stop what they are doing.
Hope this makes sense, and am looking forward to your input.

UserA must have a user account set up on the iMac that is different from UserB. With this set up when UserA initiates a Screen Sharing session with the iMac from the MBP17 they will just need to log in with their user account. When they do that a dialog box will pop up asking if they want to share the display with the user currently using the iMac, in this case UserB, or if they want to connect to a Virtual Display, which would give them their own environment separate from UserB who is already logged in and using the iMac.
Here is an example of the dialog box UserA should see when they attempt to start a screen sharing session with another Mac in which another person is already login in and using the Mac. In this case UserA will select the option to connect to the Virtual Display which allows them to work on the iMac without disturbing the user that is already using the computer. Note that the user already using the iMac may experience a slight performance hit because two users are using the resources on the one computer.
As for the acronym VPN, it stands for Virtual Private Network which is a protocol for making a encrypted secure connection over a public network between two or more separate networks. Screen Sharing actually uses a protocol called VNC which stands for Virtual Network Computing.

Similar Messages

  • Remote connection, screen sharing, etc question

    I'd like to remotely connect to my desktop either from a PC or another mac that isn't on my local network. I have a domain name registers, and i'd like to use this domain (godaddy.com) and just be able to type afp/smb/ssh (depending on if I'm on a mac or pc) and hhtp://www.mydomian.com and instantly get to my computer to change downloads and get files from an external drive, my OSX main disk, etc. I have a MobileMe account to, if thats any help. if I cant use my domain and somehow point it to my dynamic IP, I can use dyndns.
    thanks

    how would I set this up? do I forward 5900 (is that the ssh port?) and 22 on my router? or after that type ssh www.mydomain.com:5900? I'm not sure how to enable the ssh capability. I have remote management, screen sharing, file sharing, remote login, and web sharing enabled in settings, do i need anything else enabled, which ports exactly should I enable?
    Assuming you want to maintain secure connections over the internet, I would suggest configuring your home router to forward a random high numbered port to your target home system's port 22. Most home routers allow this, but how to do it varies from manufacture to manufacture. A Google Search will most likely find instructions for your model router.
    So lets assume you choose internet port 12345 to forward. Making an connect to your home system from the outside world would looks something like:
    ssh -p 12345 [email protected]
    That gives you an interactive shell login to your system.
    If you wish to tunnel a screen sharing VNC session you would use something like:
    ssh -p 12345 -L 5901:localhost:5900 [email protected]
    Then using your VNC client of choice you would connect to
    localhost:5901
    Your VNC client would then talk to local port 5901, ssh would send this to the remote system's port 5900 which is the default VNC server port.
    Using ssh to tunnel other protocols is done in a similar way, only the ports used will be different. Since I have only personally tunneled screen sharing, I'm not going to try to explain how to tunnel other protocols.
    NOTE: You can specify as many ssh -L options on the command line as you like. Also the SSHTunnel utility can help you setup ssh tunnels.

  • Remote Desktop & Screen Sharing not  working??

    Hello all,
    I am trying to connect to a friends computer via the Finder's Screen Sharing, I enabled the screen sharing preferences under the System Preferences, put the password, etc and had him do the same and I am not able to connect to his system. I'm sure there is something else I have to do in order to get this to work. In the Windows world I had to use the VNC. But, I remeber reading in a Snow Leopard book that this is all that had to be done in order for this to work.
    Best Regards,
    freesparks

    I know I could never get this working between two macs of the same OS (10.5.8) over the internet with the appropriate Sharing settings set up....
    Im guessing both Screen Sharing and Remote Access through iChat DO NOT work anywhere but in a LAN?

  • How to detect real desktop and remotely accessed(screen shared) desktop?

    Hi All,
    On Mac Os the Screen Sharing feature is similar to Remote Desktop Service. Is there a way to determine whether the terminal where we are starting the application(our own application) is real desktop or remotely accessed (screen shared) desktop?
    For Ex:
    I have booted(logged in) the Mac A sytem with user1 account. From another Mac B machine, i will login to user2 account of Mac A sytem using Screen sharing  feature. My application has to run only on real desktop, not on remotely accessed desktop(screen shared). So Is there a way(programmatically) to determine whether the terminal where I am starting the application is real desktop or remotely accessed (screen shared) desktop?
    Please guide me.
    Thanks & Regards,
    Vinay

    Have a look at the 'Son Of Grab' sample code, it shows you how to grab elements of the screen individually.

  • How can I login remotely (not screen sharing)

    Hi
    Is there a way I can login to my desktop (running 10.8.2) and work remotely - without screen sharing?
    I am talking about full desktop access, logged in remotely, without disturbing the session of another user who is logged in, and physically in front of the computer.
    I have spent a long time googling and cannot figure out if such a solution exists, either within the base OS, Apple Remote Desktop, or commercial solutions.
    In an ideal world such a solution would also be cross-platform so that the remote client could be either Mac or Windows.
    Thanks for any guidance.

    I answered my own question.
    By setting up another account it is possible to remote login with a VNC client. When connecting to the mac the login screen is presented. Provided that you login to an account that is not the front account running on the mac, that session is not disturbed.
    Thus it is possible to run with full access to apps and data, on another account and session separate from the session that is already logged on.
    However, if during that VNC session you switch users and login to the front account, you now will be the only session and will be controlling that screen. After that point you have to disconnect the VNC client, and re-log back in in order to leave the front account undistrubed.

  • Windows 8 crashes when trying to connect to a Remote Desktop or a VPN

    Hello, 
    When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network
    machine).
    Useful PC specs:
    - i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board)
    > All latest drivers and Windows updates installed.
    > Ran Memory Diagnostic. No errors.
    Event Log:
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a
    Exception code: 0xc0000005
    Fault offset: 0x00000000000027ee
    Faulting process ID: 0x994
    Faulting application start time: 0x01cdf16f9b46e882
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\DUI70.dll
    Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a
    Faulting package full name: 
    Faulting package-relative application ID: 
    WinDbg: (RDP Crash dump with procdump)
    Loading unloaded module list
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (994.1118): Access violation - code c0000005 (first/second chance not available)
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> .ecxr
    rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000
    rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0
    rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000
     r8=0000000000000001  r9=000000989f3afa28 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=00000098a1d29401
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
    dui70!DirectUI::Element::_SetValue+0xe:
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    0:000> !analyze -v
    *                        Exception Analysis                                   *
    GetPageUrlData failed, server returned HTTP status 404
    URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    FAULTING_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    DEFAULT_BUCKET_ID:  NULL_POINTER_READ
    PROCESS_NAME:  mstsc.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    READ_ADDRESS:  0000000000000000 
    FOLLOWUP_IP: 
    dui70!DirectUI::Element::_SetValue+e
    000007fe`c5be27ee 488b01          mov     rax,qword ptr [rcx]
    MOD_LIST: <ANALYSIS/>
    NTGLOBALFLAG:  0
    APPLICATION_VERIFIER_FLAGS:  0
    FAULTING_THREAD:  0000000000001118
    PRIMARY_PROBLEM_CLASS:  NULL_POINTER_READ
    BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ
    LAST_CONTROL_TRANSFER:  from 000007fec5be7db8 to 000007fec5be27ee
    STACK_TEXT:  
    00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe
    00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98
    00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689
    00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e
    00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20
    00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37
    00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69
    00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2
    00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66
    00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8
    00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56
    00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242
    00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc
    00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113
    00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b
    00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151
    00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc
    00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310
    00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b
    00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159
    00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5
    00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4
    00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af
    00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f
    00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104
    00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc
    00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6
    00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20
    00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19
    00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7
    00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219
    00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113
    00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56
    00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69
    00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168
    00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12
    00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec
    00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7
    00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9
    00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63
    00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135
    00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8
    00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56
    00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a
    00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72
    00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a
    00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b
    00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695
    00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f
    00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375
    00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    STACK_COMMAND:  ~0s; .ecxr ; kb
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  dui70!DirectUI::Element::_SetValue+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dui70
    IMAGE_NAME:  dui70.dll
    DEBUG_FLR_IMAGE_TIMESTAMP:  50108e6a
    FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue
    BUCKET_ID:  X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
    Followup: MachineOwner
    Any ideas what could be the problem and how to resolve this?

    Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.
    I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that
    provides a program that'll hash the password for you. I used it so I can say its safe:
    http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/
    I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for
    those in a bind this will work for you.
    This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

  • How can I remotely enable Screen Sharing remotely on 10.8?

    Is there a way to remotely enable Screen Sharing from another mac? I'm using 10.8.

    I assume you mean by remote login.
    To enable via SSH to an admin account:
    sudo launchctl load -F /System/Library/LaunchDaemons/com.apple.screensharing.plist
    To disable:
    sudo launchctl remove com.apple.screensharing

  • Remote Desktop/Access shared files over PPTP VPN

    Hello,
    I just bought the RV180W so I can connect to my office computer from anywhere as a VPN client. The two things I need to do while I am connected as a VPN client is to be able to access my files on my office desktop and be able to remote desktop to it as well. I have Win7 on all of my computers. Ideally, I would like to do that over PPTP VPN connection but if that is not possible I can try Cisco QuickVPN software.
    I enabled PPTP on my router and created a user account. I was also able to successfully establish the connection remotely. While I was connected as a PPTP VPN client, I was able to access the Internet and my router setup page which is telling me that the connection is good. However, I was not able to either discover my office PC under my network tab in Win7 nor I was able to remote desktop. I keep my office PC on all the time and it never go to sleep. I did not create any connection policy but maybe this is the problem. Please let me know if you know of a solution.
    Thanks!

    Hi David,
    Thank you for the response.
    I was able to access the router configuration using the local IP address (in my case 192.168.1.1). I don't think I would have been able to access it using the public IP address since I have the router remote management feature disabled.
    Now after reading your email, I was finally able to remote desktop and access shared files through a PPTP VPN connection. Here is what I did:
    1- I separted the PPTP VPN IP address range from my DHCP range (in my case, PPTP VPN range is 192.168.1.200 to 210 and my DHCP range is from 192.168.1.100 to 199)
    2- I assigned my office desktop PC that I am trying to remote desktop to a fixed IP address (192.168.1.20)
    3- For remote desktop, I had to type the IP address (192.168.1.20). Typing the PC name (officepc) or searching for was not working.
    4- For shared files, I had to map a network drive as //192.168.1.20/My Pictures for example. I couldn't find my PC when searched for it under Network.
    After doing all that, I was able to do kinda what I wanted. Ideally, I would have liked to avoid using fixed IP addresses and be able to access computers by their name and see them under the Network tab. Is their a way to do this? I noticed that RV220W offers SSL VPN, would that help me?
    I would appreciate it if you could answer my last two questions.
    Thanks!
    Mustafa

  • Unable to access Standalone VM via Remote Desktop through a VPN

    Good Morning everyone, now here is my problem.
    My company is a small software development house and we test our software on Win 7 or 8 VM's running on standalone (ie not on the domain) VM's. We are running the VM's on WS2012 R2 Hyper V and when we are inside the building we are able to Remote Desktop
    onto these VM's direct without any problem. The problem comes when we want to RD onto the VM's when working from home via the VPN. When we try to connect to the VM's via RD through the VPN the Remote Desktop Connection fails with the following alert "Remote
    Desktop can't find the computer '[Computers Name]'. This might mean that '[Computers Name]' does not belong to the specified network. Verify the computer name and domain that you are trying to connect to." The only way I can connect to the VM's is
    by going onto the host server and access the VM's via Hyper V manager and use it that way.
    Now when I try to connect to a VM that is running on the Domain via the VPN I connect without any problems at all.
    So my question is why can I connect to standalone VM's via RD without any problems when in the office but when I am at home via VPN I can't but I can connect to VM's on the domain without any problems? What do I need to do to make this work?
    Phil

    Hi Darren,
    I have just tested it and when at work I can ping by name a named server and the standalone VM without any problems.
    But when I connect from the outside via the VPN I am still able to ping by name a named server but not the stand alone server. Nor can I ping the IP address of the standalone VM although I can connect to a standalone VM using its IP address via RDC
    Phil

  • Desperately Need Help: Why won't remote desktop work w/VPN to a PC?

    I am seriously losing my mind and the IT people at my job are clueless. I am not that sophisticated but, when it comes to macs, I might as well be a genius in comparison to them.  At work I have a PC running Windows Vista.  I have installed on my Mac (running Mavericks) VPN through Netextender.  I can connect to VPN with no problems.  However, when I try to login thru remote desktop, it tells me my work computer cannot be reached.  My work computer is most certainly on and reachable.  I desperately need to figure this out!! Please help!

    Hi Gailkav,
    Welcome to the Forums     
    As per the query we understood that you are facing issue with USB in your Lenovo B50-30 laptop.
    Try to connect other USB devices like pen drive, external HDD and check if that is been recognized,
    Try to boot the system into safe mode and check for the issue.
    Hope this helps. Do post back if the issue persists!                                         ​          
    Best regards,                                                   ​       
    Ashwin. S
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Back to My Mac / Remote Management / Screen Sharing

    I'm managing computers for my family spread across 3 states. I would love to get screen sharing working but it's just not happening. I've tried the steps in the following KB article and that's allowed me to access two mini servers (one 10.7 and one 10.6.8) at home. However, I can't access a MBP at home and I can't access my family's computers (via screen sharing) at all. Here's the KB article...
    http://support.apple.com/kb/HT3486
    Here's all I'm seeing (5 computers are "missing")
    I've tried NAT port forwarding (Airport Extreme/Time Capsule) for "Apple Remote Desktop" to the computers internal IPs on ports 5900 & 3283. I've tried it without. I've tried both "Screen Sharing" and "Remote Management" in preferences. I've made sure I have my own account with admin privledges on all machines etc. This is, of course, all peppered with the occasionaly outburst of foul language...
    What am I missing?

    Spoke with Apple who spoke with Apple and so on. Tech support for Apple Desktop Remote acknowledges (as best they could) that there is a bug/ problem. Yes, reverting to an older (3.5 - 3.4 ARDagent) solves the problem (short term ?). They captured my OS info and will get back to me in 3-5 days - how do you like them apples! So, revert to ARDagent 3.4 and you can remote connect - may try this later... will post if it works. Here's what's been posted on this: https://discussions.apple.com/thread/3192451?start=0&tstart=0

  • PLEASE HELP, SOMEONE REMOTELY VIEWING/SCREEN SHARING MY MACBOOK?

    Hi - I urgently need help from anyone who knows about this issue - I am a very basic macbook user, and don't really know about all the different programmes etc. I believe someone ( the guy who sold me the macbook, who told me he was a mac repair person and programmer) has been hacking into the computer, using the remote access - there is a programmed called SCREEN SHARING but I cannot access it - and a bunch of other files such as odsagent etc - not sure if these indicate he is using the screen sharing/ remote access to my mac.
    The reason that I believe he is accessing the mac, is that he downloaded all the files, so would clearly have access to passwords etc, there were loads of his old files, that showed pictures of people saying " target", and old files showing he was studying comuter/ mac programming. The first time I went online all of a sudden the computer froze, and two green lights showed on the num lock key and the shift key I think, the two keys were frozen, and the keyboard basically wouldnt respond, but the activity continued on the screen. This has happened a number of times since then, usually just randomly the keyboard freezes, and if you wait a while it goes back to normal - the mouse works fine, then one day it keep sort of freezing/ getting stuck/ pausing for no reason - the next day its fine again. He put in a load of software, which he has obviously been able to get round the need of liscening numbers, as he did not provide me with them. one day I saw a name "macbook pro" suddenly appear, and that it was tryin to connect/ share or something - this has never happened to me before with my old mac- it was like another computer was connecting/ sharing with my computer without my permission - this was when I was online. This has not happened since.
    I am scared he is accessing the computer, because these things that happened, and because there is loads and loads of files and programmes, which sound suspicious, i dont know what they do, and I just have this dogey feeling about this guy, and the fact that there is screen viewing/ remote management files etc which I cant access, but I am not sure if they are being accessed.
    PLEASE HELP - I FEEL LIKE MY PRIVACY IS BEING INVADED - I was speaking to my family on Skype and the green lights came on/ it froze, I continued with the conversation, but later I felt like he might have been watching.
    If anyone can recommend an expert in the London area, that can check the mac to see there is nothing on there that is being used to remotely control/ screen share my mac, I would be very grateful - its just horrible using your computer, and always being worried someone is invading your privacy, and and downloading your files etc.
    Sorry if I sould paranoid, but I have a strong feeling something is not right here.
    Many thanks for your help in advance.

    Since you don't know much about computers, disconnect your internet (wireless or wired) to prevent future unwanted access. While it is smart to contact Apple Communities, this is a criminal matter and you should consider taking the matter to the police. People like this will not stop with you. You need to list the private data that may be stolen and take action (cancel credit cards, change passwords, bank accounts, phone numbers, whatever you have cause to be worried about). If you can afford it, buy a new hard drive, remove the old one, and install OS X from scratch. Give your old hard drive to the cops. Make sure you turn the Firewall on (click the Apple up on the toolbar top left > System Preferences > Security) and uncheck any "Sharing" options (System Prefernces > Sharing). This event you are experiencing is unfortunate, and rare, but with a pro-active attitude you will come through it fine - and wiser.
    EDIT
    dgambler is right in that by purchasing a Snow Leopard disk (presuming you don't already have one) and performing a fresh install (it is easy) is a sure way to "take back" the controls of your Mac. You will need to study online tutorials for "wiping the drive" rather than a simple install. But you should let the police look at the hard drive before you do that - they will be able to see exactly what this person did.
    usefull information:
    http://docs.info.apple.com/article.html?path=mac/10.4/en/mh294.html
    http://lowendmac.com/ed/rosen/mac-remote-control.html

  • Remote Access - Screen Sharing - possible to have a different session?

    I was wondering of there was some way, maybe using X11, of doing screen sharing to my iMac but with a different session.
    Can I log-in across the network and get a separate logged-in session from the one on the main screen?
    If so, how do I do it? Is there a 'How to' somewhere?
    I'd imagine something like setting up a Display parameter for X11 that can run remotely on my machine, so I can log on as a different person and run a different session without affecting what's on the main screen. Effectively to be multi-user access.

    On a Unix or Linux system (and OS/X is a Unix system) you can have multiple remote sessions running under X11.
    Mac OS X does NOT use X11 as its graphic engine. X11 is a side car on Mac OS X, provided so users that need to access Linux/Unix system which do use X11 have a way of displaying X-Windows output.
    Mac OS X itself does not use X11 in any way. So even if you could do what you want, it would not get any of the native Mac OS X applications displayed on your system.
    As someone else has pointed out, there is a trick with Fast User Switching and the Vine Server that can allow multiple users to access the system. It is a bit of a hack, and less than perfect, but if it works for you, that might be an option.

  • No Remote Desktop connection without VPN

    Not sure if this belongs here, my appoligies in advance.  I have a remote user with an ASA 5505 device that shoyld be able to connecte to a Remote PC using RDP, but is only able to do so if she 1st connects to the Check point VPN client.  I can't comment on the ASA config, but I have others with the same exact set up at home that don't need the VPN.
    Any help is appreciated, Chet

    I sometimes suffer a similar problem, where my VPN connection works, but I can't Remote Desktop to some machines.
    This usually turns out to be routing rules on my PC, or firewall settings.
    Firstly, has anything changed on your PC?  Upgrade, new software etc?  Or the work network?
    When connected on the VPN, can you ping your work PC by name or by IP address?
    CharlieF

  • Connecting to office computer remotely using screen sharing app

    How do I connect to my office computer using the screen sharing app in the system?
    Are there complete instructions somewhere that I can read?
    I have a computer at home and at the office, both with sbcglobal router connections to the internet. I have read that /System/CoreServices/Screen Sharing.app will allow you to connect to computers over the internet, but the article I read did not have much detail.
    So say my work router hardware internet address is 123.12.23.123
    When the window open after I click Screen Sharing, do I put that address in there?
    Is there a port I need to open at the office?
    Is there some internet address for my computer besides the sbc 172.12.1.23 address that I should use instead?
    Screen sharing has a computer setting under sharing "VNC viewer may control screen with password: abcdefg"
    Where do I find more information about Virtual computer networking and how I can do it with my may and the software apple provides.
    I appreciate your help.
    Message was edited by: James Mol

    The only way I have been able to do this is to use logmein.com to access my office computer, then using iChat, accept the invitation to share my office screen. One connected, I can log off logmein.
    Has anyone found an easier way?
    Thanks

Maybe you are looking for