FelixYan's Posts

Hi justanothernewguy, The client log shows that your cert could not be verified by broker side: 2015-05-26 07:27:53.017+-5:00 DEBUG (1794) [libcdk] BasicHTTP: curl (TEXT) on request 0382DA38: error:14099004:lib(20):func(153):reason(4) 2015-05-26 07:27:53.017+-5:00 DEBUG (1794) [libcdk] BasicHTTP: curl (TEXT) on request 0382DA38: Closing connection 1 1) If your cert is issued by a root CA or intermediate CA? 2) Client 3.5/3.51 has just released, could you please try with that version? 3) Could you collect the broker full levels logs? Thanks, Felix

Hi Dar 88, What's your View Client version? We fixed a similar connection flood problem in View Client side which is related with HTTP(s) secure tunnel. Would you please try to upgrade all your View Client to 3.4 or later(3.5 is available now)? With the new Client version, you can enable your secure tunnel again, then the RDP access from the external network could be work fine. Thanks for reporting the issue! Regards, Felix

Hi YoungJus11 and All, The issue has been addressed in Windows View Client. It's a DNS related problem and Client always contact DNS server which blongs to a non-interactive network interface. The fix has been involved in the subsequent release. For Mac client, we will double check in our local and update you later. Thanks for reporting the issue! Thanks, Felix

Hi Chris, Would you please let me know your full computer name and domain name? Computer->Properties to get the two values. The problem should happen when your primary domain is different from the primary DNS in your computer settings. Thanks, Felix

Hi Barry, Would you please let me know your full computer name and domain name? Computer->Properties to get the two vlaues. Looks like the problem only happen when your primary domain is different from the primary DNS in your computer settings. Thanks, Felix

Hi Barry, Thanks very much for your quickly response! So this is a known issue which we're working on. Please let me know if you have any special AD domain configuration in your environment. It's hard to reproduce the problem in my local. Will update you later once I have some progresses. Thanks, Felix

Hi Spacereamer and cmmcooper, Would you please try launch view client as "Run as administrator" option and check if it works? We're working on the problem and will update you later. Thanks, Felix

Thanks, nzorn and vRickE! This is a bug for View client 2.2. Different logged in user can't share the VDM_SERVER. The issue has been fixed and will be involved  in the next release(2.3). You can try it later, thanks! Regards, Felix

Hi Chris, Please make sue that: 1) The users you mentioned are all domain users(local user can not be used for login as current user feature). 2) Disable the login as current user function, input the user name and password manually, make sure the authentication can be successful. 3) After you installed view client with login as current user feature, make sure your machine has restarted. During the problem happened, would you please help to check the Event viewer. For Win7, you can do as this: Control Panel-> All Control Panel Items-> Administrative Tools-> Event Viewer In Event Viewer dialog, open the left trees: Event Viewer(Local)-> Windows Logs-> Application And check is there any DC related errors. If yes, please upload the error info here. Then remove the client machine from domain and re-join again. Check if it works. BTW, does the problem only happen in one special machine or all your client machines? Thanks! Regards, Felix