Only time I’ve seen this error was if the services aren’t all started or a version mismatch in the windows consolde. Did you try with the FQDN? You can ping the gateway? The server is on the network?
Only time I’ve seen this error was if the services aren’t all started or a version mismatch in the windows consolde. Did you try with the FQDN? You can ping the gateway? The server is on the network?
@kciolek Hello, yes, everything is okay from the network side..
Is the VBR server “localhost” - so is this the correct target?
In case yes, I’d suggest to reboot the server once more. If that doesn’t help, you could open a Veeam support ticket to get more detailed assistance.
Are there any errors in the Windows event log that could be related to this?
Best regards
Lukas
@lukas.k Hello Lukas,
I’m directly connected via RDP to the VBR server. That was always the case how I accessed the VBR console. Tried multiple restart already, services all up and running
Is the VBR server “localhost” - so is this the correct target?
In case yes, I’d suggest to reboot the server once more. If that doesn’t help, you could open a Veeam support ticket to get more detailed assistance.
Are there any errors in the Windows event log that could be related to this?
Best regards
Lukas
@lukas.k Hello Lukas,
I’m directly connected via RDP to the VBR server. That was always the case how I accessed the VBR console. Tried multiple restart already, services all up and running
Then open a support ticket as the console should launch with all services running.
Only time I’ve seen this error was if the services aren’t all started or a version mismatch in the windows consolde. Did you try with the FQDN? You can ping the gateway? The server is on the network?
@kciolek Hello, yes, everything is okay from the network side..
I would try rebooting, and if you still have the issue open a case with support.
Have you tried logging in through the web UI? I recently had a case with a customer where we couldn’t connect via the Windows client, but accessing it through the web UI worked without any issues.
We don´t have a final solution for the issue but after a reboot we where able to connect via both consoles.