EE - Forum Styles
fo
  • Not Answered

Remote Desktop connection to P+

Hi, we have purchased a new Dell 740 server via Emerson, Windows 2016 was already installed.

First thing whe did was to add the Remote Desktop role ( and add the TSCAL licences, per user )

Remote connections worked fine ( we use a terminal server to access our P+ servers and App.stations )

Next thing was installing Delta V version 14.3.1

Somewhere during this installation something must have happened with Remote Desktop, we could not access the server anymore...

In Event viewer security on the P+, whe see events that either the account or password is invalid, we checked all the classic settings but could not cure...

Funny thing: starting a RDP sesion from the P+ to the Terminal server does work

Has any one a suggestion?

10 Replies

  • Johnny, a couple of things worth checking:

    1) Did you install the ProPlus as a Remote Client Server? There is an option in DeltaV installation (Workstation Configuration) that prompts this question.

    2) Did you configure remote sessions on the remote client field in DeltaV Explorer for this ProPlus? Also, did you configure users that can connect to these sessions in DeltaV Explorer (empty field allows all users, but you need a session created in DeltaV Explorer and download it to the ProPlus)

    3) You need Microsoft CALs and RDSCALs for your host server, but you also need to assign a DeltaV license (Professional, Operator, etc.) to each created remote session.

    4) Using DeltaV User Manager you have to check the option to allow remote access for each user that you intend to use through the RDP session. If this setting is not in place the user will not be allowed to log in.

    There may be some other things like firewall settings, DNS, etc. but checking the above shall give you an introduction to our DeltaV Remote Client feature. The fact you can remote access the external RDS only confirms that this other server is working as a Windows box (no DeltaV) with the RDS role enabled and you are using a valid user to log in there. The user you will need to remote log in to DeltaV must be a valid user within the DeltaV environment, most likely a different user than the one you have available on this external RDS which I'm assuming is on Level 3 or above.

    I hope this helps!

    More info here: www.emerson.com/.../product-data-sheet-deltav-remote-client-deltav-en-56200.pdf
  • Is this a separate Terminal Server or is this terminal server now your Pro Plus? And are you in a Domain? was the terminal server a stand alone server when you enabled RD Role, and you were able to connect, but after running DeltaV install, it joined the DeltaV Domain, which would have completely changed RD privileges and such. By connecting to the Terminal server from another computer in the same domain, that indicates a trust issue between DeltaV L2 and the user/computer in the L3 or the firewall. Alex has some good starting points.

    Andre Dicaire

  • In reply to Andre Dicaire:

    Andre, it 's a separate terminal server ( set up by our IT guys ) that we use to run remote clients on all our Delta V systems.
    The new P+ is setup as workgroup ( it will stay a standalone test & develop P+ ).
    Since I am working from home, I have asked my collegue to re-run the Workstation configuration, this time as Remote client server, no results...

    Johnny
  • In reply to Alexandre Peixoto:

    Alex, yes to item 1 to 4...
    The P+ is setup as a workgroup
  • In reply to johnny ollivier:

    Is this Terminal server dedicated to this DeltaV system? Confused by statement this is used to run remote clients on all our Delta V systems. Did you mean you have a terminal server on each system or you have this one server and expect to connect to all systems?

    A Remote Client Server is connected to a single DeltaV system. If you have multiple DeltaV systems, each one needs its own Remote Client server.

    Andre Dicaire

  • In reply to johnny ollivier:

    You have to do this during installation. DeltaV checks if the machine is terminal server enabled and adjusts "something" appropriately during installation.
  • In reply to Andre Dicaire:

    Problem solved!
    At local security policy, security options, parameter: Network security: LAN Manager authentication level:
    This was set at: Send NTLMv2 response only. Refuse LM & NTLM
    Changed to: Send LM & NTLM – use NTLMv2 session security if negociated

    RDP works again!
  • In reply to Lun.Raznik:

    Problem solved!
    At local security policy, security options, parameter: Network security: LAN Manager authentication level:
    This was set at: Send NTLMv2 response only. Refuse LM & NTLM
    Changed to: Send LM & NTLM – use NTLMv2 session security if negociated

    RDP works again!
  • In reply to johnny ollivier:

    Thanks for sharing!

    That security policy changed from v13.3.1 vs v14.3.1. And it affects not just RDP but any other applications that uses network authentication, e.g., OPC.
  • In reply to Lun.Raznik:

    Yes, thanks for sharing your solution.

    Andre Dicaire