For server requests, the front end is populating reservation.remoteIP when the request is created. This causes the back end to essentially skip the stage where it waits for the user to acknowledge the request is ready – they don't have to click the Connect button.
The back end then immediately proceeds to the stage where it checks for a user connection. For normal reservations, the front end inserts a 'initialconnecttimeout' entry into the computerloadlog table when Connect is clicked. This isn't happening for server requests. As a result, the back end is generating warning messages in vcld.log for ever server request when it processes the reserved state.
This is benign but should be fixed. An easy way would be for the backend code could always insert an 'initialconnecttimeout' entry for server requests.