Month: July 2021

Situation: The client has Veeam backup problem with this error: 

[29.07.2021 06:52:31] <04> Error Unable to establish authenticated client-server connection.
[29.07.2021 06:52:31] <04> Error A call to SSPI failed, see inner exception. (System.Security.Authentication.AuthenticationException)
[29.07.2021 06:52:31] <04> Error at System.Net.Security.NegoState.StartSendAuthResetSignal(LazyAsyncResult lazyResult, Byte[] message, Exception exception)
[29.07.2021 06:52:31] <04> Error at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
[29.07.2021 06:52:31] <04> Error at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
[29.07.2021 06:52:31] <04> Error at System.Net.Security.NegoState.ProcessAuthentication(LazyAsyncResult lazyResult)
[29.07.2021 06:52:31] <04> Error at System.Net.Security.NegotiateStream.AuthenticateAsServer(NetworkCredential credential, ProtectionLevel requiredProtectionLevel, TokenImpersonationLevel requiredImpersonationLevel)
[29.07.2021 06:52:31] <04> Error at Veeam.EndPoint.Core.CForeignInvokerServer.AuthenticateAsServer(Socket client)
[29.07.2021 06:52:31] <04> Error No authority could be contacted for authentication (System.ComponentModel.Win32Exception)

Troubleshooting: From the log (C:\ProgramData\Veeam\Endpoint\Agent_Backup), we also find: Error [ProxyThrottling] Error while setting throttling, sourceIPs [10.255.255.59,10.255.255.58,10.0.0.104], targetIPs [10.0.0.92]. The target server is multihomed server with two Networks connections (10.255.2550/24 for SAN and 10.0.0.0/16 for LAN).

Resolution: Disable Automatic selection in Backup Repository and change it to The following server.

Situation: The client has Veeam backup problem with this error: Unable to read data from the transport connection: Unable to establish authenticated client-server connection

Troubleshooting: From the log (C:\ProgramData\Veeam\Endpoint\Agent_Backup), we also find: Error [ProxyThrottling] Error while setting throttling, sourceIPs [10.255.255.59,10.255.255.58,10.0.0.104], targetIPs [10.0.0.92]. The target server is multihomed server with two Networks connections (10.255.2550/24 for SAN and 10.0.0.0/16 for LAN).

Resolution: Disable Automatic selection in Backup Repository and change it to The following server.

Situation: The client has Veeam backup problem with this error: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. (System.IO.IOException)

Troubleshooting: From the log (C:\ProgramData\Veeam\Endpoint\Agent_Backup), we also find: Error [ProxyThrottling] Error while setting throttling, sourceIPs [10.255.255.59,10.255.255.58,10.0.0.104], targetIPs [10.0.0.92]. The target server is multihomed server with two Networks connections (10.255.2550/24 for SAN and 10.0.0.0/16 for LAN).

Resolution: Disable Automatic selection in Backup Repository and change it to The following server.

Situation: The client has Veeam backup problem with this error: No authority could be contacted for authentication (System.ComponentModel.Win32Exception).

Troubleshooting: From the log (C:\ProgramData\Veeam\Endpoint\Agent_Backup), we also find: Error [ProxyThrottling] Error while setting throttling, sourceIPs [10.255.255.59,10.255.255.58,10.0.0.104], targetIPs [10.0.0.92]. The target server is multihomed server with two Networks connections (10.255.2550/24 for SAN and 10.0.0.0/16 for LAN).

Resolution: Disable Automatic selection in Backup Repository and change it to The following server.

Situation: When running Office 365, you may receive Your computer’s Trusted Platform Module has malfunctioned. if this error persists, contact your system admin with error code 80090034.

Troubleshooting 1: Cleared your TPM.

To clear the TPM

1. Open the Windows Defender Security Center app.
2. Click Device security.
3. Click Security processor details.
4. Click Security processor troubleshooting.
5. Click Clear TPM.
6. You will be prompted to restart the computer. During the restart, you might be prompted by the UEFI to press a button to confirm that you wish to clear the TPM.
7. After the PC restarts, your TPM will be automatically prepared for use by Windows 10.

Troubleshooting 2: Turn on or turn off the TPM (available only with TPM 1.2 with Windows 10, version 1507 or 1511)

To turn on the TPM (TPM 1.2 with Windows 10, version 1507 or 1511 only)

1. Open the TPM MMC (tpm.msc).
2. In the Action pane, click Turn TPM On to display the Turn on the TPM Security Hardware page. Read the instructions on this page.
3. Click Shutdown (or Restart), and then follow the UEFI screen prompts.After the computer restarts, but before you sign in to Windows, you will be prompted to accept the reconfiguration of the TPM. This ensures that the user has physical access to the computer and that malicious software is not attempting to make changes to the TPM.

To turn off the TPM (TPM 1.2 with Windows 10, version 1507 or 1511 only)

1. Open the TPM MMC (tpm.msc).
2. In the Action pane, click Turn TPM Off to display the Turn off the TPM security hardware page.
3. In the Turn off the TPM security hardware dialog box, select a method to enter your owner password and turning off the TPM:
   • If you saved your TPM owner password on a removable storage device, insert it, and then click I have the owner password file. In the Select backup file with the TPM owner password dialog box, click Browse to locate the .tpm file that is saved on your removable storage device, click Open, and then click Turn TPM Off.
   • If you do not have the removable storage device with your saved TPM owner password, click I want to enter the password. In the Type your TPM owner password dialog box, type your password (including hyphens), and then click Turn TPM Off.
   • If you did not save your TPM owner password or no longer know it, click I do not have the TPM owner password, and follow the instructions that are provided in the dialog box and subsequent UEFI screens to turn off the TPM without entering the password.

Troubleshooting 3: Modifying two registry keys may also help you solve the problem.
a) Go to the Registry Editor (press Win + R, enter regedit)
b) Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb. Create a new REG_DWORD value called “ProtectionPolicy” and leave the value at 1.
c) Go to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity. Inside “Identity”, create a new REG_DWORD value called “EnableADAL” and leave the value at 0.
d) Restart computer and try again to login from Office 365 to activate it.

Troubleshooting 4: Setup Outlook Manually

If you have this problem to setup Outlook, try setup Outlook manually.

Situation: The client has a problem to access her remote desktop with this message:

Your Remote Desktop Service session has ended, possible for one the following reasons:

The administrator has ended the session.

An error occurred while the connection was being established.

A network problem occurred.

Troubleshooting: 1. Login locally and check the Windows update. Your may need to restart the computer.

2. If you are not on site, you may try remote shutdown command, for example: shutdown /m \\pcname /r

Situation: The client has Veeam v95. Veeam backup failed with this message: Error: No connection could be made because the target machine actively refused it 10.0.0.104:6184.

Troubleshooting: We have a problem to login this target server. It seems to us it has a connection issue. Rebooting fixes the problem.

Situation: The client can’t access his Windows 10 Pro computer remotely with this message

The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the remote tab of the System Properties dialog box.


Troubleshooting: 1. The error suggests that the domain controller cannot be contacted. It could be the DNS issue. Make sure you are using Domain Controller as DNS.
2. The client should be a Windows 10 computer.
3. Enable NLA using Properties. 1] On the remote server, press Win + R to open the Run window and type the command sysdm.cpl. Press Enter to open the System Properties window.

2] In the Remote tab, make sure the option for “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” is checked. 

Situation: The client can’t access the internet. For troubleshooting, we ask he to ping default gateway, for example, ping 192.168.1.254. She gets general failure.

Troubleshooting: 1. run netsh to enable autoconfig,

netsh wlan set autoconfig enabled=yes interface=”Wireless Network Connection” or “Wi-Fi” for example

netsh wlan set autoconfig enabled=yes interface=Wi-Fi

Restart the computer.

2. Run netsh to delete arp, for example

netsh interface ip delete arpcache

Restart the computer

3. Run netsh reset, for example

netsh int ip reset c:\resetlog.txt

Restart the computer

4. Run admin command prompt, run DISM/SFC:dism.exe /online /cleanup-image /restorehealth

then

SFC /SCANNOW

Restart the computer.

5. If your computer has 6to4, that may cause the problem. Try to disable it by running this command;

netsh int ipv6 isatap set state disabled
netsh int ipv6 6to4 set state disabled
netsh interface teredo set state disable

6. Reset winsock

netsh i i r r

netsh winsock reset

Then reboot.

7. Run safe mode with network.

8. It could be security software issue. Try to disable the firewall or security software for a test.

9. Run network troubleshooting on Windows 10. It find the problem but can’t fix it.

10. Run System restore but the system restore is off.

11. Finally, we fixe the problem by run Windows Recovery.

Situation: the client has a problem to run Veeam backup with this error: Could not perform threshold check for backup location
“\10.0.0.178\qnapbackup\host02” due to space info retrievement fail!
Error: Invalid Signature.

Resolution 1: Make sure use the correct username to access backup storage, for example NAS\username.

Resolution 2: The client just join the NAS to their domain, they need to access the NAS using domainname\username.

Resolution 3: Force the credentials renew in Veeam DB. Please follow this post: How to force the credentials renew in Veeam DB

Resolution 4: Run rescan on Repository by going to Backup Infrastructure.

Right-click on the storage and then Rescan.