Monitor Client Service Connected, Database Disconnected?

[zilch321]

I'm having issues getting the Monitor Client to run on systems other than the Veeam Server in my environment. Launching the Veeam client on the same server where the Monitor is installed is no issue. If however I Install the client on another system in the same subnet I can only get a partial connection. The Service lists itself as connected via the client, the Database does not. I am using the same domain user account on both systems so permissions shouldn't be an issue. Does anyone know what would cause this to work on the localhost but not on another host in on the same subnet? There is no firewalls between these systems or running on the hosts.

2/8/2010 1:38:22 PM Generic 0x1CCC main "Veeam Monitor for VMware version 4.5.0.189"
2/8/2010 1:38:22 PM Generic 0x1CCC main "Running at ifshvc01.xxxx.com"
2/8/2010 1:38:22 PM Generic 0x1CCC main "Local time is UTC -5"
2/8/2010 1:38:22 PM Generic 0x1CCC main "WinVer=Microsoft Windows Server 2003 Standard Edition; Platfrom=32"
2/8/2010 1:38:22 PM Generic 0x1CCC main "UserIsAdmin=true; Username=Corp\UsernameChanged"
2/8/2010 1:38:22 PM Inform 0x1CCC main "Change the current directory D:\Program Files\Veeam\Veeam Monitor for VMware succeded.
"
2/8/2010 1:38:22 PM Inform 0x1FE8 GUI "Find 4.0 client: D:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
2/8/2010 1:38:23 PM Generic 0x1FE8 GUI "Monitor started on host ifshvc01"
2/8/2010 1:38:23 PM Inform 0x1F5C pipe "Starting pipe client..."
2/8/2010 1:38:23 PM Inform 0x1F5C pipe "Pipe client started"
2/8/2010 1:38:39 PM Error 0x1FE8 GUI "Database disconnected (IFSHVC02\SQLEXPRESS\veeam_mon)"

[Vitaliy S.]

Hello,

Can you please check that your SQL server is configured for remote connections, also there is an existing topic that might help Solution - Cannot connect remote via Veeam Client

Thank you!

[zilch321]

Switched the user running the veeam service and the user used to connect to the database to domain accounts. Enabled the SQL Browser service. That seems to have fixed this issue.