-
- Influencer
- Posts: 21
- Liked: never
- Joined: Feb 01, 2010 7:41 pm
- Full Name: Shawn Barnhart
- Contact:
Connect non-domain monitor client to domain-member server?
Hi-
I'm wondering if its possible for a non-domain member Veeam ONE monitor client to connect to a domain member server running the Veeam ONE Monitor server?
I've added a local user account to the server with the same username and password as is being used on the non-member client and added that same account to all the Veeam One security groups on the server, but I still get a "can't connect" error message.
The local user account can connect to the server with the monitor client when logged on locally, and a domain account can also connect when running the monitor client remotely.
I'm thinking that the connection to the server is using the local credentials in the format of "localmachinename\username" to connect and that's what's throwing it off, but there's no way to specify what remote credentials to use.
I'm wondering if its possible for a non-domain member Veeam ONE monitor client to connect to a domain member server running the Veeam ONE Monitor server?
I've added a local user account to the server with the same username and password as is being used on the non-member client and added that same account to all the Veeam One security groups on the server, but I still get a "can't connect" error message.
The local user account can connect to the server with the monitor client when logged on locally, and a domain account can also connect when running the monitor client remotely.
I'm thinking that the connection to the server is using the local credentials in the format of "localmachinename\username" to connect and that's what's throwing it off, but there's no way to specify what remote credentials to use.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Hi Shawn,
Yes, you're right, there is no way to specify a user account to connect to Veeam ONE Server, as by default we are using the account you're currently logged in. However, you should be able to use local accounts with the same names and passwords, at least I've seen it working for some of our clients (will verify that).
Anyway, our support has a KB article that might help you in this situation: http://cp.veeam.com/knowledgebase/article/KB1550/
Thanks!
Yes, you're right, there is no way to specify a user account to connect to Veeam ONE Server, as by default we are using the account you're currently logged in. However, you should be able to use local accounts with the same names and passwords, at least I've seen it working for some of our clients (will verify that).
Anyway, our support has a KB article that might help you in this situation: http://cp.veeam.com/knowledgebase/article/KB1550/
Thanks!
-
- Influencer
- Posts: 21
- Liked: never
- Joined: Feb 01, 2010 7:41 pm
- Full Name: Shawn Barnhart
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Vitaly,
Thanks, that KB article was perfect, I added the reg key and can now connect.
For what it's worth, I did create a matching local account (same username, same password, added to all the Veeam ONE local groups on the server) and it didn't work.
Thanks, that KB article was perfect, I added the reg key and can now connect.
For what it's worth, I did create a matching local account (same username, same password, added to all the Veeam ONE local groups on the server) and it didn't work.
-
- Expert
- Posts: 173
- Liked: 25 times
- Joined: Aug 23, 2010 8:30 am
- Full Name: Vitaliy Mzokov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Hey Shawn,
Thanks for the feedback.
As for your additional comment, this probably was related to some domain policies applied against a Veeam ONE Server, which prevent non-domain computers from connecting to domain machines.
I've got the same deployment scenario in my lab and I was able to connect to my Veeam ONE Server after utilizing the following command on my Veeam ONE Monitor client machine:
Hope it helps!
- VM.
Thanks for the feedback.
As for your additional comment, this probably was related to some domain policies applied against a Veeam ONE Server, which prevent non-domain computers from connecting to domain machines.
I've got the same deployment scenario in my lab and I was able to connect to my Veeam ONE Server after utilizing the following command on my Veeam ONE Monitor client machine:
Code: Select all
NET USE \\Veeam_ONE_server_address
- VM.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Mar 04, 2013 1:31 pm
- Full Name: Ronny Andreassen
- Contact:
Re: Connect non-domain monitor client to domain-member serve
None of these suggestions worked for me.
I'm curious, why is there no way to specify what credentials to use and is this something the veeam team is looking into implementing?
I'm curious, why is there no way to specify what credentials to use and is this something the veeam team is looking into implementing?
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Hi Ronny,
The steps provided in our KB article should address it, so I would suggest contacting our support team for assistance with this. On top of that, could you please share a bit more details on why domain account does not work for you? It would help us in addressing this problem in our future updates.
Thanks!
The steps provided in our KB article should address it, so I would suggest contacting our support team for assistance with this. On top of that, could you please share a bit more details on why domain account does not work for you? It would help us in addressing this problem in our future updates.
Thanks!
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
You *really* should add a credentials box for Veeam One Monitor.
The solution provided in the KB is really insecure.
By the way, the NET USE trick worked for me.
The solution provided in the KB is really insecure.
By the way, the NET USE trick worked for me.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
OK, good to know that you've solved it and thanks for the feature request.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Same problem with veeam ONE 7.X ??? I still can't connect to server from monitor client !
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Yes, there were no changes in regards to the configuration described above, so you should be using the techniques mentioned above.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Do http://www.veeam.com/kb1550 for 6.X still apply (same registry setting) ?
Thanks.
Thanks.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Yes, instructions from v6 should work.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Well it doesn't work for me. I tried the reg. tweak (DisableClientUserCheck 1). Can you confirm ? Should i open a case ?
picture : https://filex.univ-lorraine.fr/get?auto ... t2jdmePaO1
picture : https://filex.univ-lorraine.fr/get?auto ... t2jdmePaO1
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
I will verify with the devs.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
It appears that the reg key has stopped working in the latest release, thanks for pointing this out! As a workaround for now, please use "net use" cmdlet.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Thanks for your answer. I hope it will be fixed asap. It's very annoying for us !
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Our support team has updated the KB article with new instructions, that should address the authorization problem.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Just to be sure. On a workgroup (our case), we need :
- reg tweak
AND
- same user account and password on both veeam one and monitor ?
- reg tweak
AND
- same user account and password on both veeam one and monitor ?
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Yes, according to our QC team this is all that you need to do to make it work.
-
- Influencer
- Posts: 15
- Liked: never
- Joined: Feb 24, 2013 10:41 am
Re: Connect non-domain monitor client to domain-member serve
Reg tweak doesn't work alone, is this right ? (i just tried with no result at all)
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Connect non-domain monitor client to domain-member serve
Yes, you should also use the same user account.
Who is online
Users browsing this forum: No registered users and 5 guests