I am unable to remote desktop to connect to my laptop

Similar Questions

• Windows Server 2003 r2 64-bit Remote Desktop RDP connection does not

  Hello

  I went through most of the support guides I can find on the internet and nothing seems to work.

  I enabled and disabled the service. Enabled and disabled Internet connection sharing. I totally disabled the firewall on the server and I can not always connect to the server via RDP

  I only get an error message.

  Remote Desktop cannot connect to the remote computer to one of the following reasons:

  (1) remote access to the server is not enabled

  (2) the remote computer is disabled

  (3) the remote computer is not available on the network

  Make sure that the remote computer is on and connected to the network, and remote access is enabled.

  When should I wear analysis server there is no enabled 3389 port. I am using RDP just for administrative purposes. I used to connect to the machine via RDP but one day it just stopped working.

  I also checked a few updates selection to determine if they are installed. All updates that might have compatibility problems are not installed on the server.

  Any request for information will be answered promptly.

  Thanks in advance.

  Hello

  Please post your apparent in the following link for assistance with problems of desktop connection remotely:

  https://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?Forum=winserverTS

  I hope this helps.

• Remote Desktop cannot connect to the remote computer

  Hi all

  I'm having a problem on my server running Windows Server 2008 R2.

  I can not can not on the remote server by using remote desktop (mstsc).

  Here is the error I get when connecting:

  Remote Desktop cannot connect to the remote computer to one of the following reasons:
  (1) remote access to the server is not enabled
  (2) the remote computer is disabled
  (3) the remote computer is not available on the network

  Make sure that the remote computer is on and connected to the network, and remote access is enabled.

  I tried to restart the services, but nothing helped.

  I even restarted the server, which did not help.

  Also, I can ping the server without any problem.

  Kindly help. !

  Hello

  Search logs events on the Terminal Server and the Local user's PC

  Try disabling the firewall - may have to be reconfigured.

  I suggest that repost you the question in the TechNet Windows Server forum for assistance.

  TechNet

• Remote Desktop cannot connect to the remote computer to one of the following reasons:

  We are using Windows server 2003 sp2 & windows xp professional sp3. We want to connect to the server using Remote Desktop, but we get the following error:
  --------------------------------------------------------------------------------------------------------------------------------
  Remote Desktop cannot connect to the remote computer to one of the following reasons:
  (1) remote access to the server is not enabled
  (2) the remote computer is disabled
  (3) the remote computer is not available on the network

  Make sure that the remote computer is on and connected to the network, and remote access is enabled.
  --------------------------------------------------------------------------------------------------------------------------------
  We have enabled remote access on the server & the user is member of admin & users group to the remote desktop on the server. The firewall is turned on & exceptions for port 3389 remote desktop.

  Could you please help us on this.

  Hello

  Search logs events on the Terminal Server and the Local user's PC

  What is happening to all users?

  -If you get an error in the TS, then this is a client-side problem.

  -Take TCP Dump using wire shark and see who is the RST sendign package.

  Look for this error message in google that could give you light...!

  Kind regards

  Dhruv

• Try to use remote desktop to connect to a computer in safe mode with networking

  I'm trying to troubleshoot a remotley pc on the network using remote desktop. I can connect properly, however, I want to continue to solve the problems with the pc remote in safe mode. When I choose to restart the pc in safe mode with network remote I am unable to connect to this computer by using remote desktop. Is there a certain config that I need to put in place inside msconfig which will restart in safe mode and I would still like access to connect to this computer by using remote desktop. Thank you.

  Hello

  @hoosier1077

  Assuming this isn't a general network problem (such as restarting changes to the local IP address on the remote computer).

  Maybe this can help.

  http://support.Microsoft.com/kb/315222

  http://support.Microsoft.com/kb/316434

• Remote Desktop issues connecting from home to work the computer in Windows XP. Remote Desktop stops responding and eventually disconnects.

  Just around the beginning of July (2011) I started to have remote Office questions when connecting from home to work. If I minimize the connection for a while and come back later, it will be often does not. I'll have to hit the close X button several times before, he ends by abruptly disconnects. By the sudden I want to say that I don't get no dialogue usual warning that the session will be disconnected.

  Also, sometimes when I connect I get a white screen instead of a connection window.

  Anyone know if there was a Windows Update, or anything that can cause problems with RDP.

  I used to be able to connect perfectly without any problems.

  Thank you

  original title: Remote Desktop problems for the months spent on XP

  Hello

  Your question of Windows is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the public on the TechNet site. Please post your question in the below link: http://social.technet.microsoft.com/Forums/en-US/itproxpsp/threads

• REMOTE DESKTOP cannot connect home via VPN to WORK computer

  Hi all

  Having problems connecting to the PC of Office WORK PC using remote desktop.  Currently, I connect to the WORK PC to WORK laptop with no problems.

  Page HOME of PC is a Dell Dimension 4600 Windows XP, version of Microsoft Office Home, ATT, anti-virus Norton 360 Wireless internet service.  Work VPN up and running.  Set up my computer remote tab in order to allow the communication and remote AUTHORIZED Norton 360 desktop, I can PING my computer work fine.

  I run my VPN and connect to function properly the network but when I run the Remote Desktop application, I get "this computer cannot connect to the remote computer."

  I know that my work IP address and logon information is exact and know that my work computer is configured to allow remote access because I do this work laptop.  I do not understand why my home PC has a problem if the VPN works and I can PING my computer work fine.

  Any advice would be appreciated. I looked all over the internet and cannot find additional ideas.

  Use teamviewer, it is much easier to understand. And you can give the PC connecting to a fixed password youre. If you do not have to change.  Just install on both, give the youre one connecting a password fixed, then log in with the other

  Is XP Home or Pro? If it does not support his home desk remotely

• XP Remote Desktop cannot connect to Windows 7: error 0xc00002fd

  I use Remote Desktop 6.1.7600 on Windows XP sp3 on two different computers and I am trying to connect to a Windows 7 machine on the same domain of one of them.  On the first machine to XP, I have several times a 0xC00002fd error "an authentication error has occurred" when you try to connect to the Windows 7 computer.  On the second XP machine I'm simply asked to password and user id several times.  On both XP machines I have activated CredSSP according to MS kb article 951608.  I'm an admin on the Windows 7 machine and uses my own credentials to connect.  This connection has worked in the past at least one of these XP machines and now all of a sudden it does not, or only intermittently.  Dr Mac OSX version seems to work perfectly.  This makes me wonder if there was an update on the XP side that makes CredSSP work correctly?

  Hi Bruce,.

  The question you have posted is related to the connection via the remote desktop of XP to Windows 7 computer on a domain network and would be better suited to the TechNet community. Please see the link below to find a community that will provide the support you want.

  http://social.technet.Microsoft.com/forums/en-us/category/w7itpro

  I hope this helps.

  Thank you and best regards,

  Srinivas R

  Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Can I use remote desktop to connect to a desktop PC to perform tasks of high performance?

  I have a spec PC up in one room of the House, used for high-intensity like photo editing functions and games.  I am looking to buy a laptop or a tablet to allow me to do this from other parts, but I am aware that the laptop will have to be high technique to do so at the same level.

  I wanted to ask what will happen if I logged on the desktop via the desktop PC Windows remote.  That would allow me to edit photos or play games using the spec of the PC or it automatically pick up the specifications of the laptop and run programs using this information?

  If it's this one, can anyone recommend an alternative?  I was wondering if a touch screen wireless or wireless monitor and a mouse that could pick up connection around the House might work?

  Hope it makes sense.

  Tony

  Original title: Windows Remote Desktop

  Yes I see.  Well in this case, it must do well.  Remote Desktop is pretty good, as long as there is not a lot of graphics fast.

• Unable to remote desktop to VM Machine

  Hello

  I'm new to VM environment so please forgive the newbie questions.

  I created a virtual computer on your laptop machine (A) and I am trying to remote desktop from another laptop (B) of the virtual machine and I can't do it. Check the settings of the remote desktop, and I authorize the audited machine remotely.

  I followed the instructions from http://geekswithblogs.net/NewThingsILearned/archive/2009/11/13/connect-to-vmware-virtual-machines-using-remote-desktop.aspx

  I can't do a ping computer laptop (B) virtual machine, however, when the ping of the laptop, (B), of the virtual machine, works. Also, I cannot remote into the laptop (B) of the machine of the virtual computer.

  Another problem is that I can't seem to connect the machine to the computer virtual from Windows Explorer Mobile (A) using \\Machine Name\C$.

  I enjoyed looking for this!

  Thank you!

  Your NAT configuration doesn't seem right! You transfer your host port 9997 to 192.168.123.16:443. However the NAT network is 192.168.142.0 and your VM has the IP 192.168.142.128, so that the transmission must go to 192.168.142.128 Port 3389.

  For C$ access try to use the IP address of the VM (unless you can verify the name of the virtual machine can be resolved correctly).

  For example, try:

  NET use * \\192.168.142.128\c$ u:dpm6400cf - vm\administrator *.

  and enter the password when you are prompted.

  André

• How to remote desktop to connect to a Windows XP laptop with a new laptop Windows 10

  I want to control my laptop Windows XP in my office with my new laptop Windows 10 at home.  Can anyone help?

  I've used LOG-ME-IN or another site, but now it's $99.

  Main ways would be through a third party such as LogMeIn or VNC application, or if the computer is allowed VPN access you Office remotely. However, a lot of it depends on your business security policies, but if there is a business case and it is possible that they could buy an app like this (I of course assume office you mean a society rather than a bureau office at home). Although to be honest according to your business, the people who handle COMPUTER security may not react when they find out there is a XP computer connected network if they were not already aware.

• Difficulty accessing 1 remote desktop when connected with VPN

  Hello world

  I have an ASA 5505 and have a problem where when I connect via VPN, I can RDP into a server using its internal address but I can't RDP to another server using its internal address.

  One that I can connect to a an IP of 192.168.2.10 and I can't connect to a a 192.168.2.11 on 3390 port IP address.

  The two rules are configured exactly the same except for the IP addresses and I can't see why I can't connect to this server.

  I am also able to connect to my camera system with an IP on port 37777 192.168.2.25 and able to ping any other device on the network internal.

  I also tried ping he and Telnet to port 3390 without success.

  Here is the config.

  ASA 4,0000 Version 1

  !

  !

  interface Ethernet0/0

  switchport access vlan 3

  !

  interface Ethernet0/1

  !

  interface Ethernet0/2

  switchport access vlan 2

  !

  interface Ethernet0/3

  !

  interface Ethernet0/4

  !

  interface Ethernet0/5

  !

  interface Ethernet0/6

  !

  interface Ethernet0/7

  !

  interface Vlan2

  nameif inside

  security-level 100

  IP 192.168.2.2 255.255.255.0

  !

  interface Vlan3

  nameif outside

  security-level 0

  10.1.1.1 IP address 255.255.255.0

  !

  passive FTP mode

  clock timezone IS - 5

  clock to summer time EDT recurring

  network obj_any object

  subnet 0.0.0.0 0.0.0.0

  network of the OWTS-LAN-OUT object

  10.1.1.10 range 10.1.1.49

  network of the OWTS-LAN-IN object

  Subnet 192.168.2.0 255.255.255.0

  service of the RDP3389 object

  service destination tcp 3389 eq

  Description of DC

  the object SERVER-IN network

  host 192.168.2.10

  network of the SERVER-OUT object

  Home 10.1.1.50

  network of the CAMERA-IN-TCP object

  Home 192.168.2.25

  network of the CAMERA-OUT object

  Home 10.1.1.51

  service object CAMERA-TCP

  Service tcp destination eq 37777

  the object SERVER-Virt-IN network

  Home 192.168.2.11

  network of the SERVER-Virt-OUT object

  Home 10.1.1.52

  service of the RDP3390 object

  Service tcp destination eq 3390

  Description of VS for Master

  network of the CAMERA-IN-UDP object

  Home 192.168.2.25

  service object CAMERA-UDP

  Service udp destination eq 37778

  the object OWTS LAN OUT VPN network

  subnet 10.1.1.128 255.255.255.128

  the object SERVER-Virt-IN-VPN network

  Home 192.168.2.11

  the object SERVER-IN-VPN network

  host 192.168.2.10

  the object CAMERA-IN-VPN network

  Home 192.168.2.25

  object-group Protocol TCPUDP

  object-protocol udp

  object-tcp protocol

  AnyConnect_Client_Local_Print deny ip extended access list a whole

  AnyConnect_Client_Local_Print list extended access permit tcp any any eq lpd

  Note AnyConnect_Client_Local_Print of access list IPP: Internet Printing Protocol

  AnyConnect_Client_Local_Print list extended access permit tcp any any eq 631

  print the access-list AnyConnect_Client_Local_Print Note Windows port

  AnyConnect_Client_Local_Print list extended access permit tcp any any eq 9100

  access-list AnyConnect_Client_Local_Print mDNS Note: multicast DNS protocol

  AnyConnect_Client_Local_Print list extended access permit udp any host 224.0.0.251 eq 5353

  AnyConnect_Client_Local_Print of access list LLMNR Note: link Local Multicast Name Resolution protocol

  AnyConnect_Client_Local_Print list extended access permit udp any host 224.0.0.252 eq 5355

  Note access list TCP/NetBIOS protocol AnyConnect_Client_Local_Print

  AnyConnect_Client_Local_Print list extended access permit tcp any any eq 137

  AnyConnect_Client_Local_Print list extended access udp allowed any any eq netbios-ns

  implicit rule of access-list inside1_access_in Note: allow all traffic to less secure networks

  inside1_access_in of access allowed any ip an extended list

  outside_access_in list extended access allowed object RDP3389 any host 192.168.2.10

  outside_access_in list extended access allowed object RDP3390 any host 192.168.2.11

  outside_access_in list extended access allowed object CAMERA TCP any host 192.168.2.25

  outside_access_in list extended access allowed object CAMERA UDP any host 192.168.2.25

  pager lines 24

  Enable logging

  exploitation forest-size of the buffer 10240

  asdm of logging of information

  Within 1500 MTU

  Outside 1500 MTU

  local pool RAVPN 10.1.1.129 - 10.1.1.254 255.255.255.128 IP mask

  no failover

  ICMP unreachable rate-limit 1 burst-size 1

  don't allow no asdm history

  ARP timeout 14400

  NAT static destination SERVER-IN-VPN SERVER-IN-VPN (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

  NAT static destination of CAMERA-IN-VPN VPN-IN-CAMERA (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

  NAT static destination of SERVER Virt-IN-VPN-SERVER-Virt-IN-VPN (indoor, outdoor) static source OWTS LAN OUT VPN OWTS-LAN-OUT-VPN

  !

  network of the OWTS-LAN-IN object

  NAT dynamic interface (indoor, outdoor)

  the object SERVER-IN network

  NAT (inside, outside) Shared SERVER-OUT service tcp 3389 3389

  network of the CAMERA-IN-TCP object

  NAT (inside, outside) static CAMERA-OFF 37777 37777 tcp service

  the object SERVER-Virt-IN network

  NAT (inside, outside) Shared SERVER-Virt-OUT 3390 3390 tcp service

  inside1_access_in access to the interface inside group

  Access-group outside_access_in in interface outside

  Route outside 0.0.0.0 0.0.0.0 10.1.1.2 1

  Timeout xlate 03:00

  Pat-xlate timeout 0:00:30

  Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02

  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00

  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00

  Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute

  timeout tcp-proxy-reassembly 0:01:00

  Floating conn timeout 0:00:00

  dynamic-access-policy-registration DfltAccessPolicy

  identity of the user by default-domain LOCAL

  Enable http server

  http 192.168.2.0 255.255.255.0 inside

  No snmp server location

  No snmp Server contact

  Server enable SNMP traps snmp authentication linkup, linkdown warmstart of cold start

  Crypto ipsec transform-set ikev1 ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac

  Crypto ipsec transform-set ikev1 ESP-DES-SHA esp - esp-sha-hmac

  Crypto ipsec transform-set ikev1 SHA-ESP-3DES esp-3des esp-sha-hmac

  Crypto ipsec transform-set ikev1 esp ESP-DES-MD5-esp-md5-hmac

  Crypto ipsec transform-set ikev1 ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac

  Crypto ipsec transform-set ikev1 ESP-3DES-MD5-esp-3des esp-md5-hmac

  Crypto ipsec transform-set ikev1 ESP-AES-256-SHA esp-aes-256 esp-sha-hmac

  Crypto ipsec transform-set ikev1 ESP-AES-128-SHA aes - esp esp-sha-hmac

  Crypto ipsec transform-set ikev1 ESP-AES-192-SHA esp-aes-192 esp-sha-hmac

  Crypto ipsec transform-set ikev1 ESP-AES-128-MD5-esp - aes esp-md5-hmac

  crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 pfs Group1 set

  crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 define ikev1 transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP

  DES-SHA ESP-DES-MD5

  outside_map card crypto 65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP

  outside_map interface card crypto outside

  Crypto ca trustpoint ASDM_TrustPoint0

  Terminal registration

  name of the object CN = SACTSGRO

  Configure CRL

  Crypto ikev1 allow outside

  IKEv1 crypto policy 10

  authentication crack

  aes-256 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 20

  authentication rsa - sig

  aes-256 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 30

  preshared authentication

  aes-256 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 40

  authentication crack

  aes-192 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 50

  authentication rsa - sig

  aes-192 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 60

  preshared authentication

  aes-192 encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 70

  authentication crack

  aes encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 80

  authentication rsa - sig

  aes encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 90

  preshared authentication

  aes encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 100

  authentication crack

  3des encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 110

  authentication rsa - sig

  3des encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 120

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 130

  authentication crack

  the Encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 140

  authentication rsa - sig

  the Encryption

  sha hash

  Group 2

  life 86400

  IKEv1 crypto policy 150

  preshared authentication

  the Encryption

  sha hash

  Group 2

  life 86400

  Telnet 192.168.2.0 255.255.255.0 inside

  Telnet timeout 15

  SSH 192.168.2.0 255.255.255.0 inside

  SSH timeout 5

  SSH version 2

  SSH group dh-Group1-sha1 key exchange

  Console timeout 15

  dhcpd auto_config inside

  !

  a basic threat threat detection

  statistical threat detection port

  Statistical threat detection Protocol

  Statistics-list of access threat detection

  no statistical threat detection tcp-interception

  WebVPN

  username admin privilege 15 xxxxx encrypted password

  attributes of user admin name

  VPN-group-policy DfltGrpPolicy

  type tunnel-group CTSGRA remote access

  attributes global-tunnel-group CTSGRA

  address RAVPN pool

  IPSec-attributes tunnel-group CTSGRA

  IKEv1 pre-shared-key *.

  !

  class-map inspection_default

  match default-inspection-traffic

  !

  !

  Policy-map global_policy

  class inspection_default

  inspect the icmp

  !

  global service-policy global_policy

  context of prompt hostname

  no remote anonymous reporting call

  Cryptochecksum:0140431e7642742a856e91246356e6a2

  : end

  Thanks for your help

  Ok

  So, basically, you set up the router so that you can directly connect to the ASA using the Cisco VPN Client. And also, the goal was ultimately only allow traffic to the LAN through the VPN Client ONLY connection.

  It seems to me to realize that you have only the following configurations of NAT

  VPN Client NAT0 / free of NAT / identity NAT

  the object of the LAN network

  Subnet 192.168.2.0 255.255.255.0

  network of the VPN-POOL object

  subnet 10.1.1.128 255.255.255.128

  NAT static destination LAN LAN (indoor, outdoor) static source VPN-VPN-POOL

  The NAT configuration above is simply to tell the ASA who don't do any type of NAT when there is traffic between the network 192.168.2.0/24 LAN and VPN 10.1.1.128/25 pool. That way if you have additional hosts on the local network that needs to be connected to, you won't have to do any form of changes to the NAT configurations for customer VPN users. You simply to allow connections in the ACL list (explained further below)

  Failure to PAT

  object-group network by DEFAULT-PAT-SOURCE

  object-network 192.168.2.0 255.255.255.0

  NAT automatic interface after (indoor, outdoor) dynamic source by DEFAULT-PAT-SOURCE

  This configuration is intended just to replace the previous rule of PAT dynamic on the SAA. I guess that your router will do the translation of the ASA "outside" IP address of the interface to the public IP address of routers and this configuration should allow normal use of the Internet from the local network.

  I suggest you remove all other NAT configurations, before adding these.

  Control of the VPN clients access to internal resources

  Also, I assume that your current VPN client is configured as full Tunnel. In other words, it will tunnel all traffic to the VPN connection, so that its assets?

  To control traffic from the VPN Client users, I would suggest that you do the following

  • Set up "no sysopt permit vpn connection"
    • This will change the ASA operation so that connections through a VPN connection NOT allowed by default in order to bypass the ACL 'outside' interface. So, after this change, you can allow connections you need in the 'outer' interface ACL.
  • Configure rules you need for connections from VPN clients to the "external" ACL interface. Although I guess they already exist as you connect there without the VPN also

  I can't say this with 100% certainty, but it seems to me that the things above, you should get to the point where you can access internal resources ONLY after when you have connected to the ASA via the connection of the VPN client. Naturally take precautions like backups of configuration if you want to major configuration changes. If you manage remotely the ASA then you also also have the ability to configure a timer on the SAA, whereupon it recharges automatically. This could help in situations where a missconfiguration breaks you management connection and you don't have another way to connect remotely. Then the ASA would simply restart after that timer missed and also restart with the original configuration (as long as you did not record anything between the two)

  Why you use a different port for the other devices RDP connection? I can understand it if its use through the Internet, but if the RDP connection would be used by the VPN Client only so I don't think that it is not necessary to manipulate the default port 3389 on the server or on the SAA.

  Also of course if there is something on the side of real server preventing these connections then these configuration changes may not help at all.

  Let me know if I understood something wrong

  -Jouni

• sharing Windows 7 printer cable on my desktop and connect wirelessly to laptop both running Windows 7

  On my desk, I configure printer sharing, but it cannot add my laptop.

  I can use internet from my laptop using the network but no printer?

  Any help would be really appreciated

  Thank you

  Ray

  Hi Ray,

  We would like to know more about details to help you better.

  (1) what happens when you try to print by using the shared printer from your laptop? You get the error message?

  (2) is the shared printer is detected on your laptop?

  (3) what happens when you try to add the printer to your laptop?

  (4) have you enabled file sharing and printing on your laptop?

  (5) did you share the printer on the network?

  (6) you are able to print from the desktop?

  You can view the steps in the link below and then check if it works.

  Share a printer

   

  http://Windows.Microsoft.com/en-in/Windows7/share-a-printer

  Write us with the details asked so that we can understand the question better to help you.

• The mouse does not work in Remote Desktop

  I have a Win 7 64 bit Pro computer desktop that I try to run Remote Desktop to connect to my server Windows Home Server 2011. When I log in, my server's desktop is visible and I can see and move my mouse but when I left click of the mouse, nothing happens. Then if I click right, menu contextual office does not, but it is in the lower left corner, whenever I do a right-click No matter where I click. When the context menu displays and I hover over an element, it is not derivative of blue as it should. So basically just mouse doesn't work at all on the remote desktop.  However, the keyboard works.  I can click on the Windows key to bring up the menu start and use the arrow keys to navigate in it.

  Everything works fine on the server if I connect directly into it with the mouse and keyboard. I should also mention that exactly the same thing happens if I try to use remote desktop to connect to my Win 7 notebook Home Premium 64 - bit on my Windows 7 Pro Office above.

  And finally, if I use remote desktop to connect from my laptop or desktop to my Win XP Pro system at work, everything works perfectly fine. So is this something with the connection to a system Win 7 or WHS 2011? Any help appreciated. Thank you.

  I thought about it.  I had this program that runs on the server that reverses the mouse.  This is necessary, since I use a trackball turned 180 degrees for better comfort and "sakasa" mouse to use for the release of the mouse.  But I didn't need on the server and the system office.

• Unable to connect to the desktop computer running Windows 7 laptop running Windows 7, both in my home network, using remote desktop

  My desktop (host) is running Win7 Pro and my (client) laptop is running Win 7 Home Premium. For the office, I went to the control panel and allows remote connections. When I try to connect with the laptop in my same home network, I get an error message: Remote Desktop cannot connect to the remote computer you for one of the following reasons:

  (1) remote access to the server is not enabled

  (2) the remote computer is disabled

  (3) the remote computer is not available on the network

  Now, the computer is on and I can see what he listed as one of my computers on network. In fact, I accessed the command of remote desktop by right-clicking on the desktop in the list of networks and by selecting Remote Desktop in the menu dropdown.

  Obviously, I am missing something or something wrong. Please help me to understand.

  What do you call the remote [DRC] host desktop desktop machine, IE. local LAN IP static, the laptop?

  See this help as possible...

  http://theillustratednetwork.MVPs.org/RemoteDesktopTroubleshootingChecklist.html