New
#11
one more question if I may,
the SSL VPN connection, I presume you just type an URL and logon.. are you using a citrix type configuration to present you with a landing page when you connect where you can select services/programmes?
one more question if I may,
the SSL VPN connection, I presume you just type an URL and logon.. are you using a citrix type configuration to present you with a landing page when you connect where you can select services/programmes?
All I supply is username and password to connect to SSL. Then I select a couputer which routes to a machine name.
Then it is just a remote session on the computer I believe.
Windows firewall is disabled in GP.
Remote connections were enabled as your pictures shows. THis was about the only thing I had done to the windows 7 machine. I did not do anything in windows firewall to allow an exception as it is supposed to be disabled through group policy.
I did not add anything with the /domain users.
Maybe that is the issue. I can't check until late tomorrow though.
I added things like
domain/domain users
domain/administrators
and I now see where I am at a login screen for that machine - but it doesn't pass through the password. You get a wrong password message. When I type in the password it doesn't accept it either.
I think it is a local windows 7 machine issue and not an SSL issues?
When I use my old password .... it gives me the original error message. So it appears it like my old password that is saved as a local password for a local user on the machine.
It doesn't appear to accept the domain credentials or login from the remote session.
Are you able to logon the machine directly on the network. Try using a Windows XP machine to a Windows 7 machine without using the VPN. This way you can eliminate the VPN and the Windows Server 2003.
from work here I can remote nto the server.
I remote desktop connection to the windows 7 machine
I was able to login.
Any ideas on what to check with ssl?
I know that in some cases when I VPN into a network that I have to REMOVE the domain information in the VPN Connection. If I don't then I would connect as say bsamson@mydomain.local.mydomain.local. The double domain information would make it impossible for me to navigate the network, because I was really bsamson@mydomain.local. This could be causing the issue with RDP. Or it could be just the opposite. Where you are not getting any domain information so you are trying to log into the machine as just bsamson. You may need to use bsamson@mydomain.local and then the password to log in when using the RDP Client.