Remote Access - How to resolve common error messages when connecting remotely to a CoreImage device


Introduction

Two common errors can occur when attempting to remotely access a Classic-CoreImage device:

  1. Access denied
  2. Cannot find the computer

Instructions

1.  Error: The connection was denied because the user account is not authorized for remote login

If you are trying to connect to a remote Classic-CoreImage computer and receive the error "The connection was denied because the user account is not authorized for remote login" you have either not been granted remote access to that computer or you are not an administrator.

Access Denied Error when attempting to remote into a CoreImage system

Resolution:

  • Request remote access rights to the Classic-CoreImage device.
  • If you have recently been granted remote access rights to the Classic-CoreImage computer and are still receiving the error make sure to run maintenance on the computer. Depending on how recently you were granted access the computer may not have automatically updated.

 

 

2.  Error:  Remote Desktop can't find the computer

If you are attempting to connect to a computer and receive the error "Remote Desktop can't find the computer 'Device Name'. This might mean that 'Device Name' does not belong to the specified network. Verify the computer name and domain that you are trying to connect to" there are a few possible reasons to have generated it.

Example screenshot of the error "Remote Desktop can't find the computer"

Resolution:

  • If you are connecting from a Classic-CoreImage device make sure you're on the MFleet wireless network if onsite or connected to the Michigan Medicine Cisco Secure Client VPN if remote.
  • Make sure you typed the target Device Name of the computer correctly.  All Classic-CoreImage Windows Device Names are 8 characters in length.
    • You can also try to enter computer name as "name.umhs.med.umich.edu" (e.g., WS123456.umhs.med.umich.edu instead of just WS123456).  You must use this fully qualified name if you are connecting from a personally owned device.
  • Make sure the target device is online and connected to the internet. If you are working remotely while the target device is onsite, the Service Desk can attempt to remotely start the device.