Domain service uses remote domain as a local one

[ThHagel]

Hello community,

this is a support request that I already addressed to NI using my SSP - but unfortunately it's not possible to quickly get in touch with specialists using that path. So I hope to find someone who's experienced enough for a serious Domain-Service-Problem (I know, most will stop reading here).

so here we go........

we encounter a problem with the NI-Domain-Service applied within a LabVIEW-DSC-Project (LabVIEW and DSC 2010 w/o SP).

Our application is installed on multiple PCs and uses local domains on each of them. The local domain names are the same on each PC. The PCs are connected within a common network on the customers site.

Now the problem:

the local Domain hosted on one of the PCs is recognized by the other PCs as their own local domain!
Please see the attached screenshot. You’ll see that a local domain is hosted on a remote PC.
This is of course unwanted and leads to misbehaviors of the complete user-management (including very chaotic ones).


What could be important to know:

- The local domain was initially created on one of the PCs and has been deployed to the others
- The only PC that uses its really own local domain is the one on which we initially created it
- All other PCs connect somehow to that first PC and use that remote domain as their own local domain, instead of using their own really local ones.
- First deploy was done by copy/paste of the Domain-Folder
- To ensure the deploy method wasn’t the root cause, we also tried with the export/import function of the domain manager with the same result
- To check for a possible workaround, we also tried to setup local domains with different names - after reboot all local domains were again linked to the first PCs domain.
- Even if the local domain gets removed on a misbehaving PC - after a reboot the first PCs domain is again available as the local one.
- We tried to create a new domain on a PC not connected to the others - after deploy to the target PCs again the first PC’s domain was used by all others


The core questions are:

- What could be the reason for the domain-service to use a Domain of a remote PC as its own local domain?
- What setting of the system environment could influence the domain-service to end up with that behavior?
- Where does the domain-service store its information and how can it be reset to default (to delete the domain-folder doesn’t help)?


The PCs have been recently installed (WinXP SP3) and integrated to customers system environments. The concerned application is fully tested and working well, but can’t be released because of the problems with the user-management. 

Thanks in advance for any input!

With best regards,
Thomas