Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1028
  • Last Modified:

enabling remote desktop in Home Premium

I am trying to enable Remote Desktop in Vista Home Premium 32 bit. I think that i have made the necessary registry hacks and firewall changes but I can't get the computer to listen on the RDP port of 3389. The command netstat -a | find /i "3389" doesn't show any listening. I have double checked the Windows firewall as well as the services. I figure that I am missing something pretty minor, however, i can't figure out what that may be.

Any suggestions on a fix would be greatly appreciated.
0
LostInWindows
Asked:
LostInWindows
  • 13
  • 10
  • 3
1 Solution
 
dhoffman_98Commented:
Perhaps what you are missing is that Vista Home Premium does not support Remote Desktop... officially.

There are many hacks out there on the net that talk about how to implement it in Vista Home Premium, but as it is not officially supported, this site is probably not the best place to ask questions about how to hack the OS to provide something it is not supposed to support. Try google.
0
 
LostInWindowsAuthor Commented:
Isn't there be a way to enable a specific port number?
0
 
dhoffman_98Commented:
Services enable port numbers by becoming active. If the firewall is blocking that port, you have to add an exception to the firewall.
0
Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

 
LostInWindowsAuthor Commented:
That is what has me puzzled. I manually added a firewall exception for port 3398 and enabled it. Yet, still when I enter     netstat -a | find /i "3389"    I don't show any result
0
 
dhoffman_98Commented:
Netstat won't show a result unless you have an active listener that has opened the port connection. If you are not seeing it, then it means the process is not connecting to the TCP/IP stack to open a connection.

Make sure the MSTSC process is actually running.
0
 
JoWickermanCommented:
Hi LostInWindows,

Try:

1. Download termsrv.zip here: http://www.unet.fi/sub/termsrv.zip
2. Extract Termsrv.zip to a temp directory
3. Start Command Prompt in Administrator mode (Run As Administrator)
4. Run the corresponding batch file for your Vista edition
5. Allow TCP Port 3389 on Windows Firewall or any other firewall product.
6. Done

Let me know if this helps.

Cheers
0
 
LostInWindowsAuthor Commented:
JoWickerman, I did all of your suggestion. My problem is I can't get the PC to listen on port 3389
0
 
JoWickermanCommented:
Oh ok. Did you check that "Allow connections from computers running any version of Remote Desktop (less secure)" is clicked?
0
 
LostInWindowsAuthor Commented:
I don't think that shows in Home Premium. I will be at the site later this morning, i will double check.
0
 
JoWickermanCommented:
Cool. Let me know!
0
 
LostInWindowsAuthor Commented:
The remote assistance advanced icon shows to allow all requests. However, because it is a "home" product, the RDP portion of the window is hidden. I thought it might be worthwhile to do a netstat -an and see what is listening.
0
 
JoWickermanCommented:
Any luck?
0
 
LostInWindowsAuthor Commented:
The PC is in an office and the user was sick on Monday and Tuesday. I hope to find out today. If she isn't in I will drop by.
0
 
LostInWindowsAuthor Commented:
The problem that I have is that I have customized the firewall to open port 3389. However, when I do a netstat -an then I find that Port 3389 is not listening. How do I turn on the port to listen. The netstat -an output follows:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:6646           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:10172          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:10172        127.0.0.1:49202        ESTABLISHED
  TCP    127.0.0.1:10172        127.0.0.1:49203        ESTABLISHED
  TCP    127.0.0.1:10172        127.0.0.1:49395        ESTABLISHED
  TCP    127.0.0.1:49202        127.0.0.1:10172        ESTABLISHED
  TCP    127.0.0.1:49203        127.0.0.1:10172        ESTABLISHED
  TCP    127.0.0.1:49395        127.0.0.1:10172        ESTABLISHED
  TCP    192.168.2.25:139       0.0.0.0:0              LISTENING
  TCP    192.168.2.25:10172     192.168.2.33:55299     ESTABLISHED
  TCP    192.168.2.25:10172     192.168.2.33:55300     ESTABLISHED
  TCP    192.168.2.25:10172     192.168.2.33:55301     ESTABLISHED
  TCP    192.168.2.25:49162     192.168.2.2:445        ESTABLISHED
  TCP    192.168.2.25:49679     216.49.94.13:80        TIME_WAIT
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:49155             [::]:0                 LISTENING
  TCP    [::]:49156             [::]:0                 LISTENING
  TCP    [::]:49157             [::]:0                 LISTENING
  UDP    0.0.0.0:123            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:56640          *:*
  UDP    0.0.0.0:59297          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:54889        *:*
  UDP    127.0.0.1:57453        *:*
  UDP    127.0.0.1:57459        *:*
  UDP    192.168.2.25:137       *:*
  UDP    192.168.2.25:138       *:*
  UDP    192.168.2.25:1900      *:*
  UDP    192.168.2.25:6646      *:*
  UDP    192.168.2.25:54888     *:*
  UDP    [::]:123               *:*
  UDP    [::]:500               *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:59298             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:54886            *:*
  UDP    [fe80::34d4:13cb:3f57:fde6%9]:1900  *:*
  UDP    [fe80::34d4:13cb:3f57:fde6%9]:54887  *:*
0
 
JoWickermanCommented:
Try:

Run command prompt -> net localgroup "Administrators" "NT Authority\Network Service" /add
Go to the c:\windows\registration -> Rightclick and add full control to the administrator and everyone account on that folder.
0
 
LostInWindowsAuthor Commented:
I have done the changes. Now I get a Username and passowrd screen. However, my login attempt is refused. I even tried from withing the office on the same workgroup and I get a message: "This computer can't connect to the remote computer. Try connecting again or contact the owner of the remote computer"
0
 
LostInWindowsAuthor Commented:
Attempt to increase points
0
 
JoWickermanCommented:
You'll have to connect as Administrator on the local PC...

Did you change the remote desktop users settings?
0
 
LostInWindowsAuthor Commented:
This is Vista. The account I want to connect to has Admin privileges, however, the administrator account is disabled by default.
0
 
JoWickermanCommented:
Can you enable the admin account? Or create an account with admin rights?
0
 
LostInWindowsAuthor Commented:
The workstation has 1 account on it. It has Admin rights enabled.
Like I mentioned earlier now when I attempt to log in I get a log on screen for username and password, however, I see the following message:
"This computer can't connect to the remote computer. Try connecting again or contact the owner of the remote computer"
0
 
JoWickermanCommented:
What happens if you use the credentials of the user whose account is on the PC. The one with the admin rights? For testing purposes, ask the user for her password, she can change it later again...
0
 
LostInWindowsAuthor Commented:
When I try that account from inside the company workgroup I get the Remote Desktop Logon Screen then the message "This computer can't connect to the remote computer. Try connecting again or contact the owner of the remote computer"
From Outside of the workgroup  I get the message  "This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
0
 
JoWickermanCommented:
Hhhmmm... Spoke to a Microsoft representative. You'll have to upgrade to Vista business or Ultimate for this to work properly.
0
 
LostInWindowsAuthor Commented:
OK. It seems unreasonable of MS to charge over $200 to upgrade from Premium to Business. You would think that they would have a Vista to Vista upgrade that would be more reasonably priced.
0
 
JoWickermanCommented:
Yeah... I agree with you there...
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 13
  • 10
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now