VBR 12.3 console fails to connect to remote server: The logon attempt failed

No bug that I am aware of with 12.3. Can you resolve the FQDN of the server using ping?  Same with IP to FQDN?  Also is the FW turned on and are the required ports open?  Is there another FW that could be blocking it?

There are many things to check but typically FQDN not working is DNS.

​@Chris.Childerhose: Please read my full post, not only the header.

It is, as the console doesn’t attempt to read the DNS.

I did read the full post not just the header thanks!  That is why I asked what I did and said that DNS is the issue.  If you put an entry in the hosts file does the FQDN work?

Maybe there is an entry in the hosts file that might cause trouble.

Does the VBR server (and the server the console is running on) have a DNS suffix set?

Are you testing the ping / nslookup using the hostname or the FQDN? Does both work?

Good points from Chris and Lukas. 
Is it possible for you to check from another system (maybe you can quickly deploy a Test-VM client) with a v12.3 Console installed - just to check if the issue is related to your system, your VBR, or anything else.

Cheers, Markus

​Thanks, @Chris.Childerhose ​@lukas.k ​@Dynamic 

• Both NsLookup and Ping accept both hostname and FQDN
• Ports are open as logon via the IP address is successful
• Test-NetConnection in PS of the ports are successful
• Adding FQDN in Hosts file makes no change
• I have been running VBR through all versions from 9.5 to 12.3; only 12.3 sports this issue
• Our DNS (Active Directory) setup has ran flawlessly for about 15 years
• Server is a virtual Windows Server 2022 running for a year or so with no issues and nothing  else than VBR and its database(s) installed
• An install of the VBR console on another virtual server behaves identically: Logon attempts fail for hostname and FQDN but succeed for IP address

I would check this link as maybe there is some new ports (I think there is in 12.3) for the console to communicate to the Veeam Server - https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120#backup---replication-console

​@Chris.Childerhose: I did for the two mandatory ports: 9392 and 9420.

Also 9396, 9401, and 10003 are open.

And, as mentioned, logon via the IP address is successful.

Then at this point I would suggest opening a support ticket to get further assistance.  There is only so much we can offer from the community and everything appears to be working as expected to allow the connection.

​@Chris.Childerhose: Yes, it seems so. Thanks anyway.

I’ve opened a case for this: 07560868

Sounds good.  Let us know what you find and the solution if there is one.

I received this message:

Dear Customer,

This is Veeam Support with a system generated courtesy notification.

Unfortunately, due to low support staff availability we were unable to process your request. This support case has been archived automatically.

So, when not even read, I use the offered option to Talk to Manager:

If you believe this is in error, please reach out to our management team via 'Talk to Manager' option on the portal.

I’ll be back.

I ran into the same issue just now upgrading from 12.2.0.334 to 12.3.0.310. Connecting to the VBR server from a remote PC (jumpbox or other workstation) does not work anymore via hostname. It shows “logon attempt failed” however It does work with IP address though.

Clearly a bug. 

I just tested this and connected to one of many VBR servers we have running 12.3 (upgraded from 12.2) without issue using the FQDN.  So not sure why it is not working for others.

Same issue here but the case is different.

I migrated 2 Veeam Backup & Replication servers on 2 new ones, using the veeam procedure (stop old, install new, point to the same mssql db, then restore config on itself (for credentials)). From 12.3.0.310 to 12.3.0.310. On former server I was not having the issue, but i do have it on the new one… connect on IP is ok, connect on hostname is not. Everything works fine for backups.

- DNS is ok (and reverse)
- tried with servername only and servername.domain
- Checked SPN’s and seems ok (cannot check old servers SPN’s as old servers have been removed)
- local firewall is ok
- test-netconnection is ok for console port (9392) and ip or servername or servername.domain

- local console works fine on “localhost” and servername and servername.domain

Services are using a service account (like on old servers).

Case open to support, will give feedback here if resolved.

I solved my case by sending the System Event logs of the computer i’m launching the console from.

I saw a Kerberos error message about SPN misconfigured on the computer account instead of the service account, so i did :

setspn -Q VeeamBackupSvc/VeeamServerName

to see where the spn are registered, in my case it’s registered on the computer object

so i did :

setspn -D VeeamBackupSvc/VeeamServerName VeeamServerName$
setspn -D VeeamBackupSvc/VeeamServerName.Domain VeeamServerName$

and then

setspn -A VeeamBackupSvc/VeeamServerName Domain\VeeamServiceAccount
setspn -A VeeamBackupSvc/VeeamServerName.Domain Domain\VeeamServiceAccount

(replace VeeamServerName, Domain, and VeeamServiceAccount with your own ofc)

and it works !!!

Great to hear you resolved this and thanks for sharing the solution with the community.  👍