Windows 7 - I need help figuring out why Remote Desktop won't accept logins...

tallship · 02-01-2012

Hello

When I try to connect via remote desktop with http:/adminusername@x.x.x.x I receive the following:

I need help figuring out why Remote Desktop won't accept logins...-selection_129.png

This occurs when I invoke RDP in the form rdp://adminusername@x.x.x.x

Once i click on "OK", Then it shows my login avatar, with a password box, and upon providing my password credentials it returns to the screen above, so I know I'm getting through to the correct machine.

If I attempt to merely connect to the machine w/o providing a username, then I get no login prompt whatsoever.

If I try to connect from another windows box, I get the following:

I need help figuring out why Remote Desktop won't accept logins...-selection_131.png

I need help figuring out why Remote Desktop won't accept logins...-selection_131.png

I've set up RDP many times before, but it's been a while and I can't figure why I can't seem to login to my new Windows 7 Ultimate x64 box.

I've gone through the following pages at:

Why can’t I connect using Remote Desktop Connection?

Allow Remote Desktop connections from outside your home network

and in accordance with our very own tutorial here: Remote Desktop Connection (RDC) - Network

To be clear, I chose:

Quote:

Allow connections from computers running any version of Remote Desktop (less secure)

Seen here in this shot:

These are all things I know how to do already, but I've double and triple checked my configs to no avail.

The service is running as per "net start":

The port is open too, as nmap reports below:

Code:

$ nmap -p3389 -PN x.x.x.x # IP Address redacted

Starting Nmap 5.21 ( http://nmap.org ) at 2012-02-01 07:19 PST
Nmap scan report for x.x.x.x
Host is up.
PORT     STATE    SERVICE
3389/tcp filtered ms-term-serv

Nmap done: 1 IP address (1 host up) scanned in 13.29 seconds

Windows firewall wasn't running, so I started it and enabled RDP connections, as the screenie below indicates:

The machine has a public IP addy, is on a routed network, and other windows machines on that IP block have no problems accepting connections via RDP. I don't know why nmap is reporting that the port is 'filtered' either, since I'm getting a login prompt when I specify the username (I added the user, and created another user and added that user too, to the Administrators, Users, and Remote Desktop Users groups).

Here's the value for the key in my HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber:

I've installed Mikogo, and VNC server, and can connect to the box via either of those methods without any issues, but want to be able to connect via the native RDP too.

Any assistance would be most appreciated, I'm at a loss to understand why I can't connect.

You're thoughts, comments?

Thanks

.

Anak · 02-01-2012

Hi tallship, welcome to 7F!

I did not go through your external links to check if they mention whether or not you have the Services set properly for both machines.

I surmise you have double checked the reasons in this Alert box.

Name: Selection_131.png
Views: 218
Size: 43.0 KB

The suggested settings from Black Viper:

I need help figuring out why Remote Desktop won't accept logins...-rpcblkvip.jpg

By the way, excellent first post!

EDIT: I did see where you posted the services screenshot.

Anak · 02-01-2012

Quote:

I don't know why nmap is reporting that the port is 'filtered' either,

Found this:

Quote:

filtered

Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software. These ports frustrate attackers because they provide so little information. Sometimes they respond with ICMP error messages such as type 3 code 13 (destination unreachable: communication administratively prohibited), but filters that simply drop probes without responding are far more common. This forces Nmap to retry several times just in case the probe was dropped due to network congestion rather than filtering. This slows down the scan dramatically.

Source: Port Scanning Basics

That looks to be an good site.

tallship · 02-04-2012

I found the problem. Eset was installed, so I disabled windows firewall and added the port I had configured Remote Desktop to listen on.

Voila!

Thanks for all your help, and I'm marking this thread as solved.

tallship · 02-04-2012

Quote: Originally Posted by Anak

The suggested settings from Black Viper:
Attachment 196188

By the way, excellent first post!

Thank you @Anak

And thanks for the link to Black Viper too. It's a very good resource for choosing which services don't really need to be running.

Anak · 02-04-2012

Your welcome! Thank you for posting back with the solution. I am Happy you were able to get it sorted out.

Windows 7 - I need help figuring out why Remote Desktop won't accept logins...

I need help figuring out why Remote Desktop won't accept logins... problems?