HKLM\System\CurrentControlSet\Control\Terminal Server. In the right hand pane fSingleSessionPerUser should be zero. If you just look in the batch command that you used to install the patch it is all right there. I believe you only had 2 choices when you install the patch and they were single session per User and Allow blank passwords. I don't recall what the defaults were but it's all in the batch file.

So we are talking about the Concurrent RDP Patcher then? I thought this one was the more reliable fix found at missingremote. I'll try again with the RDP patcher and the suggestions you made. I am SOL for now because I tried to boot the remote computer into safe mode and now I can't get into it with logmein either. I'll have to wait until I have access to it on monday. 

There were a number of versions. One for RTM, one for SP1 and a second version for SP1. I am sure there were some inbetweens also but if your version ran to completion without any error messages you should be golden. Are there any routers or firewalls between you and the target machine that could be blocking port 3389? This will only work on your local network unless you have the remote router port forwarding packets to your target machine.

I did port forward 3389. I'll try again on Monday and post here.

When I set thse things up the first thing I do is prove that I can access the target machine from the same network. Only then do I try to access it from a remote network. Make sure that you either have a hard coded address in the target machine nic, or have a reservation set in the router so that the target computer gets the same IP address every time.Make sure that the port forwarding settings match that IP. Make sure that the firewall on your local source computer allows Port 3389 out through Windows firewall. Make sure that port 3389 is not being blocked outbound by by your local router. You get the picture.

I was trying to re-download this utility tonight and the link on the 1st posting is not longer working.  

untermensch, Can you upload the latest version somewhere else and update your post with its location.

Thanks for this post, it works great!

Question, though, I can get any user who is an administrator to remote in but standard users don’t have access. How can I give the standard users access to remote logins as well? I’ve tried a Group Policy plugin for Win7 Home Premium and added the Users group to the ‘Allow log on through Remote Desktop Services’ under Computer Configuration/Security Settings/Local Policies/User Rights Assignment but that doesn’t work.

The error I get when trying to log in via a standard user: "The connection was denied because the user account is not authorized for remote login."

zebdor44

Thanks for this post, it works great!

Question, though, I can get any user who is an administrator to remote in but standard users don’t have access. How can I give the standard users access to remote logins as well? I’ve tried a Group Policy plugin for Win7 Home Premium and added the Users group to the ‘Allow log on through Remote Desktop Services’ under Computer Configuration/Security Settings/Local Policies/User Rights Assignment but that doesn’t work.

The error I get when trying to log in via a standard user: "The connection was denied because the user account is not authorized for remote login."

I've never tried this in a version of Windows that doesn't support it, but I would imagine that instead of adding the Users group to the Local Group Policy Security setting "Allow log on through RDS", you should add the User (not the group) to the Remote Desktop Users group.

I'm not sure if the Remote Desktop Users group exists in Home Premium, but if it does, it will have an SID of S-1-5-32-555.

Editing this directly in the registry would be difficult for all but very experienced users because it's all tied to SID's and GUID's.

Where did you get a gpedit.msc that works in Home Premium?

I suppose as a last resort, you could upgrade your copy of Windows to the Professional edition.

barnabas1969

zebdor44

Thanks for this post, it works great!

Question, though, I can get any user who is an administrator to remote in but standard users don’t have access. How can I give the standard users access to remote logins as well? I’ve tried a Group Policy plugin for Win7 Home Premium and added the Users group to the ‘Allow log on through Remote Desktop Services’ under Computer Configuration/Security Settings/Local Policies/User Rights Assignment but that doesn’t work.

The error I get when trying to log in via a standard user: "The connection was denied because the user account is not authorized for remote login."

I've never tried this in a version of Windows that doesn't support it, but I would imagine that instead of adding the Users group to the Local Group Policy Security setting "Allow log on through RDS", you should add the User (not the group) to the Remote Desktop Users group.

I'm not sure if the Remote Desktop Users group exists in Home Premium, but if it does, it will have an SID of S-1-5-32-555.

Editing this directly in the registry would be difficult for all but very experienced users because it's all tied to SID's and GUID's.

Where did you get a gpedit.msc that works in Home Premium?

I suppose as a last resort, you could upgrade your copy of Windows to the Professional edition.

I was able to copy over gpedit.msc from a different Win7 Ultimate system, but even with just adding the user to "Allow log on through RDS" it still doesn't work.  I've read elsewhere that it will work if you go to Control Panel -> System -> Remote Settings and click on Select Users under the Remote Desktop section, but Windows 7 Home Premium doesn't have that section.  Any other thoughts?  Remote Desktop Users doesn't exist in Windows 7 HP.  I've tried adding that group through 'net localgroup "Remote Desktop Users" /add' and then adding users to this group via the command line and then adding the group to allow logins via gpedit but that didn't work either.

I've thought about upgrading but all I need is to get standard users remote access, and since admins have remote access I'm hoping there's a way to do that for standard users as well even if it does require a registry change.

From what I've read, Remote Desktop Users is a built-in group.  If you create one yourself, it won't have the correct SID, and therefore will not work as expected.  I would imagine that the SID for Remote Desktop Users is embedded in the Windows code.

I'm sure there's a way to hack the registry to make it work... but it will probably involve quite a few tweaks to the registry.  Everything would need to be pointing to the correct SID's and GUID's.  I probably wouldn't want to attempt it.  This is one of the many reasons I've never owned any of the "Home" editions of Windows.  When I build a PC, I want total control over the security settings... so I have always chosen the Professional edition of every NT-based version of Windows since Windows XP.  

Can somebody upload this tool somwhere? It seems that it is not longer available at this hosters...

Have you looked on the missing remote?

www.missingremote.com/.../how-enable-concurrent-sessions-windows-7-service-pack-1-rtm

zebdor44

Thanks for this post, it works great!

Question, though, I can get any user who is an administrator to remote in but standard users don’t have access. How can I give the standard users access to remote logins as well? I’ve tried a Group Policy plugin for Win7 Home Premium and added the Users group to the ‘Allow log on through Remote Desktop Services’ under Computer Configuration/Security Settings/Local Policies/User Rights Assignment but that doesn’t work.

The error I get when trying to log in via a standard user: "The connection was denied because the user account is not authorized for remote login."

Did you try to create a new standard user from scratch with a password?  There is no way to add an existing user to the Remote Login list in HP as you have found out.  Also remote blank password login is disabled by default and for good security reasons.

OK, I have set this up successfully on several machines.  However I am having a problem on my Win7 Pro machine.  I cannot get it to work as a server using a port different than 3389.  I have modified the one registry entry, rebooted, and forwarded the port , however it accept RDP connections if I use any port other than 3389.  All my other machines use different ports (mostly because of security, but also because I have multiple machines on one network I need to access and the router needs to be able to handle all of them).

What am I missing?

Any help would be appreciated.

Thanks

Tim

I cannot answer your direct question, but have a workaround for you.  If you can live with this one machine being in accessible directly from the internet, then you have a couple of options:

1. Use a VPN to access your private network and then use the Private IP address on the local LAN over 3389.  

2. Connect remotely with Remote Desktop to any other machine on the network.  Then RD from that machine to the problem one.