Veeam One Client remote access to Monitor Server

[pirx]

I'm trying to get access from a Veeam One Client on a terminalserver to my Veeam One instance. I've checked https://helpcenter.veeam.com/docs/one/d ... ml?ver=120 and added this to the firewall ruleset. What am I missing? DNS is working, VO server is reachable.

Source: Veeam ONE
Destiantion: Client Veeam ONE Server
Ports: TCP 139; 445 UDP 137
Used by Veeam ONE Client to communicate with the Veeam ONE Server.

This was not sufficient. I also had to add high ports (49157/tcp). Now I don't see any blocked requests in fw log anymore, but I still get an connection error.

Could not connect to Veeam One Monitoring Server specified in Settings < Client Settings

If I then click on "Reconnect" I get an error regarding DB connection. Which is kind of odd on a client. Maybe just a Gui error because there is no connection at all.



Logs:

Code: Select all

26.01.24 13:49:01 Generic 0x1780 GUI		"Pipe client has been created."
26.01.24 13:49:02 Warning 0x1780 GUI		"Service connection failed Address = \\sxxxxxx.net\pipe\VeeaMDCS Error = 0x78f"
26.01.24 13:49:02 Error   0x1860 n/a		"LoadAlarmTree FAILED: Communication with Veeam ONE Monitoring Server has been lost"
26.01.24 13:49:02 Info    0x1780 GUI		"UI location: Alarm Management"
26.01.24 13:49:02 Error   0x1860 n/a		"Load alarms for category FAILED:  Communication with Veeam ONE Monitoring Server has been lost"
26.01.24 13:49:02 Error   0x1860 n/a		"An error has occurred in loader: class CAlarmsManagementLoader. Error information follows:: Communication with Veeam ONE Monitoring Server has been lost because of HRESULT: 0x809c0002 (Unknown error 0X809C0002) - caught at [BaseLoader.cpp:82]. Diagnostic information follows
The exception of class CHResultException has been thrown in [PipeAlarmRequest.cpp:33]
[struct errinfo_comerror_ * __ptr64] = 0x809c0002: Unknown error 0X809C0002
  Description: Communication with Veeam ONE Monitoring Server has been lost"

[RomanK]

Hello prix,

As far as I know, ports TCP 139, 445 and UDP 137 should be enough.
Please open a support case and provide a case ID in this thread so we can collect all the additional details and investigate it accordingly.

Thanks

[pirx]

Those ports were definitely not enough, I found some old posts about dynamic ports that need to be opened. I was kind of surprised to see that the client is connecting via those ports to the server. I'll create a case next week.

[pirx]

# 07107122

[RomanK]

Hello prix,

Thank you for the case number. Please continue to work with our support engineers. I'm confident they will find the cause of this issue.

Thanks

[pirx]

No solution yet. It's possible that we have something configured on our Windows servers that is not the MS default. But without knowing which ports Veeam really uses for communication or what else Veeam One needs to be able to communicate, it's a bit hard to find what it is. No ports appear to be blocked, I see packets coming in to VO server (10.11.38.23) from the client (10.24.76.39). But then a RST/ACK is sent (from the VO client) and communication is terminated.

[RomanK]

Hello prix,

I can see that the support case has already escalated. That should mean that the T1 engineer confirmed that all is configured according to the documentation.

There is always a chance that something prevents the communication. As you've mentioned, something is probably not set as a default on the MS side. There is also a chance that some security hardware like traffic analyzers could affect communication. Anyway, our QA team must reproduce the configuration and confirm the issue. Please be patient, all support cases have a solution at the end.

Thanks