A user is experiencing issues with remote shell on a PC – sometimes it works, sometimes it doesn’t. ControlUp suggests checking for consistency, like connectivity issues or blocked websockets. The user also mentions installing Edge DX agent on one PC, wondering if this may cause a delay in remote shell functionality. They are instructed to check the devices event log within Edge DX.
Read the entire ‘Troubleshooting Remote Shell Issues with ControlUp’ thread below:
Sometimes when I try to do a remote shell on a user’s PC, I get a window that opens and says, "Waiting for agent connection…" and then nothing else happens. Most of the time this works, but sometimes not. Any ideas on how to fix this?
Is there any consistency, like the same machines or maybe machines on a particular subnet? Although if you’re getting data, it should have no connectivity issues, but maybe somehow websockets get blocked on the device?
I’ve tested connecting to several PCs in the same subnet as the one that I can’t connect to, I’m able to start a remote shell on those PCs. The one PC I’m trying to connect to that I can’t, I just installed the Edge DX agent on this afternoon. Not sure if it take a bit for the remote shell to start working.
No, should pretty much be instantly. What’s showing in the devices event log inside Edge DX?
Continue reading and comment on the thread ‘Troubleshooting Remote Shell Issues with ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops