![]() Internally we don't see this behaviour, so i'm guessing it must be the Pulse Secure. When the user successfully can connect, i get a reply to my pings. ![]() I cannot ping our gateway by hostname or ip as well. I've have connected to the users laptop using Teamviewer, to see what's going on.Įven while they are succesfully connected, i'm not able to ping our Domain controller by hostname or IP. We only have a few external users during day-time. They receive the same error and after a while and some tries they can connect. Users are starting to work, make connection to our internal network and try to start an RDS session. Type a valid Remote Desktop Gateway server addressĪfter waiting some time, and trying to connect, out of the blue they can connect.Ģ. Select one of the following to download the detailed step-by-step configuration guides. You can use either the LDAP or RADIUS protocol. Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Azure MFA Server integrates with your Juniper/Pulse Secure SSL VPN appliance to provide additional security for Juniper/Pulse Secure SSL VPN logins and portal access. After this happends they are no longer able to log on and receive an error: A user sucessfully connects using the Pulse Secure client, logs on the RDS farm and after some time, while being at work, the session seems to freeze/ disconnect. Randomly we receive calls from external user who are complaining about the following:ġ. Remote users are logging in, using the Pulse Secure (Used to be Juniper Junos Pulse) VPN client.Īfter setting up a connection to our internal network, the users use a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |