AnsweredAssumed Answered

Differtent domain login

Question asked by Marijn Van Den Heuvel on Jan 16, 2017
Latest reply on Jan 22, 2017 by Phil Welbourn

Like • Show 0 Likes0
Comment • 8

So I am trying to understand how the PDM login system works.

I am currently trying to add different users from different domains, that are connected true a VPN.

When I connect to the vault and want to make a vault view it asks for domain information, and I can't connect.

I know I probably need to add these users to PDM archive access panel, but these panel can't find the domain group.

I asked my var but he couldn't understand it and told me I need to hire them to do the implementation... Great advise....

Our ICT department says we need to register more users on our own server to get this.

But I am getting the feeling no-one understands it.

So I turned to the forums with all these awesome powerusers .

Do I need to login with domain/user or something like that?

Can someone show how me how they configured their archive login security with a multiple domain setup, and how they login on the other domains?

Marijn Van Den Heuvel Jan 18, 2017 7:38 AM

Correct Answer

Soo to attach a vault view, I need to use windows login credentials. NOT PDM LOGIN....

I did not know this.

Now I am able to attach an vault on another domain.

Now I only have an issue with read acces, but this is probably a matter of setting the host file.

See the reply in context

No one else had this question

Outcomes

Grant Chapman Jan 16, 2017 1:28 PM

I am having a little trouble understanding your question but I think I have the answer. The way PDM standard does licensing is the key to your issues I think. The licenses have to be handed out by the server that they are trying to enter. For example PDM server A is the one you control, your trying to let Bob and Sam into your PDM A. You must have PDM Standard Licenses for Bob and Sam in your server and they must be able to check them out to access the vault. So for example if Bob and Sam have their Solidworks license as standalone or on a difference network license server you are going to run into issues. I am working with my VAR right now on a work around... basically telling my PDM Vault server to look at Bob and Sam's License server (That they maintian) to check out a license for Bob or Sam, then hand the license to Bob or Sam from my PDM Vault. You can add rules or something to ensure that Bob or Sam can only check our their licenses from your server and not steal yours. Also to ensure that you or your employees don't accidentally steal Bob or Sam's licenses. Also another issue we had with VPN is that the timeout was set for something like 100 milliseconds, which is almost impossible to serve up over a VPN. So we had to do a registry hack to enable a much longer timeout.

Hope this helps!

Actions

Marijn Van Den Heuvel @ Grant Chapman on Jan 17, 2017 6:14 AM

Tnx for the reply, this surely helps, since as I see I will encounter these issues after I fixed this issue....

But not my issue currently.

I think I need to add users to the security setup (screenshot below) so that they can attach a vault view.

I think this list is populated by manage computer>Local users and groups.

How should I set this up?

Actions

Faur Arama Jan 17, 2017 7:23 AM

The users for the second domain must be defined in the first domain, where PDM resides. They must have access to the first domain. Also the PDM system verify, from time to time, if these users exists and witch are their permissions.

Actions

Charley Saint Jan 17, 2017 12:51 PM

Hello,

You actually just need to setup a Domain Trust so the local Domain Controller knows where to authenticate a user. Understanding Trusts

Actions

Marijn Van Den Heuvel Jan 18, 2017 7:38 AM

Soo to attach a vault view, I need to use windows login credentials. NOT PDM LOGIN....

I did not know this.

Now I am able to attach an vault on another domain.

Now I only have an issue with read acces, but this is probably a matter of setting the host file.

Actions

Phil Welbourn @ Marijn Van Den Heuvel on Jan 22, 2017 6:07 AM

I'm suffering from something similar - have users on a workgroup trying to connect to a vault to create the first view - I thought it would be enough to create a Windows user on the vault server that I could use from the client machines for the initial setup, but I get username/password error using that account. The vault is on a newly configured Server Essentials 2012 machine which by default creates its own domain.

Do we think the workgroup / domain setup could be the issue. I have reasons why i can't have the client machines join the domain of this extra server so hopefully that isn't the only fix :-)

Any pointers greatly appreciated...

Actions

Richard Bremmer @ Phil Welbourn on Jan 22, 2017 9:31 AM

The windows user needs to have the correct rights in the Archive Server Configuration and you might need to add the domain when logging in (this is really all about reading the dialog itself).

Actions

Phil Welbourn @ Richard Bremmer on Jan 22, 2017 2:27 PM

Thanks Richard,

Yes - correct rights in the Archive setup and I tried every conceivable combination of domain before username but to no avail. Once I reached 100% frustration I stepped away. So will attack it again refreshed next week :-)

Actions

8 Replies

Grant Chapman Jan 16, 2017 1:28 PM
Mark Correct
Correct Answer
I am having a little trouble understanding your question but I think I have the answer. The way PDM standard does licensing is the key to your issues I think. The licenses have to be handed out by the server that they are trying to enter. For example PDM server A is the one you control, your trying to let Bob and Sam into your PDM A. You must have PDM Standard Licenses for Bob and Sam in your server and they must be able to check them out to access the vault. So for example if Bob and Sam have their Solidworks license as standalone or on a difference network license server you are going to run into issues. I am working with my VAR right now on a work around... basically telling my PDM Vault server to look at Bob and Sam's License server (That they maintian) to check out a license for Bob or Sam, then hand the license to Bob or Sam from my PDM Vault. You can add rules or something to ensure that Bob or Sam can only check our their licenses from your server and not steal yours. Also to ensure that you or your employees don't accidentally steal Bob or Sam's licenses. Also another issue we had with VPN is that the timeout was set for something like 100 milliseconds, which is almost impossible to serve up over a VPN. So we had to do a registry hack to enable a much longer timeout.
Hope this helps!
Like • Show 0 Likes0
Actions
- Marijn Van Den Heuvel @ Grant Chapman on Jan 17, 2017 6:14 AM
  Mark Correct
  Correct Answer
  Tnx for the reply, this surely helps, since as I see I will encounter these issues after I fixed this issue....
  But not my issue currently.
  I think I need to add users to the security setup (screenshot below) so that they can attach a vault view.
  I think this list is populated by manage computer>Local users and groups.
  How should I set this up?
  Like • Show 0 Likes0
  Actions
Faur Arama Jan 17, 2017 7:23 AM
Mark Correct
Correct Answer
The users for the second domain must be defined in the first domain, where PDM resides. They must have access to the first domain. Also the PDM system verify, from time to time, if these users exists and witch are their permissions.
Like • Show 0 Likes0
Actions
Charley Saint Jan 17, 2017 12:51 PM
Mark Correct
Correct Answer
Hello,

You actually just need to setup a Domain Trust so the local Domain Controller knows where to authenticate a user. Understanding Trusts
Like • Show 0 Likes0
Actions
Marijn Van Den Heuvel Jan 18, 2017 7:38 AM
Unmark Correct
Correct Answer
Soo to attach a vault view, I need to use windows login credentials. NOT PDM LOGIN....
I did not know this.
Now I am able to attach an vault on another domain.
Now I only have an issue with read acces, but this is probably a matter of setting the host file.
Like • Show 0 Likes0
Actions
- Phil Welbourn @ Marijn Van Den Heuvel on Jan 22, 2017 6:07 AM
  Mark Correct
  Correct Answer
  I'm suffering from something similar - have users on a workgroup trying to connect to a vault to create the first view - I thought it would be enough to create a Windows user on the vault server that I could use from the client machines for the initial setup, but I get username/password error using that account. The vault is on a newly configured Server Essentials 2012 machine which by default creates its own domain.
  
  Do we think the workgroup / domain setup could be the issue. I have reasons why i can't have the client machines join the domain of this extra server so hopefully that isn't the only fix :-)
  
  Any pointers greatly appreciated...
  Like • Show 0 Likes0
  Actions
  - Richard Bremmer @ Phil Welbourn on Jan 22, 2017 9:31 AM
    Mark Correct
    Correct Answer
    The windows user needs to have the correct rights in the Archive Server Configuration and you might need to add the domain when logging in (this is really all about reading the dialog itself).
    Like • Show 0 Likes0
    Actions
    - Phil Welbourn @ Richard Bremmer on Jan 22, 2017 2:27 PM
      Mark Correct
      Correct Answer
      Thanks Richard,
      
      Yes - correct rights in the Archive setup and I tried every conceivable combination of domain before username but to no avail. Once I reached 100% frustration I stepped away. So will attack it again refreshed next week :-)
      Like • Show 0 Likes0
      Actions

Differtent domain login

Outcomes

Related Content

Recommended Content

Incoming Links