RDP - The Logon Attemp Failed

Hi guys

My setup is as this:
Ubuntu host machine running VMWare with Windows 7 Professional VM. I have a static IP address. VMWare is using BRIDGED connection to this VM.
My routers internal IP is 192.168.0.1- Port 3389 forwarded to 192.168.0.9
Ubuntu host (DHCP enabled) 192.168.0.16
Windows 7 Pro has (DHCP enabled) 192.168.0.9 - computer name is "VPS-2" and user name is "virtual"
I have enabled "Allow connection from computers running any version of Remote Desktop"
So, before installing SP1 on Win7 Pro I'm pretty sure my RDP was working, but now all I get from another machine connecting via the RDP to Win7 Pro is:
"The Logon Atempt Failed". It even gives me this error when I use incorrect usernames and passwords. I have tried connection using these credentials using external IP:
1) "vps-2\virtual" and password
2) "virtual" and password
3) incorrect machine name and password
Result is always the same error message - The Logon Attempt Failed
I have also tried connection using local IP address and same usernames/passwords stated above with the same result.
So what's wrong?
Thanks.
kirretAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Rob WilliamsConnect With a Mentor Commented:
I would try creating a new user account, add it to the remote desktop user group, and test it.
0
 
lucifer82Commented:
Have you checked the firewall setting on the Virtual PC? Make sure the RDP (3389) is allowed.

Also for testing purpose you might want to disable firewall all together and see if that is causing the issue.
0
 
kirretAuthor Commented:
If firewall was blocking it then I guess I wouldn't get as far as asking for a password?
Anyway, there is only firewall there is is the built-in Windows Firewall which I have disabled and still the same message keeps coming up.
Thanks
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
Rob WilliamsCommented:
See if the VM is accesible by telneting to the VM using
telnet  123.123.123.123  3389
If accesible you will get a blank screen and a flashing cursor.

If not accesible, see if the VM is "listening"
netstat -an |find "3389"
Should return:
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING

If not listening, make sure the RD services role is running on the VM in services.msc
0
 
kirretAuthor Commented:
@RobWill

Did telnet 192.168.0.9 3389 and got a blank black screen so I guess it is telnetting. Also check VM services on VM and they are all in STARTED state.
I think if it's gonna take too much effort to find out the problem then I;m just gonna reinstall that VM as there's no 3rd party software on it right now, just MS updates.
Let me know if you have any other thoughts...
0
 
Rob WilliamsCommented:
If telnet works it definately sounds like an account issue.  Is the user account "virtual" a mamber of the remote desktop users group?
0
 
kirretAuthor Commented:
It's a standalone installation, no domain. During the installation I named this account "IM" but after installing all the updates I started to get that problem so have changed the account name since then with no positive effect.
0
 
kirretAuthor Commented:
LOL, created a new account with a password and problem solved with that account. So I'm just going to delete the original account and use this new one for RDP. By the way, didn't have to add this new user to any groups, just made it an admin account.
Thanks!
0
 
Rob WilliamsCommented:
Good to hear.
Administrators are added to the remote desktop users group by default.
0
All Courses

From novice to tech pro — start learning today.