Hello, we are currently letting our users take their thin-client home with them and work via vpn. For that we copied our homeoffice profile, removed the auto-start and added a button that connects to vpn. I thought the Clients should behave just like our homeoffice clients but they aren’t manageable via the UMS. They are shown as offline and we can’t change their configuration, which is something that works with our standard homeoffice config. Any ideas why? Some screenshots:
(HYBRID = Clients with button, FEST = Standard homeoffice)
Hey Julian, can you ping the devices when the devices are red? Are they able to ping the UMS?
The IGEL Cloud Gateway (ICG) is required if the UMS and the devices are not in the same network.
Why is it required if it works fine with our standard config? We are not planning to implement the cloud gateway.
The UMS-Server is pingable and the Client is pingable under the adress that is shown as hardware adress in the local client informations.
Ok, great. Just in case, could you please check if you can connect via telnet (a.e.) to the device from ums like these:
telnet IpOfYourClient 30005
I’m able to mirror the client when putting in the IP from the informations. Does that help you? If not: How do I check the connection via telnet in the UMS?
From the endpoint, like these:
From UMS, assuming Windows: www.google.de/amp/s/winaero.com/test-remote-network-port-connection-in-windows-10/amp/
I tested the command on the server the UMS is running on with the result “TcpTestSucceeded : True”
and from the endpoint (s. Gif sent above)?
The commands all worked fine. The pingable IP is not in the lease list of eth0 though.
what do you mean by that?
btw. is time / date set correctly on that device?
I did everything like in the gif. At the end the IPs of eth 0 are being shown. The pingable IP is missing there.
However the client is suddenly shown green in the UMS with the right IP showing.
Could you try on another device if
and / or
makes the device appear green too?
Yes, it does.
Then, it seems that it‘s the „old topic“ that the last know IP isn‘t reported back after a Vpn connect.
Thanks for the answer! I’ll look into that
Thats what I added. Works fine so far.
Continue reading and comment on the thread ‘Moved IGEL Thin Clients from the office to home and now we they can’t conenct to the UMS’. Not a member? Join Here!
Learn more, search the IGEL Knowledge Base
Ask a question or comment on the above message thread?Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.
Submit a question, or Join Today!
Popular Message Threads
- Receiving error: “Citrix Receiver cannot create a secure connection in this browser” when launching a secure connection from Firefox on IGEL OS
- How to Install IGEL OS via a Bootable USB Drive
- Where to delete the certificates that cause ‘invalid certificate’ when trying to import an IGEL into UMS?
- How to change the default IGEL UMS admin password?
- IGEL UMS Universal Update Error: “could not resolve host name”
- IGEL UD3 (LX50) randomly get this error with Citrix: The X Request 130.1 caused error :”10: BadAccess ( attempt to access private resource denied) any ideas?
- Citrix connection via Netscaler Error: “AM_ERROR_AUTH_NETWORK_ERROR” on IGEL OS