Connection Errors to Remote Desktop from OSX after Domain name change

We have an issue using Microsoft Remote Desktop from Macs in our school. All was well until we changed the domain name of our RDS servers and installed a new wildcard certificate. Connections work perfectly in Windows 7/8 and also iOS on iPads, but we cannot
get any Macs to connect having tried OSX 10.7 and 10.9. The error message says the connection failed to load but seems to add a spurious end to the connection string - TS/en-US/Default.aspx - but we cannot trace where this is being picked up.
We can get to the site in a web browser and sign in to receive the "browser not supported" message in Safari so traffic is obviously getting to the severs.
Has anyone else had a similar issue? We have spent days poking around with DNS etc but can't seem to make any progress here.

Hi Jeremy,
I have tried removing connections and also re-installing the App. We have been using this App since January with no real issues until we made our domain name change - I really don't understand why it works fine in Windows and iOS but not OSX. We are doing
nothing different to what we have done from day 1.
Log file from our old connection when it was working looked like this:
[2014-Mar-24 10:41:43] RDP (0): Final rdp configuration used: redirectcomports=1
server port=3389
use multimon=1
redirectdrives=1
promptcredentialonce=1
authentication level=0
full address=rdsfarm.xxxxxxx.internal
session bpp=16
prompt for credentials on client=1
redirectprinters=1
drivestoredirect=*
alternate shell=||OpenMind
gatewayusagemethod=2
alternate full address=rdsfarm.xxxxxx.internal
workspace id=rdsgw.xxxxxxx.internal
allow font smoothing=1
redirectposdevices=0
audiocapturemode=1
gatewaycredentialssource=0
remoteapplicationname=OpenMind 2.0
devicestoredirect=*
remoteapplicationmode=1
remoteapplicationprogram=||OpenMind
enablecredsspsupport=1
redirectsmartcards=1
redirectclipboard=1
span monitors=1
gatewayprofileusagemethod=1
gatewayhostname=rds.xxxxxxx.sch.uk
remoteapplicationcmdline=
The log file looks very different now, all I am getting is:
[2014-Jun-17 10:26:41] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Jun-17 10:26:41] RDP (0): lo0 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Jun-17 10:26:41] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
[2014-Jun-17 10:26:41] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Jun-17 10:26:41] RDP (0): gif0 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): stf0 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): en0 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): en1 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::21f:5bff:feb8:3f72%en1 netmask=ffff:ffff:ffff:ffff::
[2014-Jun-17 10:26:41] RDP (0): en1 af=2 (AF_INET)  addr=192.168.0.65 netmask=255.255.255.0
[2014-Jun-17 10:26:41] RDP (0): fw0 af=18  addr= netmask=
[2014-Jun-17 10:26:41] RDP (0): --- END INTERFACE LIST ---
[2014-Jun-17 10:26:41] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Jun-17 10:26:41] RDP (0): client version: 8.0.24875
[2014-Jun-17 10:26:41] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Jun-17 10:26:41] RDP (0): correlation id: 9f18df13-7c84-dc4b-a780-e6b77a280000
[2014-Jun-17 10:26:41] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Jun-17 10:26:41] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Jun-17 11:44:15] RDP (0): *** Application terminated ***
[2014-Jun-18 09:51:37] RDP (0): *** Application terminated ***
[2014-Jun-19 12:00:19] RDP (0): *** Application terminated ***
[2014-Jun-19 12:15:32] RDP (0): *** Application terminated ***
[2014-Jun-19 12:16:21] RDP (0): *** Application terminated ***

Similar Messages

  • Updates to website after domain name change

    Can I still update my website using iweb after I transition to a new domain name?

    I use third party hosting to mean a company other than Apple's .Mac. I also use godaddy to host my sites and it is very simple. They will provide an address of the ftp site name for your domain. I publish from iWeb to a folder, then use Cyberduck (any FTP program will do) to upload. You don't even need the ftp program because godaddy has their own simple ftp built in to the service. They also have excellent and free technical service. You can look at my site at: http://bandb.holage.com.

  • Connection error, and clicking sound from remote speakers

    Problem:
    Remote speakers produce clicking sounds when music is streamed from AirPort. Initially iTunes does not display a connection error, but it displays the following after switching from Base Station to Multiple Speaker mode:
    "An error occurred while connecting to the remote speaker "Base Station". An unknown error occurred (-3256)"
    The setup worked yesterday, and the Airport Firmware v6.3 and iTunes 6.0.5.20 are installed. I am able to use AirPort Admin Utility from my laptop to remotely change settings and restart the base station.
    Please help.
    Thanks.

    So i tried few more things like disable/enable sound card, driver reinstalation, bitrate changing and everything elese i could find here on forums or on the net (pretty much same stuff like here could be find on internet) and strange thing is that no one have same or similar problem like me... i just don't know anymore what to do...

  • HT5422 Can I install an earlier version of the Apple Remote Desktop from a disc on OSX 10.7.5?

    I cannot install an earlier version of the Apple Remote Desktop from a disc on my OSX 10.7.5 It says that the installation requires an earlier OSX version.
    I cannot upgrade with the RemoteDesktopAdmin361 available on line, since no Remote Desktop application exists. Any suggestions?

    Assuming your disk is for ARD 3.x, try this:
    • Insert your ARD CD
    • Open in Finder
    • Right click on the Remote Desktop.mpkg and show contents
    • Navigate to contents/installers
    • Drag the RemoteDesktopAdmin.pkg file onto the workstation and install
    • Run Software Update
    • Upgrade to the latest version of the admin application before attempting to launch the app
    Regards.

  • 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!

  • [Forum FAQ] Troubleshoot the error "The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode"

    Symptom
    RD License server is a key component of RDS. It licenses users to access RDS servers.
    After purchase the required RDS CALs, we need to activate the RDS License server and install the purchased RDS CALs. However, during the installation or after installation, we may face errors
    about RDS License.
    In most cases, the following error may occur.
    Error:
    The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server "Server name" does not have any installed licenses with the following
    attributes:
    Product version: Windows Server 2012
    Licensing mode: Per User
    License type: RDS CALs
    Troubleshooting
    1. Check whether the RD License Configuration is configured properly and there are no Warnings in the Event.
    2. The License Server should be part of 'RD Server License' group in Active Directory Domain Services.
    3. Check if the Licensing Mode is correct.
    - To change the Licensing Mode we can use RD Licensing diagnose, PowerShell cmdlet and Group Policy.
    Via PowerShell cmdlet:
    To change the licensing mode on RDSH/RDVH:
    $obj = get-wmiobject -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
    $obj.ChangeMode(value)
    # Value can be 2 - per Device, 4 - Per user
    Via Group Policy
    Path: Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
    Use the specified RD license servers = FQDN of server name
    Set the Remote Desktop licensing mode =
    Per User
    However, if issue persists, please provide detailed information and post the question in the
    Remote Desktop Services (Terminal Services) forum.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Richard,
    You need to uninstall Remote desktop session host feature. After removing it, you will default two connections which does not need to purchase RD CALs'.
    Thanks,
    Umesh.S.K

  • 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

  • Troubleshooting error with Remote Desktop 3.1

    Have OSX Server 10.4.10 on a powerPC with Remote Desktop 2.2, Security scans advise to update to Remote Desktop Client 3.1. Everytime I do this I get this error "The Remote Desktop Administrator software failed to start du to an unexpected error. The Remote Desktop software may not be installed correctly or the computer may require a restart."
    I have two machines on this network that are giving this error, one this server and the other a laptop. Version 2.2 was running and working just fine prior to the update, now its broke. Is there a log file somewhere to try to figure this error out? Has anyone else experienced this issue? I have already tried to reset permissions, and reboot, but nothing works.

    Just to confirm my understanding, you are running the ARD 2.2 Administrator on the server, and something is advising you to upgrade that system to the ARD 3.1 client? If that's the situation, then do not upgrade. The 3.x client will not work with the ARD 2.2 administrator. If you did indeed upgrade, you'll need remove ARD using the instructions here and then reinstall ARD 2.2 from your installation disks.
    Similarly, if you've upgraded any client workstation to the 3.x client, you'll need to remove it and reinstall the 2.2 client using this installer. It says it's an "updater", but it will work anyway.
    Hope this helps.

  • PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

    Hi all,
    we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
    the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html) 
    What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
    with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
    WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
    Is what i'm trying actually possible?
    Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
    desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
    Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

    It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
    Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Group Policy to clear down MRU lists and to clear or to prevent user login details for programs such as Remote Desktop from being recorded

    Hi there,
    Please can anyone instruct me on how to set up Group Policy to clear down MRU lists and to clear or to prevent user login details for programs such as Remote Desktop from being recorded. Your help would be much appreciated.
    Kind regards,
    RocknRollTim
    P.S. I was redirected by a forum user off the Microsoft Community forum.

    Hi RocknRollTim,
    Agree with Jason. Using a script will be a better option.
    Just addition, for history of RDP Connections, please open Registry Editor and follow the path:
    HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default. Please check if find MRU registry items where the name (or the IP address) of the terminal server is kept in.
    Please also follow the path: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers. It contains
    the list of all RDC (remote desktop client) connections that have ever been established from this computer.
    When expand Server folder and select a node, you will see the UsernameHint key that show the name of the user connected by rdp.
    Please back up registry items to avoid unexpected issues before any operation.
    If any update, please feel free to let us know.
    Hope this helps.
    Best regards,
    Justin Gu
    Thank you for responding back Justin Gu and I agree with both you and Jason Miller that a script can easily achieve this task. Thank you all for your help.
    Many thanks,
    RocknRollTim

  • Why is it not possible to install apple remote desktop (from appstore bought earlier) on my new imac 21?

    why is it not possible to install apple remote desktop (from appstore bought earlier) on my new imac 21?

    hello Dahveed, thanks for your reply, i solved it with the help of the migration assistant from another mac - now it works (but before as more info: for my new imac it was not possible to install apple remote desktop from appstore (the install-button not available, the same as installed already...) - and i don't know why...? - is it possible that the reason is the number of owned macs?)

  • I have an Ipad 2 and here is what I am trying to accomplish.  On my laptop I connect to a remote desktop connection to access a shared program we use for reporting.  How do I set up my Ipad to access this remote server?  Thanks for the help.

    I have an Ipad 2 and here is what I am trying to accomplish.  On my laptop I connect to a remote desktop connection to access a shared program we use for reporting.  How do I set up my Ipad to access this remote server?  Thanks for the help.

    Close ... before going for a specific Cisco app ... lets find out some details:
    Host we need more details:
    What is your server environment (Windows Server, or Mac OS X Server, or Linux)?
    What security is implemented in your environment - as what is restricted (RDP for all or specifc credentials on all machines? Are you part of local admin group to the server you wish to connect)?
    Does your environment Support CISCO IPSec connection? If so use Settings> VPN and IPSec tab to enter VPN details, if not then go with above suggestion. IF your restricted to RSA then either built in VPN settings or 3rd party app for RSA would suffice.
    Finally, there are many RDP applications out there I use "Mocha RDP Light" (free minimal ads when launched not when connecting).

  • Start remote desktop from windows lock screen

    Is it possible to invoke remote desktop from the lock screen of a host machine without interfering with any active session on that host machine? The host machine might have been locked by someone who had just walked away from it or the host machine may
    be being used remotely by its regular user. But despite this i would like to use it to run a remote session to my regular machine.

    Hi,
    The answer is no, Lock screen aims to protect user's profile and system resources securitry, Remote desktop need to use system rescoures, such as Printer, Drives, and so on. Therefore, it's impossible to start remote desktop from Widnows lock screen.
    Roger Lu
    TechNet Community Support

  • Difference between Terminal server connection and MSTSC remote desktop connection

    Hi everyone , Wats the main difference between Terminal server connection and MSTSC remote desktop connection? Well both are used to connect a server remotely. right!
    Are there any much difference between them?

    RDP is a protocol and MSTSC is the RDP client.
    In the situation you are referring to, you use MSTSC (RDP Client) in both cases, but when you connect to a client PC (Windows 7, Windows XP, etc) you can only connect if nobody is using that PC at the moment, if you connect to a server you can work along with
    some other users. Server OS supports 2 connections by default, if you want more people you need Remote Desktop Services and RDS licenses.
    Thanks,
    сила в справедливости

  • Cannot contact user after a name change

    One of our users got married and changed her last name.  My colleagues changed her name and alias in AD and in Exchange, and they changed her email address, keeping the old address as a secondary SMTP address in Exchange.  I ran the following command
    on the Lync server:
    Set-CsUser -Identity "CN=JNewname,OU=HQ,DC=Corp,DC=Com" -SipAddress sip:[email protected]
    After the user logged off the Domain and then logged back on, she could log in to Lync and could initiate an IM conversation with me.  However, I still cannot contact her.  She was never in my favorites list, and when I start typing her new alias,
    she shows up in my Lync client with her new name and then "Presence unknown".  When I try to initiate an IM conversation with her, my Lync client says "We couldn't send this message because we couldn't find Newname, Jane".
    I have tried deleting the Lync local cache from my client machine and still have the same errors.  What am I missing with this name change?
    Thank you very much for your help.

    Thank you!  That must have been what I should have done after I changed the sip address.  As it turns out, the contact had started working sometime before you posted this.  Does this update process take place automatically over time and the
    Update-CsAddressBook command would have forced the update immediately?  I had changed the sip address about 2 hours before I posted this question.
    Thanks so much for your help.  I will incorporate this into a memo I am writing for making a name change.

Maybe you are looking for

  • How to view pdf in 5700

    hi how to view pdf file in 5700?

  • INS0029 Error occurred during installation

    Version: OWB Client 9.2.0.2.8 OWB Repository 9.2.0.2.0 I cannot install successfully OWB Runtime Repository. Installation falls in 66%, then display Error message: INS0029 Error occurred during installation. What can I do?

  • 11g on Oracle Ent Linux ./runInstaller Pop is not displayed...

    I am having a very weird error...While installing the CRS my OUI does not show the popup where I can add 2nd node info. Just a grey screen. I have XCLOCK running... Any help is greatly appreciated. Thanks, Paru

  • My 13 MacBook Pro acts like the battery has died while it is plugged in.

    I will use my MacBook normally, it will be plugged in and fully charged. I will leave it on, close the lid and leave it plugged in for the night. The next morning it will still be fully charged (the charger indicator light is green, pressing the butt

  • MessageBrokerService failed to initialize

    I edited my server.xml to open up the https port, then Blaze threw this exception at initialization. I want to use Custom authentication for my application.  Is my server.xml set up correctly?  I tried it with vanilla tomcat, it worked perfectly. I a