Remote Desktop - not running/no listener on port 3389

Hello,
I have a problem with RDS (Remote Desktop) on a Windows 7 machine. It worked fine for the past 2 years.
Error: The computer can’t connect to the remote computer.
First I checked some settings:
RDP enabled (also tried to disable, reboot en then enable)
Registry: fEnableWinStation (1)
Firewall is disabled
RDP / RDS services are running
Problem:
RDP/RDS is not listening
“qwinsta” command: rdp-tcp is not listed
“netstat –an” command: no listener on port 3389
(rdp is configured to use the default port, 3389)
I also checked the “RDP Winstation driver” and the “Remote Desktop Services Security Filter Driver”.
Statup type: Demand
Problem: Both are NOT started.
When I start them manually, or set the startup type to “boot” and then reboot
the drivers will start, but it makes no difference. Still not listening on 3389.
Does someone know a solution besides reinstall the OS.
Thanks.

Hi,
Firstly, I would like to check when did this issue happen? Whether you have tried installed some software or updates?
Meanwhile, please try to perform a
system restore to check the result.
Also check the server settings, here is a similar thread:
Terminal Services/ Remote Desktop not working
Hope this helps.
Vincent Wang
TechNet Community Support
Have you tried this?
Regards
Vincent Wang
TechNet Community Support

Similar Messages

I was running remote desktop on my old mac pro running 10.4.11. Upgraded to new pro running 10.6.7 Can I get remote desktop to run on new computer?

I was running remote desktop on my old mac pro running 10.4.11 Just upgraded to new pro running 10.6.7 Can I get my previous remote desktop to
run on new computer?
Thanks

Are you talking Apple's Remote Desktop software, or Microsoft's?

Is it possible to get Remote Desktop Services running when in Sysprep Audit mode in 2012r2?

Hi,
I'm setting up some images for 2012r2 and personally like to be able to access the machines via RDP. I have broken out of the OOBE by pressing
CTRL+SHIFT+F3, however, even though RDP is enabled (System --> Remote Setting) and running (Services --> Remote Desktop Services),
when I run 'netstat -a', I cannot see any process bound to port 3389, as such I cannot connect. Have restarted the services just in case, but no dice.
I most the other OS setups (Windows 7, 208R2) this is fine (assuming you update either the password in audit mode or enable RDP login with a blank password), but the fact that nothing is listening
on 3389 means that no matter what I do, I will not be able to connect.
Is there any reason why this is the case?
Cheers
Chris
Chris

Hi Chris,
Thank you for posting in Windows Server Forum.
Can you ping successfully the respective server?
Initially check whether there is any firewall rule set which is blocking your connection. Please try to change the RDP port from following registry key and verify whether you can get access.
To change the port assigned to RDP:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the Remote Desktop server, open Registry Editor. To open Registry Editor, Start Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Remote Desktop server\WinStations
Note: RDP-TCP is the default connection name. To change the port for a specific connection on the Remote Desktop server, select the connection under the WinStations key.
1. In the right-pane, double-click the PortNumber registry entry.
2. Type the port number that you want to assign to RDP in the
Click OK to save the change, and then close Registry Editor.
For more information you can refer following article (Point 2: You may have a Port assignment conflict).
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote desktop not working "remotely"

I have a Windows 7 Ultimate computer I'm trying to access through Remote Desktop.
I'm able to access that computer from another computer when both are in the same LAN, but I fail to access it through the internet.
I already tried disabling windows firewall in the target computer to narrow it down, and it still fails. So the problem mustn't be in the firewall. Only I don't know where else to look.
Since I can access within the same LAN, I assume the Remote Desktop settings are fine.
This is what I did to attempt to access the pc over the internet:
- In my router's admin console, I set up port forwarding and port mapping to work with my target computer's local IP address and port 3389 (remote desktop's port):
- Then I used an IP lookup service to find my external IP address.
- I tried that IP:port combination on remote desktop, with the user name from the target pc I want to use (I also tried without entering the user name, but it also fails):
I always get an error message saying that remote desktop is not enabled, or the remote computer is turned off or not available on the network. The first two are false, since I can access the computer on a LAN and it is definitely not turned off.
The firewall on my router is disabled, so I really don't know where I'm going wrong.
Can anyone help, please?
Thanks!!

Hi Patr1c1a,
Did you check the radion button "Allow connections from computers running any version of Remote Desktop" on the recieving computer ?
System properties / Remote
Kind regards,
Gianni

Reporting & Analysis workspace9 server not running on server at port 6800

Hi all,
i installed hyperion 9 system them with reporting and essbase ..
after configured all .. configure shows sucess but after shared services configuration failed in BI
unable to open workspace
when i tried to open Workspace
"Could not find a Hyperion Reporting and Analysis in workspace9 server running on server at port 6800. Please verify your server connect string and confirm that the server is up."
Please help...

Restart order all serives in the below mentioned order:
Hyperion S9 Shared Services
Hyperion S9 OpenLDAP
Hyperion S9 BI+ Analytic Services 9.3.1 - hypservice
HyperionRMIRegistry
Hyperion S9 Planning
Hyperion S9 Administration Services ATS5
Hyperion S9 Apache 2.0
Hyperion S9 BI+ 9.3 Core Services 1
Hyperion S9 BI+ 9.3 Financial Reporting Print Server
Hyperion S9 BI+ 9.3 Financial Reporting Report Server
Hyperion S9 BI+ 9.3 Financial Reporting Scheduler Server
Hyperion S9 BI+ 9.3 Financial Reporting Java RMI Registry
"Hyperion S9 BI+ 9.3 Financial Reporting Web application
Hyperion S9 BI+ 9.3 Web Analysis
Hyperion S9 Financial Management DME Listener
Hyperion S9 BI+ 9.3 Workspace
-Sasi

Remote Desktop not showing the graphical interface of an Ubuntu14.04 allocated in Azure

Dear users, dear Ubuntu experts
I have allocate in Azure a Ubuntu 14.04 from the gallery and try to connect frooma Windows Machine using the Remote desktop connection.
I can connect trough putty to the machine, so it is up and running
I have follow this tutorial, to connect trought Remote Desktop :
https://community.hpcloud.com/article/using-windows-rdp-access-your-ubuntu-instance
and after complete it, I can connect to Ubuntu, the interface to logon apear, so I enter the credentials, but as soon as the Ubuntu desktop should be shown, all I get is a short-of-grey-old-out-of-signal-tv image
may I have miss some step ??

Hi,
from the original post I mention, I exectued :
sudo apt-get update
sudo apt-get install ubuntu-desktop
sudo apt-get install xrdp
in the article you mention, same steps are required, and yes, indeed i did them
as describe in the article, I got the " slightly unusual-looking login screen "
but not at all the next ubuntu desktop screen
NOTE: first time I runned //sudo apt-get update// I got a error like uncomplete package, then I do the update, and run again //sudo apt-get install ubuntu-desktop //, it last the installation for
about half hour and finish sucesfully
That was my "log"
sudo apt-get update
sudo apt-get install ubuntu-desktop
sudo apt-get install xrdp
Azure >> add Remote Desktop EndPoint
sudo /etc/init.d/xrdp start
sudo adduser MyUserName --force-badname

Remote desktop not connecting

So basically i have set up a server, created a domain, everything is fine, the server can access the internet, it can see other computers in the network, the computers can see the server. Problem is I want to administrate the server remotely. So i set up
the remote desktop to allow users to connect remotely. Problem is it only lets me connect from other pc in the same network , I cannot make a connection from an outside network. I am trying many different options but none seem to help.
I have placed users in the list which allows the remote desktop connection
I tried disabling the firewall, i added the ports ranging 3387-3390 tcp and udp. Enabled any inbound and outbound rule for remote desktop.
Tried port forwarding though there are 2 routers on the network so i had access to only one . I forwarded the same ports through the router. And called the internet provider to forward the ports for their router. (They havent dont that as i am writing this
so that may be the problem but i cant be sure).
I tried installing teamviewer as an alternative. Problem is when i installed it , it didnt work also. It said there is no internet connection and that i have to check it. Then it tries to connect to the StayAlive server but fails ant tells me that i may
have a proxy , and i should manually set up its settings , but there is no proxy. So from what i have gathered . I am really at a loss here is there some settings i messed up in the windows server or is this a problem with ports not being open.
I am having a hard time figuring out where the problem is , as i have tried doing every settings that comes to mind, but it has been a pain in the behind getting remote desktop to work from an outside network.
Also i do know the outside Ip of the network, i use that to connect to the server but have no luck with that. I am open to any suggestions anyone may have. I will try to provide as much info as possible to help me solve this problem.

I dont quite understand, problem is that it doesnt even connect to the server it basically times out while trying to connect, at first i thought maybe it was because there are no users with licenses added but the error would be different when connecting,
also as i have said , i installed teamviewer on the server and it says to check internet connection, though the server can reach the internet. I tried creating the gateway, the wizard just created it . It didnt ask me to add any users. Can the server be somehow
blocking connections, but not notifying? As there are no logs of connection attempts. It just seems that the server cant be reached from the outside only from inside the local network.
The computers in the same network can use teamviewer, but the server even though being on the same network cannot. Firewall is turned off, no antivirus firewalls are present, ports have been forwarded through both routers. I cannot seem to find the reason
to this problem.

Remote Desktop not working via ASA

Hi Everyone,
ASA has 2 interfaces inside and sales.
There is ACL on interface sales that allow RDP on tcp port 3389 from sales to inside subnet 10.0.0.15.
Interface sales is attached to switch.
I did test from switch
2950A#telnet 10.0.0.15 3389
Trying 10.0.0.15, 3389 ...
% Connection refused by remote host
2950A#ping 10.0.0.15
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.15, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 ms
2950A#
logs on firewall show
May 18 2014 18:50:34: %ASA-6-302013: Built inbound TCP connection 313812 for sales:10.12.12.2/24066 (10.12.12.2/24066) to inside:10.0.0.15/3389 (10.0.0.15/3389)
May 18 2014 18:50:34: %ASA-6-302014: Teardown TCP connection 313812 for sales:10.12.12.2/24066 to inside:10.0.0.15/3389 duration 0:00:00 bytes 0 TCP Reset-I
Where 10.0.0.15 is PC and this PC is configured to allow Remote desktop connection coming in.
Any ideas what can i check?
Regards
MAhesh

Hi Jennifer,
I tested the RDP in both directions no luck.
Sales has security level
interface Vlan3
nameif sales
security-level 50
ip address 10.12.12.1 255.255.255.0
interface Vlan1
nameif inside
security-level 100
ip address 10.0.0.1 255.255.255.0
Ping works fine in both directions means from switch to PC and PC to switch so this should rule out routing right?
Seems NAT is not configured between inside and sales.
Regards
MAhesh

Printing locally from remote desktop not working

i have a client who recently upgraded his computers from xp to win7. he has a multi store quickbooks pos setup where he has to log in to a remote desktop connection onto a server in another store. he used to just login and run his reports and
then print them locally. since the upgrade, he has not been able to do this. the work around i found was to keep the xp laptop just for printing reports. well, now he is separating from the other store and going out on his own. he needs
to run some reports and save them to the local machine in order to bring the databases to his store. first, i need to know how to make the win 7 computer print the reports locally, so that he can run them (the xp laptop crashed). second, i need
to know how to copy the files onto his local computer (in server 2008 i can drag and drop them, not in 2003).
the win 7 is 64 bit, the server 2003 is 32. i tried installing the print drivers locally onto the server, but it's the wrong architecture. i also tried installing the 32 bit drivers onto the win 7 machine, same thing. i found several things
to try, but really need to get this fixed asap. when i try to install the printer, it shows up, and adds just fine. i am really having a fit here.
the copying thing is an absolute must also. i may be able to get by without the print issue fixed, but would like to know what happened just for my own information. thanx in advance.

Hi,
Firstly you can check whether print spooler service is not stopped. Also ensure that printer driver is compatible\supported by Windows 7 and by server. If you are using printer redirection then might happen that it’s not configure properly. The client must
have enough permission and also check client requirement for printer redirection (RDP 6.1 or above, .Net 3.5or above).
More information:
Terminal Server and Printer Redirection
Five reasons printer redirection causes Windows printing problems in RDS
For this can you describe little more”second, i need to know how to copy the files onto his local computer (in server 2008 i can drag and drop them, not in 2003).” Do you want to copy from remote session to local computer?
Hope it helps!
Thanks,
Dharmesh

Thaw computers over remote desktop to run software updates

I've got a network of computers running 10.5.6 and have Faronics Deep Freeze installed. Disabling deep freeze on every machine to run software updates, and then re-enabling it is a colossal pain.
What I want to do is create a workflow that I can send to all computers simultaneously through Remote Desktop that will first thaw the computer, then run software updates, and finally re-freeze the computer. I've never used Automator before, and I'm not really sure where to start. Can anyone give me some ideas?

Thanks for your prompt reply.
OK, maybe I'm missing something basic but then why would I ever want to run Windows network in my office? The bugbear about Macs is that there is certain Windows software for which there is no good Mac equivalent. But you are telling me that as long as I have a couple of Windows boxes, I can run my Windows software on them through my Mac, even though the data files are stored on an separate box (an Xserve).
Now, for the $64 question -- is it possible to set up a network in such a way that I could use RDC on my PowerBook in, say, Chicago to run the software installed on the Windows box and in turn to open and manipulate the files stored on the Xserve in my office, halfway across the world in Abu Dhabi? Would this be a particularly difficult configuration?
Thanks,
DXB Law

Apple Remote Desktop not connecting to O2 Wireless Box

I've successfully got Apple Remote Desktop to connect to, view and control various Macs connected to numerous routers.
But the O2 Wireless Box doesn't want to play ball and I simply can't figure out why it won't allow me to connect.
Using http://portforward.com/english/routers/port_forwarding/O2/O2-TG585v7/Apple_Remot e_Desktop.htm as a guide (this was the only O2 router it referred to), I'm forwarding ports 3283, 5900 & 5988 but I simply can't connect using Apple Remote Desktop via the Internet. It just sticks on 'Connecting...' and then goes to a failed message. It suggested that, perhaps, Remote Desktop isn't enabled on the other machine ... but it is.
It seems to be something very odd about the router (it doesn't even allow remote management of the router as O2 removed that functionality fearing it was 'too dangerous' to allow the end user access to this) and I'm wondering whether there's something else I need to do to make the connection.
Can anyone give me as guidance on this please? It's driving me crazy!

Hi Jason,
It is often difficult to explain a problem, so don't worry. Let's break it down.
Firstly, does ARD work when you are at your place of work? - can you control a mac?
If so, this is good.
Ok, from work you need to access your router and find your public IP address, you only have one. You will often find this is the status page.
The IP is usually a class A address starting with 80 or 90, but this obviously isn't always so, depending on your ISP and region. make sure you are not using the router's local lan IP! You will also need to make sure your home router is allowing ARD ports through!
You now need to port forward the ARD ports to the mac you want to control, which I believe you have done. For example, port 3283 > IP address of remote mac.
I know when I did this, I just opened up all ports for a couple of minutes just to get it working, then I locked access down. If you havn't done so then you need to enable remote management on your work router so you can configure it at home.
On your mac at 'home' open ARD, and go to file> add by address and enter the PUBLIC IP address. You will also need to enter the admin user name and password for the said mac.
That's it, you should have control.
If your macs at work and home have a firewall enabled then you will need to update your rules.
Good luck!

Can I use Remote Desktop to run Windows software from my Mac

Here's what I want to do:
1) Set up a small office LAN with an Apple Xserve as the file server; clients are mostly iMacs but a few PCs.
2) There are one or two software apps I need that exist only in the Windows world (such as a good document comparison software like DeltaView).
3) I want to have one dedicated PC for my one or two essential Windows apps and then run Remote Desktop Connection on my Mac client to launch the Windows app on the PC client and use it to edit or otherwise manipulate a data file stored on the server.
Is this possible?

Thanks for your prompt reply.
OK, maybe I'm missing something basic but then why would I ever want to run Windows network in my office? The bugbear about Macs is that there is certain Windows software for which there is no good Mac equivalent. But you are telling me that as long as I have a couple of Windows boxes, I can run my Windows software on them through my Mac, even though the data files are stored on an separate box (an Xserve).
Now, for the $64 question -- is it possible to set up a network in such a way that I could use RDC on my PowerBook in, say, Chicago to run the software installed on the Windows box and in turn to open and manipulate the files stored on the Xserve in my office, halfway across the world in Abu Dhabi? Would this be a particularly difficult configuration?
Thanks,
DXB Law

Windows RDP Remote Desktop not working with WRVS4400N

I use RDP extensively on my LAN to use and manage 4 PCs running Win XP or Win7. My consumer-grade Cisco Linksys WRT610n crapped out after less than 2 years, so I thought I'd try the Cisco WRVS4400N to gain extra features like VPN. I have not enabled anything new on the router except for adding a second wireless SSID for guest use, although no bandwidth management or VLANs have been set up yet. Firmware version is 2.0.0.8.
Since installing this router I have been unable to use Windows RDP on ANY of my computers on the LAN, whether I use the machine name or the IP address. I can ping every device on my network - print servers, NAS boxes, PCs, but no RDP. WHAT'S GOING ON?

I have the EXACTLY same problem!......
It´s driving me crazy that I have spend 150 $ for some shit of a device (Sorry but i´m frustrated)
I have almost tried everything to make RDP work without any succes.
I have opened port 3389 to the spefic computer with RDP enabled. It worked prefectly with a low-budget router
undtil a changed it out a (high quality router - WRVS4400N-EU Version 2)
Could some please tell me what i´m doing wrong or what Cisco is doing wrong.
I have always belived that Cisco produckts was equal quality

Apple remote desktop not working

Just upgraded to Mavericks and can not use apple remote desktop. I bought my copy of ARD from the store. Anyway of getting this fixed?

Hi ikarous79,
If you are having issues with Apple Remote Desktop under Mavericks, you may want to make sure you have updated to ARD 3.7, which was just released recently. You may find the following article helpful:
Apple Support: About Apple Remote Desktop 3.7
http://support.apple.com/kb/HT5896
Regards,
- Brenden

Remote desktop not allowed between two Windows 8.1 pro pcs

PC1 client of a domain
PC2 notebook (no domain)
User (in remote access) is a domain administrator and also pc1 admin.Logon is not allowed from pc2 to pc1 with the following message:
"The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support."
no problem if I use a PC with Windows 7 or XP
The standard configurations for remote access are equal for the two pc: no network authentication is required"
Thanks

Hi,
Enable the two policies below on PC1 to check how it works:
Computer Settings\Policies\Administrative Templates\Windows Components\Remote Desktop Session Host\Security\Require use of specific security layer for remote (RDP) connections
Set Security Layer to RDP
2. Computer Settings\Policies\Administrative Templates\Windows Components\Remote Desktop Session Host\Security\ Require user authentication for remote connections by using Network Level Authentication
Set to Disabled
Alex Zhao
TechNet Community Support

Remote Desktop - not running/no listener on port 3389

Similar Messages

Maybe you are looking for