- Posts: 94
- Liked: 12 times
- Joined: Jul 23, 2012 3:48 pm
Isolated IP (10.100.a.x) which is the production IP of the VM, therefore that is what the isolated VM believes it's IP is.
Access IP: (10.100.a.y) which is an unused IP on our production network
I'm not really sure what I'm going wrong here. Any ideas? On this network with these VMs, DHCP is not used. Everything is manually assigned.
Also, not sure if it is related or not but from time to time I get the following message box error from Veeam: AcquireMksTicket Failed. vmRef: 'vm-6814' permission to perform this operation was denied.
Now, the AD account that Veeam runs was not granted full access to the vCenter environment. It was put in a custom role created with the required vCenter permissions list found in the forum. Again, not sure if that error has anything to do with Veeam or not, just throwing that out there.
Edit: Also I'm running B&R 188.8.131.52
- Veeam Software
- Posts: 18027
- Liked: 1531 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Users browsing this forum: No registered users and 33 guests