Trying to install a standard gateway on a Remote Desktop. The gateway works for about 24 hours and then fails. Once I login to the "On Premise Gateway" app, and restart the gateway it works again for another 24 hours.
The error message the incremental refresh shows is either "DM_GWPipeline_Gateway_SpooledOperationMissing" or "DM_GWPipeline_Gateway_TimeoutError"
Any help would be greatly appreciated!!
Thank you!
I have tried restarting the gateway and running the check network check to make sure reaching the ports is successful.
After a failure log onto the Remote Desktop machine and open Task Manager from the start menu. Go to the Performance tab and then the CPU tab. Note the Uptime metric. If that uptime is just a few minutes then this machine is not “always on”. This is typical for many virtual desktop machines which pause after a period of not being logged into.
As stated in the documentation:
Don't install a gateway on a computer, like a laptop, that might be turned off, asleep, or disconnected from the internet. The gateway can't run under any of those circumstances.
Related
Noob here with AWS workspaces. Brand new AWS account, went through full tutorial to set up a Windows workspace as per this video (twice). Both times, I can sign in but trying to connect to the Workspace is unsuccessful via the AWS client or their web client. When trying to use their web client I get "Connecting..." for about 10 minutes, and then an error (see image below). Note that I can connect just fine using RDP to the Workspace windows desktop, using Remmina (I'm on ubuntu) so I know these hosts are spun up and working just fine. But the AWS clients aren't working. I've tried all troubleshooting steps provided by AWS including verifying that the right processes are running on the host with Powershell as Administrator.
Anybody else running into this? It seems pretty weak of Amazon to release this offering that doesn't work "out of the box" with pretty much default choices for everything including their own Windows image.
I am running a Windows Server VM on GCP.
When logging in via Remote Desktop, I am starting certain applications which should actively run for a couple of hours.
But when closing my Remote Desktop Connection, all applications stop working.
How can I prevent this from happening?
In order to keep the session ongoing, you'll have to configure the RD Session Host time limits.
Open the group policy editor with: Windows+R, then type gpedit.msc, confirm with Enter.
Then in the management console, navigate to:
Computer Configuration
Administrative Templates
Windows Components
Remote Desktop Services
Remote Desktop Session Host
Session Time Limits
There one can adjust the settings:
Set time limit for disconnected sessions
Terminate session when time limits are reached
Everyday I log into my SSH session of a Google Cloud VM I maintain (Debian).
Since a week ago, I noticed my performance was lagging as I typed into the VM or when doing something else. I mostly login into this VM to check log files of scheduled scripts I have, and even when I use "cat script.log", what used to take less than 2 seconds now takes at least 5 or 7 seconds, loading the log text.
Pinging different websites bring me an reasonable 10 - 15 ms. I'm pretty sure it's not about my local connection either, everything else I do works fine in my local computer.
A warning started to appear now into my session, saying
"Please consider adding the IAP-secured Tunnel User IAM role to start using Cloud IAP for TCP forwarding for better performance. Learn more Dismiss"
I've already configured the IAP secured tunnel to my account, which is the owner account of GCP project.
Another coworker of mine is being able to access the VM without any performance issues whatsoever.
Your issue is in my opinion with the ISP. For some reason the SSH sessions are lagging.
That's why even other computers using your home ISP lag SSH sessions too. If that was firewall rule interfering you wouldn't be able to connect at all.
You may try to reset all the network hardware in your home and if that doesn't help
run tracert command in windows shell and then contact your ISP and pass your findings. It's possible it's something on their end (and if not maybe their's ISP etc).
To solve the problem you need to add "IAP-secured Tunnel User" at the project level in IAM for that user.IAP-secured Tunnel User + See instructions here in a blog I wrote about this. That should solve your problem.
When using RDP to connect to my Azure Windows Server 2016 VM, I am able to connect and the blue loading screen appears briefly then turn black and the connection is broken. I have worked through all the troubleshoot suggestions of:
After each troubleshooting step, try reconnecting to the VM:
1) Reset Remote Desktop configuration.
2) Check Network Security Group rules / Cloud Services endpoints.
3) Review VM console logs.
4) Reset the NIC for the VM.
5) Check the VM Resource Health.
6) Reset your VM password.
7) Restart your VM.
8) Redeploy your VM.
But nothing has worked.
Any suggestions greatly appreciated.
According to your description. Many possible reasons may cause this black screen. Firstly You can try to upsize the VM via the Azure portal.
Also, I suggest checking the RDP client side.
Use control+alt+end, then sign out to close the RDP session and launch another one.
try to connect through Remote Desktop Manager which can resolve the same issue for someone.
Known issue: A black screen may appear while logon by using remote desktop
From Virtual Machine settings on the portal, find Diagnose and solve problems, follow the steps of SOLUTIONS TO COMMON PROBLEMS.
More references about Black Screen after RDP
I use the Windows EvtSubscribe API in my program that runs as a service, generally on Windows Server 2008 R2 Domain Controllers. It is registered for kerberos logon events and it's purpose is to provide single sign on for my application on the network.
I grab the username/IP from the logon event and use them to pre-authenticate an IP address. This has worked well in a large number of sites until it was used recently on an extremely large site (60,000 users logging on and off throughout the day). The Domain Controller isn't under extremely high load as far as I can tell from Process Monitor but the events are not being passed on to my application right away, they delay by what can be 20 minutes to an hour.
I use the PUSH method as described in the API. The code is identical.
In Event Viewer, looking at the security logs the logon events come in immediately when a user logs on to the domain. However the event is not pushed to my application till much, much later.
I have never seen this occur at any of the other sites my application has been installed on and I'm wondering if its a configuration issue on the servers themselves. The site with the delays has 4 clustered domain controllers in total with my application running and reporting on each. All 4 periodically experience extended delays in receiving the events.
Has anyone else come across something similar or have any ideas what could be at play?
I have tried replicating it using VMs and ADTest to generate load without much luck.