This is a weird situation and I am trying to figure out how RoyalTS utilizes RDP inside of Windows.
I have a machine that runs Windows 7 thus RDP client 6.1
I have a certain server that when trying to connect, it sits there and eventually the RDP window goes away.
I can connect to other boxes, using RDP just fine.
Just for testing, I loaded RoyalTS on the Windows 7 machine and guess what I could connect to the server with no issues
If i run MSTSC by itself, I still get the same error.
What does RoyalTS do differently? If you are allowed to tell me! 8-)
Thanks!
Clay
Hi Clay,
can you post the error messages you get when you use mstsc.exe? Additionally, check the log in Royal TS (via the view menu), there's a chance that Royal TS logged some fall back routines to ensure you can connect where mstsc.exe will just fail (mostly security related stuff like NLA).
cheers, Stefan
Stefan,
There are no errors or event logs posted. The RDP connection diaglog box goes through its normal animation (the moving cyclon bar)
then just disappears.
It only happens on the one server.
All servers are 2008
Dont spend a bunch of time on this, i was just wondering how RoyalTS could connect but MSTSC could not.
When all your servers with this behavior are 2008 I guess it's the NLA setting. Try to change the NLA setting on the server or look at your mstsc.exe advanced setting for server authentication.
cheers
finally got back around to this and it seems that a faulty ISP was the issue. The connection was very poor! Is RoyalTS more forgiving on bad connections?
When Royal TS sets the parameters for reconnect, there's a good chance it's not the same setting MS is using in mstsc.exe. So, yes, there might be a slightly different behavior and in your case even a better one.
Our Forums are currently offline due to maintenance work.