Comprehensive data protection for all workloads
Post Reply
Papa4x
Lurker
Posts: 2
Liked: never
Joined: Feb 23, 2009 12:37 pm
Contact:

Cannot connect to the host's administrative share, two nic's

Post by Papa4x » Feb 23, 2009 1:18 pm

We receive the following warning:

Cannot connect to the host's administrative share. Host: [xxx.xxx.xxx.xxx].

The Virtual machine has two nic's, one public and one private.
The error mentions the public ip-address.

How can I tell Veeam to use the private address?

Tia

Gostev
SVP, Product Management
Posts: 24474
Liked: 3414 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Cannot connect to the host's administrative share, two nic's

Post by Gostev » Feb 23, 2009 4:56 pm

I need to check with developers on how we determing IP address to use... I assume it's simple DNS query. Could you check what IP is returned by your DNS if you perform nslookup on the VM name, is it public or private?

Papa4x
Lurker
Posts: 2
Liked: never
Joined: Feb 23, 2009 12:37 pm
Contact:

Re: Cannot connect to the host's administrative share, two nic's

Post by Papa4x » Feb 23, 2009 9:18 pm

DNS returns a private address

Gostev
SVP, Product Management
Posts: 24474
Liked: 3414 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Cannot connect to the host's administrative share, two nic's

Post by Gostev » Feb 24, 2009 1:17 pm

OK, here's what I found out:
- Veeam Backup gets first IP address returned by VMware API
- VMware API uses VMware Tools to collect the IP address data

Right now workaround is not clear, may be disabling/enabling the public address will help.

We will try to address this issue in the next update for you.

Superkikim
Influencer
Posts: 16
Liked: 2 times
Joined: Jul 15, 2010 9:26 pm
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Superkikim » Jul 16, 2010 8:21 pm

Hi.

I get the same problem . But my virtual machine has only one nic. However, it is the vcenter and veeam server. Don't now if this is a problem...

Win2003std64 in english...

Creating snapshot
VssGAConn: Failed to connect. Errors:
"Cannot connect to the host's administrative share. Host: [xxx.xx.x.x]. Account: [OVH-VCENTER\Administrator].
Win32 error:No network provider accepted the given network path.
Code: 1203
"

Gostev
SVP, Product Management
Posts: 24474
Liked: 3414 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Gostev » Jul 16, 2010 8:28 pm

Are you able to open \\xxx.xx.x.x\admin$ with Windows Explorer while logged on to your Veeam Backup server as OVH-VCENTER\Administrator?

Superkikim
Influencer
Posts: 16
Liked: 2 times
Joined: Jul 15, 2010 9:26 pm
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Superkikim » Jul 26, 2010 11:09 am

Gostev wrote:Are you able to open \\xxx.xx.x.x\admin$ with Windows Explorer while logged on to your Veeam Backup server as OVH-VCENTER\Administrator?
No, the result is: No network provider accepted the given network path. But I guess I know why... This is a rented dedicated server. The network configuration is kind of special ... It uses the physical host gateway as gateway for the VMs but it is not in the same subnet as the virtual machine itself.

i.e. (fictive IPs):

Physical host IP: 172.30.12.8
Phyiscal gateway: 172.30.12.254

VM IP: 10.0.0.1
VM Gateway: 172.30.12.254
VM subnet mask: 255.255.255.255

If I use \\localhost\admin$ or \\hostname\admin$ it works.

For now, I have given up on VSS and uses vmware tools quiescing. But VSS could be an asset for sure.

Vitaliy S.
Product Manager
Posts: 22777
Liked: 1526 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Vitaliy S. » Jul 26, 2010 12:07 pm

With an upcoming v5 release, you will no longer need a direct network connection to guest VMs in order for Veeam VSS to work. This would definitely be helpful in the current situation.

Superkikim
Influencer
Posts: 16
Liked: 2 times
Joined: Jul 15, 2010 9:26 pm
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Superkikim » Jul 26, 2010 10:28 pm

Will the license be the same ? or should I wait for version 5 before to buy ?
When is it supposed to be released ?

Gostev
SVP, Product Management
Posts: 24474
Liked: 3414 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by Gostev » Jul 27, 2010 12:41 am

With VEEAM, all upgrades are "free" for customers with maintenance agreement in force - including major releases.
We are aiming to release it in late Q3.

iav
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 24, 2011 5:24 pm
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by iav » May 14, 2015 8:36 pm

Have same error with VM Windows 2012 R2 and ms exchange web access cluster ("windows network balancin cluster, WNLB).
Veeam tryes to connect to asmin share via cluster address.
nslookup on veeam server by vm name returns correct (node private, not clustered) IP.

How to workaround it?

error message:

Code: Select all

14.05.2015 23:27:28 :: Processing Exchange-CA-01 Error: Cannot upload guest agent's files to the administrative share  [\\x.x.x.50\ADMIN$].
Cannot upload the VSS package.
Cannot copy file. Source file: [C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll]. Target file: [\\x.x.x.50\ADMIN$\VeeamVssSupport\VeeamVssSupport.dll].
CopyFile() failed.
Win32 error:The system cannot find the file specified.
 Code: 2

Code: Select all

C:\>nslookup exchange-ca-01

Name:    exchange-ca-01.xx.xx
Address:  xx.xx.xx.36

alanbolte
Expert
Posts: 635
Liked: 172 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by alanbolte » May 15, 2015 7:08 am 2 people like this post

You can tell Veeam v8 not to use the cluster address by creating the following registry value on your Veeam B&R server:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Type: REG_MULTI_SZ (multi-string value)
Value name: NLBClusterPrimaryIps

The first line of the string should be the cluster IP address. If you have any other NLB clusters, add their cluster IP addresses as separate lines.
Do not add private node IP addresses to this registry value.

If you're running v7, you will need to upgrade before this will work.

iav
Influencer
Posts: 11
Liked: 1 time
Joined: Mar 24, 2011 5:24 pm
Contact:

Re: Cannot connect to the host's administrative share, two n

Post by iav » May 15, 2015 1:29 pm

Thank you, alanbolte!
Problem is solved!

Post Reply

Who is online

Users browsing this forum: Google [Bot], wishr and 46 guests