Logging into VM with different time that current time
Hi all,
I doubt this is a common problem (though who knows) but I often set our VMs back or forward in time to test various features of our financial software. However if the VM time (it's a Windows 7 VM usually) is out of sync with the current time RDM won't let me in.
I can NOT login with Windows RDP but I can login directly through Virtual Box.
Is there a setting I can disable somewhere e.g. Assert Current Time that will not check for this? Or allow me to still login? Or perhaps its a Windows related issue which is not easily solved.
Thanks
m
All Comments (5)
Hello,
RDM is not a protocol, in the case of RDP, we simply call mstsc.exe in our external mode, or wrap the Microsoft RDP ActiveX in our embedded mode.
That being said, we sometimes face challenges in finding the proper parameter combination to replicate what mstsc does.
Could you describe the "can not login" part? Is there an error or you are being prompted for credentials?
Best regards,
Maurice
Thanks for the reply Maurice.
Basically it says I can't login and my login credentials are invalid. THe date on the VM might be 3 days before the current date.
"Your credentials did not work
The credentials thtat were used to connect to 10.48.10.60 did not work. Please enter new credentials"
If I reboot the VM (which causes the time to resync) then all is well.
Maybe there is a log somewhere else that I could look at?
That sounds like a RDP error message.
Easiest test at this time would be to import the rdp session that works into RDM. If it works as is we could compare two sessions to see what setting is different.
Maurice
Apologies I am a bit of a newb at some of this:
"import the rdp session"
What do I import? Is this an .rdp file?
Soorry, just saw that RDP DIDNT work.
I see a lot of old posts on the Internet with an error like that, but the fix is to use the IP address instead of the computer name, but you are already doing that. No other ideas at this time.
Maurice