Remote desktop Not working

Dear Sir,
yesterday connect the RDP Is worked .but today not connect the RDP .please help me
Thanks
Gourav GAngil
09827931158

Hi gourav,
Thank you for posting in Windows Server Forum.
Please provide little more information for further troubleshooting.
Are you trying to take RDP for server session?
What’s your server and OS client version?
Did user have the access of taking Remote Desktop Session? It means we need to add the user under Remote Desktop User” local group.
In meantime you can refer below article for information.
Why can’t I connect using Remote Desktop Connection?
http://windows.microsoft.com/en-in/windows7/why-can-t-i-connect-using-remote-desktop-connection
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

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

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

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

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

Maximum number of monitors used for remote desktop not working correctly

My goal is to connect from my home to my work machine but limit the number of monitors used to 2.
At work, I have a machine running Windows 7 Enterprise SP1 with dual monitors. My home machine is Windows 8.1 Pro and it has 3 monitors (on two video cards).
I followed the instructions of the MSDN blog post about using multiple monitors for remote desktop but cannot get it to work right.
Here's what I see when I modify the group policy setting "Limit maximum number of monitors" on the target (work) machine:
Setting - Result:
1 - 1
2 - 1 (???)
3 - 3
It looks like I can't limit the number of monitors used to 2, I get either one or all. Am I missing something or is this by design?
Max

Hi Max,
Support for multiple monitors is available when connecting from any Windows 7/8.1 computer, however, there are restrictions when connecting to a computer using multi-monitor mode. When connecting to Windows 7 computers, only computers that are running Windows
7 Enterprise or Ultimate can be connected to in multi-monitor mode. When connecting to Windows 8.1, only computers that are running Windows 8.1 Professional or Enterprise can be connected to in multi-monitor mode.
Karen Hu
TechNet Community Support

Why is Apple remote desktop not working?

I have 4 machines in a remote office that I need to connect to using ARD 3.6. I have a VPN connection working and am able to successfully control all but one of the machines. I have checked all of the settings and have confirmed that the Mac that ARD is not working has all of the same sharing preferences as the machines that are working. All of these machines are on the same network. All of the machines are running OS 10.8.x. All machines that I am able to connect to are running 10.8.3 but the one I can't is only at 10.8.2, but that is only because I haven't been able to remote into it yet to perform the OS update. The weird thing is that I can see the unresponsive Mac (can see the IP address, the version of ARD, OS version, etc.) but I simply can't connect to it to control or observe using ARD. I am however able to use TeamViewer from a remote Windows PC.
Can someone provide some ideas as to what to check and or how to fix this? TIA.

Do you have remote login enabled?
Have you tried using the kickstart command to restart the ARD Client?
http://support.apple.com/kb/HT2370?viewlocale=en_US&locale=en_US
If it's not enabled you will need to call a user or someone at the location and have them check the box to enable remote login.
In the past the ARD client has 'stalled' forcing me to restart the agent. Another option would be to have someone restart the machine for you.
I have actually had to use ssh to uninstall and re-install the client software due to corruption or ??.
Let me know what the outcome is. I see this was from May so let me know either way.
Thanks

Remote desktop not working with WAAS

I've got the WAAS setup and i'm see ok acceleration between sites but I have a complete failure of remote desktop. I've had to place a deny statement in my access list on the remote sites router for port 3389 to exclude traffic from the WAAS to even be able to get an RDP connection to work. I've tried to tell the WAAS to just set Remote-Desktop traffic to pass through but still no luck. Any help would be appreciated.

Because Internet access is allowed directly from the remote sites the ACL below will only redirect traffic destined for private addresses to the 474 located at the remote site.
ip access-list extended WCCP-REDIRECT
     permit tcp 10.0.0.0 0.255.255.255 172.17.0.0 0.0.255.25
     permit tcp 172.17.0.0 0.0.255.255 10.0.0.0 0.255.255.255
     permit tcp 172.16.0.0 0.15.255.255 172.17.0.0 0.0.255.25
     permit tcp 172.17.0.0 0.0.255.255 17.16.0.0 0.15.255.255
     permit tcp 192.168.0.0 0.0.255.255 172.17.0.0 0.0.255.25
     permit tcp 172.17.0.0 0.0.255.255 192.168.0.0 0.0.255.255
By adding this I can force RDP to sort of work
     deny tcp any any eq 3389
     deny tcp any eq 3389

Remote Desktop Not working with EoMPLS

I am hosting a HVPLS domain on my 7613 Core router where my spokes (6524ME) terminate the port based Pseudowires. All spokes have an MTU size of 1522. The clients are have intermitent problems with Windows Remote Desktop and mail synchronization. This clearly is an indication of an MTU issue. After doing a little bit of research I found, I need to decrease the MTU to make RDP work properly. Is it possible to reduce MTU of an L3 port to less than 1500?. Can i adjust my tcp-mss on the port where my xconnect is originated?
Thanks in advance guys..

I am back after a hectic week on this issue...I could find out something very interesting... At times of convergence, the new path takes sometime to calculate the MRU... Mean to say when you issue the command ping mpls pseudowire destn .. The new path has an MRU of 0 for some 5 seconds..After 5-6 seconds MRU comes back with 1700..This screws up the applications like mail synchronization etc.
Apart from this I found a lot of OSPF flapping due to aggresive BFD timers also, which creates issues with remote desktop. I am unable to convince myself on the MRU issue why it happens. IOS issues on 6524??

Remote desktop not working on mountain lion

My ARD does not work on Mountain Lion. The software opens but all I get is the menu at the top, and my only working option is to quit. I spoke to Apple support and they suggest (as they usually do) to reinstall the whole operating system, but I can't accept this as a valid answer as everything else works. There must be a way to fix this without having to reinstall a machine that came originally with Mountain Lion!

I was able to fix my issue by just uninstalling ARD (I used AppZapper) - and just reinstalling it - no "Archive & Install" required - best of luck with your situation!

Remote Desktop not working on client after crash

I was installing the ARD Client along with some other OS upgrades on two client computers. My main ARD console was busy copying some files so I set up ARD to install the pkgs via the task server on another Mac. During the install my main ARD console crashed. Now the clients show up with the status that Screen sharing is allowed but they show the old version of the ARD client is installed. I manually installed the new ARD client but it still shows up on my console as the old version. Sometimes I can connect to the clients and sometimes I cannot. I can't do anything other than screen sharing and that is not working well either. I went to the client computer and stopped and started ARD through system preferences. When that didn't work I used the terminal command to kickstart ARD on the client. No change on the admin side. I've also noticed when I am able to connect to the client that it is constantly reconnecting to it like it is dropping the connection. I ran Activity monitor on the client and ARDAgent shows up there but keeps disappearing like its starting and stopping on its own. Has anyone had anything similar happen to them?

When I looked in this folder, I saw the "Client" folder with the red "no access" icon on it. I did a GetInfo and changed the permissions for this folder to include Administrators with read/write (why it wasn't already like this as I was logged into the server through ARD as admin [server is headless], I'll never know).
I propagated this perm changes down through the folder's children and all seems well. Its likely that because of the access issue, ARD could not initiate any connections (vnc://serverIP did not work either initially).
YMMV.

Remote desktop not working with dot1x authenticated machines

Hi,
we are using machine and user authentication , when machine at logoff the machine is authenticated so users can RDP to it
but after logging in the remote desktop session goes down because after user authentication the machine gets a new ip address .
is there any way to avoid this issue ?

I am back after a hectic week on this issue...I could find out something very interesting... At times of convergence, the new path takes sometime to calculate the MRU... Mean to say when you issue the command ping mpls pseudowire destn .. The new path has an MRU of 0 for some 5 seconds..After 5-6 seconds MRU comes back with 1700..This screws up the applications like mail synchronization etc.
Apart from this I found a lot of OSPF flapping due to aggresive BFD timers also, which creates issues with remote desktop. I am unable to convince myself on the MRU issue why it happens. IOS issues on 6524??

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

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

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

Similar Messages

Maybe you are looking for