Peter Mikula
asked on
Unable to login to RD Gateway published apps from one particular network location
we have a Windows Server 2012 R2 with functioning RD Gateway with published apps. It works from everywhere expect one office network location. We have there a SOHO Asus RT-ACRH13 firewall. Computers that can log in from other network locations are unable to login from that location (snapshot attached). We have disabled the firewall feature on it but no luck. Any other ideas what to do?
I also get an error 20499 on the server
Remote Desktop Services has taken too long to load the user configuration from server
BUt I'm able to login from another network with a different firewall just fine
snap1.png
I also get an error 20499 on the server
Remote Desktop Services has taken too long to load the user configuration from server
BUt I'm able to login from another network with a different firewall just fine
snap1.png
ASKER
I will have it as soon as possible as I don't have access to the server direclty.
but we did made the registry change for the TCP offload did not seem to help
but we did made the registry change for the TCP offload did not seem to help
ASKER
output attached
GetOffloadingGlobalSetting.png
GetOffloadingGlobalSetting.png
Can you log in to regular RDP session from problematic location?
ASKER
I have not tried, will try soon
new updates though. We have brought another laptop (Win 7) on site and connected behind the firewall and was able to connect, but none of the regular computers in that office which all run Win 7 Pro are not able to connect.
Those computers don't get the cert prompt warning so you can move on
the new computer we brought in though gets the attach cert mismatch error (attached) before it can connect
cert-mismatch.png
new updates though. We have brought another laptop (Win 7) on site and connected behind the firewall and was able to connect, but none of the regular computers in that office which all run Win 7 Pro are not able to connect.
Those computers don't get the cert prompt warning so you can move on
the new computer we brought in though gets the attach cert mismatch error (attached) before it can connect
cert-mismatch.png
Can you post build numbers of all computers involved.
cmd, neter VER command.
We will examine updates after that.
cmd, neter VER command.
We will examine updates after that.
ASKER
6.1.7601
ASKER
the thing with those computer is that they never get that cert mismatch prompt window where you can click OK to ignore and move on
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thnaks!
Open in new window