new1234.jpg

Archive

Posts Tagged ‘DNS’

Veeam: Client error: NFC storage connection is unavailable

December 10th, 2014 1 comment

Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:

Processing ‘DC01’ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].

image

 

Solution

When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01

In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.

Make sure you have:

– Added the vSphere host in DNS, create a A record in your DNS server

Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server

 

End result

 

image

 

More information: Veeam

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: VMware Data Protection (VDP) 5.5 IP/DNS could not be resolved

March 18th, 2014 1 comment

During the network configuration at the VMware Data Protection (VDP) appliance I received this warning message:

IP/DNS could not be resolved. Please check the hostname, domain, and DNS values for forward and reverse lookup validation

 

image 

 

Troubleshoot:

VMware VDP whitepaper: Before you deploy vSphere Data Protection, an entry needs to be added to the DNS Server for the appliance IP address and FQDN. This DNS Server must support forward and reverse lookup. Failure to have DNS set up properly can cause many runtime or configuration issues.

As you can see, the nslookup failed:

  image

Solution:

Add the domain and search domain in the /etc/resolv.conf file

 image

And make sure you’ve created a correct PTR record at the DNS server for reverse DNS functionality, at the DNS server:

 image

Select: Create associated pointer (PTR) record

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Cisco:“Authentication failed” na DNS security update 953230 (MS08-037)

February 17th, 2009 No comments

Kan zijn, bijvoorbeeld vandaag in het geval van bij een klant, dat de Cisco VPN niet meer werkt met de melding “authentication failed”.

 

Na controle van de PIX alsmede de server blijkt dat op de server de Internet Authentication Service was gestopt.

 

Dit problem zal zich vaker kunnen voordoen omdat het ontstaat na een security update van Microsoft:

DNS security update 953230 (MS08-037) http://support.microsoft.com/kb/956189

 

Oplossing is een aanpassing in het register:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters

Daar de key ReservedPorts aanpassen door de poorten van IAS toe te voegen:

1645-1646

1812-1813

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: Cisco, Microsoft Tags: ,