{"id":2561,"date":"2019-03-25T17:40:09","date_gmt":"2019-03-25T20:40:09","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain-windows-xpwindows-xp\/"},"modified":"2019-09-19T09:36:51","modified_gmt":"2019-09-19T12:36:51","slug":"configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain-windows-xpwindows-xp","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/configuring-remote-domains-in-machines-that-are-not-part-of-a-microsoft-network-domain-windows-xpwindows-xp\/","title":{"rendered":"Configuring Remote Domains in machines that are not part of a Microsoft network domain (Windows XP\/Windows XP)."},"content":{"rendered":"

Introduction<\/h3>\n

When configuring a Client Remote Domain in Studio, the E3 Studio of the Client machine access the files of the Server Domain on the path indicated in the Client Domain configuration. This path can be a folder created locally, in the Client Domain machine, or can be a folder share of the Server Domain on the remote machine, accessed via network. In this case, the share must be accessed remotely by the SYSTEM user. When the machines belong to a Microsoft network domain, the SYSTEM user has permissions to access the share without problems. However, when machines are only on the same workgroup, this permission must be explicitly defined.<\/p>\n

From version 3.0 on, where the functionality of Remote Domains<\/b> is available, E3 Server always runs as a service on the SYSTEM account. Services which use the SYSTEM account start on the system context without credentials, that is, without user and password authentication. These services, running without a Microsoft network domain, and which want to access network resources, have their access denied because of a lack of credentials and for using a null session.<\/p>\n

This article shows which configurations are needed when both machines are running Windows XP Service Pack 2.<\/p>\n

General Configurations<\/h3>\n

The configurations displayed next must be done on the machine running the Server Domain. This configuration must be done directly on Windows Registry. In this case, follow these procedures:<\/p>\n

    \n
  1. \n
    Access the key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Lanmanserver\\parameters<\/b>.<\/div>\n<\/li>\n
  2. \n
    Create the variable RestrictNullSessAccess<\/code>, of type DWORD<\/b>, and set its value to 0.<\/div>\n<\/li>\n<\/ol>\n

    \"\"<\/p>\n

    According to Microsoft, the key RestrictNullSessAccess<\/code> specifies whether the server limits access to the system for users logged on without user and password authentication. Possible values are:<\/p>\n

    \n