Remote desktop OUTSIDE network

Hi all,
I'm a general user, not a server user, so I apologize in advance for my ignorance. Here are the specs:
Me: Mac Pro, 8 core, 10.6.8, wireless hookup via Comcast
Controlled computer: iMac, 10.7.1, no firewall, ethernet hookup via Comcast
Situation:
My grandparents are 92 and 95 and they've been Mac users for a decade and a half -- that said, they're in their 90s so if an icon gets moved or something is downloaded to a different location, the wheels fall off the truck. For the past several months they've been out of communication because they can't remember their email password (it's more likely that they aren't noting that the password is Case Sensitive). Their old iMac was the orange bubble iMac, so it was time for a replacement. I bought a new basic iMac and am going to ship it to them (they live in another state), but first I wanted to set it up exactly as they'd need it. While I have it, I figure now would be the best to set up VPN where any time they have trouble I can tunnel in via VPN and take over their computer as an admin.
I can't figure it out, sadly.
I am fairly sure Apple Remote Desktop only works for people in the same network and that's all I can find while researching on the 'net. Would that work once I use VPN for someone 1,000 miles away? How do I set it up? What software would you recommend (it doesn't have to be free)?
Am I right to think the following?:
I download a VPN client to my computer.
I download a VPN server to their computer.
I turn all sharing on via System Preferences on theirs.
How do I actually see and control their computer? How do I set up a user/pass to get in?
Note: Security is not an issue -- nothing they will do on this computer needs to be secure. It's web browsing, emailing, and Skype -- they don't have control of their own finances.
In a perfect world I can reset their passwords if they forget them, turn on some classical music while they're having dinner, change their background to pictures of their grandkids, do all of the system updates for them, and install new software that may help them.
MANY thanks to anyone who can help me figure this out!
Matt

Sorry for the length...
You actually can use ARD (Apple Remote Desktop) to Admin a computer from afar not connected to your network.  It does not require VPN or VNC access.  I do it all the time with a computer, also for my grandparents who are 81 & 83 years of age located in the Midwest...I live in California and access it about once a week when as you put it perfectly "the wheels fall off".
The key issues that I ran into when setting up the connection that I use are the NAT tunneling that is needed due to the Router that my grandparents use to connect to the Internet and the DHCP which I had to modify in their router for the assignment of private IP addresses in their home.  Since the router is set up for DHCP (needed) I had to specifically set up and assign a specific internal IP address as a static address to their single computer while maintaining the rest of the assignments as dynamic DHCP for the reasons that follow.  My sister goes to visit them frequently with her laptop (WIFI connection) and I take my laptop (WIFI Connection) and other devices (also WIFI) with me and access the net when I visit (about once a year) with their network.
The DHCP that the router uses to normally assigns internal IP's, does so on a first come first serve basis and creates issues where the IP address that ARD uses to access the client computer could potentially be assigned to another device if it connects to the network first before the client computer, or the client computer is assigned another IP address by the DHCP due to the routing table.  This causes some issues as in order to use ARD through a router to a client computer on another network you have to know the IP address for the connection (ISP assigned IP address) you are trying to enter through (often dynamic IP) and then you have to know the specific internal IP address for the computer on the network for NAT tunneling.
In my case my grandparents luckily are on a static IP address assigned to them by their ISP so I only had to overcome the Router configuration issues.  There are however reporting services that are paid (usually inexpensive) which use a small program on the client computer to broadcast the IP address to the secure service which then keeps record of the current dynamic IP that the computer is on so that if it changes with the ISP, one only needs to log into the service to retrieve this current IP and then they can access the client computer with it after reconfiguration of ARD. (This is the first mountain to climb)
The issue that often times these days is the second mountain that you have to climb is the DHCP and NAT tunneling.  This is in the client computers router configuration and is individual to each router manufacturer and model so I recommend consulting the manufacturers router manual on how to configure the router for NAT tunneling.  Not all routers can be set up for this, for instance my time capsule I have as a router behind a router configuration at my home to get full use of my 802.11N speeds for multiple devices that are capable of the N protocol will allow for this and the "Back to my Mac" service; which essentially does near to the same thing as ARD does, however my AT&T Uverse Gateway which is an 802.11G router...though quite sophisticated is actually not capable of the services needed to remote control the computer behind it as a client computer for “Back to my Mac” which is another reason I use the Time Capsule as a router behind the gateway.  It also gives me two separate private networks and a bit more security though can cause issues if not properly configured.
These are the issues that I ran into when setting up the remote administration of my Grandparents computer and I have successfully maintained this remote access for over a year now with few issues.  (It still blows my grandparents mind that I can do this from California).  I do have to say that the router configuration was done with another party (my mother) being my eyes and ears in the Midwest while she was visiting them, though it was my configuration instructions that allowed her to set up the router configuration for NAT tunneling and single internal static IP configuration while maintaining DHCP for other devices (she's wouldn't know where to begin when it comes to router configurations and I have CCNA training).
I hope this helps at least with the hurdles that need to be jumped in most remote network accesses using ARD and to assure people in need of this information or with questions regarding it that it can be done with the correct configuration and a router with the capabilities on the client side.
Also in case anyone is wondering my grandparents have a Netgear router though I don’t endorse any one router or manufacturer.  The important thing here is the routers capabilities not the brand or model.
Message was edited by: Dark_Angel

Similar Messages

  • Remote desktop into network won't work

    First time VPN newbie. I need to set up vpn for a friends small  business using RV082 so, as a test, I set it up here at my home using a  very basic config. The network topology looks like:
    cloud => cable modem => RV082 => DIR655 => win7 PC
    At  a remote site, I fire up QUICKVPN, enter necessary data and  successfully connect. Bring up Remote Desktop and put in the IP of my  home pc and the logon username and, after a minute or two, it says  "unable to connect to the computer" (or words to that effect). My home  PC has been configured to allow remote desktop connections and this has  occured in the past but not since the RV082 installation. There is  nothing in the PC's logs nor in the RV082's logs. What should be my line  of investigation?

    Hi Zym0tiC.
    I had a similar experience with my daughter's Arch Linux laptop using a PCMCIA wireless card to connect to the network after an upgrade this last Friday (I believe this was to kernel16-2.6.10-3).
    To make things work properly (although I haven't gotten to this fully resolved) I did the following: (a) invoked hotplug in rc.conf; and (b) made sure that all possible ethernet ports (in my case, eth0, eth1, and eth2) were specified in rc.conf (I used DHCP). The PCMCIA card is then recognized and connected using /etc/rc.d/network properly at boot (or by hand after boot).
    I'm going to look into this further to see if I can't understand this better.
    Regards,
    Win

  • Remote desktop to laptop running Window 7 from laptop running Windows 8.1 on same network

    I am trying to remote desktop into my Windows 7.1 laptop with my Windows 8.1 laptop.  They are both connected to the same network and I can ping each other with their dns names.  I can even use Windows Explorer to explore the file system of each
    laptop.  
    When I try to use Remote Desktop Connection I get the error message "The remote computer requires Network Level Authentication, which your computer does not support."  How do I turn this on in Windows 8.1?  
    I was able to figure it out on my Windows 7 laptop which I can remote into my Windows 8.1 laptop.
    Thanks for your help,
    Fred
    Fred Schmid

    When I uncheck the "Allow connections from computers running Remote Desktop with Network Level Authentication (recommended)", I still get the warning message:
    "The identity of the remote computer cannot be verified.  Do you want to connect anyway?"
    But it allows me to connect.
    What does that tell me?
    Also, when I right click on the icon in the upper left corner of the Remote Desktop Connection window it says that Network Level Authentication is support on both computers.
    Thanks for your help,
    Fred Schmid
    Hi,
    From the details in the error prompt, We could understand that the RDP client is trying to validate the remote server’s certificate. The RDP client throws error prompt when it could not trust the certificate. The good thing is, the RDP client allows
    us to bypass the certificate validation and connect to the server any way.
    The Ideal solution for this is to apply the correct certificate on the server. The Microsoft support article (http://support.microsoft.com/kb/2000960) explains how to verify the selected certificate on
    the server.
    In my case, I don’t have the control over the servers. But I’m sure the servers I connect, are trust worthy. So, It is annoying to see this error message every time when I connect to the servers. And, every time I have to select the check box “Don’t
    ask me again for connecting this computer“.
    Kate Li
    TechNet Community Support

  • Remote Desktop Network Level Authentication

    Recently, I began getting failed connections from a Windows 7 Enterprise client to another Windows 7 Enterprise host where the host is requiring NLA. This has been a problem on and off for YEARS and I have found no link that can tell me to configure something
    that I haven't already configured. Neither system underwent any configurations changes that I know of with the exception of Windows security updates/patches. In fact, some people in my company have the same issue while other do not. I can find no rhyme or
    reason to it. Heres where I'm at:
    "The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support."
    But I do. when i click the upper left hand corner of my RDP client window and select "About", I see this:
    "Remote Desktop Connection
    Shell Version 6.1.7601
    Control Version 6.1.7601
    Network Level Authentication Supported.
    Remote Desktop Protocol 7.1 supported."
    And the above info is exactly what it says on the host.
    Here's the SecurityProvider registry settings on the client:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders]
    "SecurityProviders"="credssp.dll"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SaslProfiles]
    "GSSAPI"="Kerberos"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
    "EventLogging"=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\CipherSuites]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
    "DisabledByDefault"=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest]
    "Debuglevel"=dword:00000000
    "Negotiate"=dword:00000000
    "UTF8HTTP"=dword:00000001
    "UTF8SASL"=dword:00000001
    "DigestEncryptionAlgorithms"="3des,rc4"
    Every link I have looked at tells me to look at those things. Anyone got something new? :)
    Also if someone knows how to log the RDP failures that would be cool too. Presently I have turned on Audit Other Security Events in GPO but it doesn't tell me if someone attempted to authenticate with a less then desirable security protocol.
    As a fix, for now, I have reduced the security requirements on the host to not require NLA. <-- This is the only consistent fix I have ever seen that works.
    By the way, just about every link I see also starts talking about setting up RD session host service. I am not running Windows Server 2008. This a Windows 7 to Windows 7 problem

    Hi,
    On both Windows 7, Please go to System Properties,
    Remote tab and make sure that Allow connections only from computers running Remote Desktop with Network Level Authentication
    is unchecked.
    If problem persists, please check if there was any Windows updates need to install, if so, try to install updates for test.
    Roger Lu
    TechNet Community Support

  • Remote Desktop to Windows 8 (in Azure) using a Windows Live Account

    This took me a while to find this answer so posting it again in case it help anybody and also perhaps somebody has a suggestion of a better way to do it.
    I spun up a Windows 8 Pro VM in Azure (using MSDN subscription) which gives me a local account to access it with via RDP. No problems there.
    I want to use a Microsoft Account on this VM instead of a local account however, because I want to sync my OneDrive (reason: I have a lot of data in the Cloud via backup programs like Carbonite and CrashPlan  that I want to move to my OneDrive as it
    has unlimited space now, but don't want to use home or work network for that move as it will take months to move it all about. Cloud-to-Cloud initial data move seemed like it would be quicker hence I am doing it in Azure.)
    I can't use OneDrive with the local account no matter what I tried so I had to log in as a Microsoft account.
    I tried adding my Microsoft Account to this VM, making it Administrator and then switching the local account to that one but this process failed (even tried different accounts, one without 2-factor auth. enabled: nothing.)
    I also tried RDPin in using the MicrosoftAccount\[email protected] rather than convert or link the local account but that didn't work either. "Your credentials didn't work." Even trying with just the email address didn't work. Nor did using
    an app password (I have 2-factor enabled of course.)
    The only way I was able to log in was to:
    Under System properties of the Windows 8 Pro VM, under Remote tab uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication"
    I follered these instructions to create and edit an RDP file on my local pc:
    http://support.microsoft.com/kb/941641
    Once I connected from my local pc with the modified RDP file to the Windows 8 Pro VM in Azure, I was prompted for the user to log in as by the VM, allowing me to select the Microsoft Account I had previously added instead of the local account which looked
    the same as if you do it physically at the machine. This had not happened before and once I did, everything was fine after that :-)

    Hi,
    Please use the original RDP file in another computer and install the certificate. And then use the new RDP for test
    Karen Hu
    TechNet Community Support

  • Cannot get Remote Desktop to work on Windows 7

    Ok. I am having issues trying to connect remotely using RDP. From what I know, the network was pre-configured from another IT group and was able to get it up and running. My company was commissioned to migrate his old PC (WINXP) to Windows 7. I have gone
    through the steps of allowing remote desktop and following instructions:
    To configure remote access, follow these steps:
    1. In Control Panel, click System And Security, and then click System.
    2. On the System page, click Remote Settings in the left pane. This opens the System Properties dialog box to the Remote tab.
    3. To disable Remote Desktop, select Don’t Allow Connections To This Com¬puter, and then click OK.Skip the remaining steps.
    4. To enable Remote Desktop, you have two options. You can:
    Select Allow Connections From Computers Running Any Version Of Remote Desktop to allow connections from any version of Windows.
    Select Allow Connections Only From Computers Running Remote Desktop With Network Level Authentication to allow connections only from Windows 7 or later computers (and computers with secure network authentication).
    5. Click Select Users. This displays the Remote Desktop Users dialog box.
    6. To grant Remote Desktop access to a user, click Add. This opens the Select Users dialog box. In the Select Users dialog box, click Locations to select the computer or domain in which the users you want to work with are located. Type the
    name of a user you want to work with in the Enter The Object Names To Select field, and then click Check Names. If matches are found, select the account you want to use and then click OK. If no matches are found, update the name you entered and try searching
    again. Repeat this step as necessary, and then click OK.
    7. To revoke remote access permissions for a user account, select the account and then click Remove.
    8. Click OK twice when you have finished.
    One thing that I found odd when he launched Remote Desktop from his home laptop is the IP entry:
    Computer> [Public Router IP]:49250
    Login> Domain\Admin
    Password> *****
    From the odd port number I would assume that was for port forwarding so I logged into his router and found exactly that. In port forwarding, he had the in/out as 49250 TCP to 192.168.30. I went into the firewall and enabled Remote Desktop in the inbound
    rules. 
    As of right now, I can use Remote Desktop to remote into the server, and withing their server, I cam use Remote Desktop to remote into the workstation. I just can't remote into the workstation directly using the port 49250. Any suggestions on this, something
    I have missing?
    He has Norton Security installed on this computer and I tried adding Inbound/Outbound rules to its 'Smart Firewall' to allow remote desktop and the port.

    Thanks for the reply.
    When I use Remote Desktop and use the Public IP of the router without the port number (49250), I am able to get into the server. However, when I try to use RDP with the [Public IP]:49250, it will not connect to the 192.168.0.30 workstation.
    Right now the router is program to forward port 49250 requests to the 0.30 workstation.
    I am going to work on the Inbound/Outbound Firewall settings today and see if this will resolve the issue.

  • Windows XP couldn't remote desktop Windows2012

    Hi Everyone:
    I have an issue as the following lines indicates.
    "An authentication error has occured.The specified target is unknown or unreachable"
    The remote side is Server2012,however the Windows 7 client can remote desktop the Windows Server 2012 sucessfully.
    Any help or suggestion will be appreciated.
    By the way how to verify my account,I want to insert a problem picture,however the system told me that I should verfiy my account by Microsoft first.

    Hi,
    Thank you for posting in Windows Server Forum.
    Agree with the words of Jeremy, firstly please check that required details for server connection. In addition, also verify that on your RDCB server, go to system properties, Remote tab and make sure that Allow connections only from computers running Remote
    Desktop with Network Level Authentication is unchecked.
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Remote Desktop Login events

    I am trying to capture through SCOM events when specific accounts RDP into servers.  I know it is logon type 3 but the workstation name the session is initiated from is blank.  Is there a specific configuration required to log this information?
    Thanks
    Paul
    Paul Glickenhaus

    IP addresses or workstations are not captured when Remote Desktop are enabled without Network level Authentication.
    Run sysdm.cpl to open system properties, select Remote -> Remote Desktop -> Allow Remote Desktop -> Allow connections only from computers running Remote desktop with Network Level Authentication.
    Also you can use
    this c# project to log authentication events in sql server

  • I want to remote desktop connect via Bluetooth

    I have two laptops on a little pan network. I can share folders and files between them. But I additionaly want to be able to establish a remote desktop connection between the two laptops. I'm not having too much success here. Can someone point me in the right direction? Thank you.
    Oh - XP Professional SP3. Toshiba BlueTooth Stack which hasnt been upgraded.
    Thanks again.

    I use remote desktop access - mstsc.exe - to remote all my servers at work.
    So I have my PAN at home on two XP Pro SP3 laptops w/ internal bluetooth. I run mstsc.exe and cannot see my other computer across the PAN. I can share folders without issue. Both laptops are in the same workgroup but mstsc.exe fails.
    I'm missing something.
    Ahhhh. Figured it out. The remote desktop access network configuration is in it's options. The computer field has a drop down menu, I was expecting it to populate being a drop down menu. But there were no menu items listed. That throw me off. But I just typed my other computer's name in the field and it connected me to the log in screen and my other comuter is now listed in the drop-down menu. That how its done.
    It's slow though. But I knew that.

  • Group Policy to Force Remote Desktop NLA Radio Button

    Hey Guys:
    I'm looking for a script or GPO to force the Network Level Authentication (NLA) for Remote Desktop.
    I've searched and found a lot of info on how to disable the "less secure" remote desktop option but can't figure out how to force the "more secure" radio button.  When I disable the "less secure" option Windows still defaults
    at "Don't allow connections to this computer".  
    That's what I want to change.  I want the GPO to force the "Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)" option.
    Any ideas?
    Thanks!

    In order to do this you have to enable the two separate GPO settings below:
    Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security
    Require user authentication for remote connections by using Network Level Authentication
    Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections
    Allow users to connect remotely using Remote Desktop Services

  • Microsoft Remote Desktop and small network, pc and macs

    I have a machine running 8.1 pro with a connected printer, networked via an unmanaged switch to two macs in the network. One mac is a headless mac mini, the other is a mac pro i am using to access the pc via MRD. This network is not connected to the internet.
    I can ping the pc from the macpro, and can see files shared on the pc, but cannot get MRD to connect.
    One network cable from the macpro is connected to the isp's router, the other to the switch connecting the three machines. That second connection has a self-assigned ip, and the internet connection on the macpro is not shared.
    On the pc in ipv4 properties, the ip address is set manually. Ip address and subnet mask are there (169.254.94.25 and 255.255.0.0) and default gateway is blank. Workgroup is set up as private. Remote Desktop is enabled. Firewall seems to be right. Windows
    Network Diagnostic says no issues detected.
    I've tried MDR settings with the ip address of the pc in gateway and also without, leaving gateway blank and just using the name of the pc with the same result: "Unable to connect to remote PC. Please verify Remote Desktop is enabled,..."
    The switch and cables are good. If I connect the switch to the router and change the ipv4 address to automatic, I can connect to the PC with MRD.
    Any suggestions? Is there a setting I'm missing? I've searched the Microsoft site for help but find only the most general instructions, which I think I've followed.
    I've asked this question on the Windows Web and Network discussion and was advised to post it here by the support engineer.

    Hello JAS42,
    If my understanding is right, one network cable from MAC pro is connect to the switch and the Windows 8.1 PC is connect to the switch too, and the IP setting in the Windows 8.1 is ‘(169.254.94.25 and 255.255.0.0) and default gateway is blank’.
    If a DHCP server cannot be found or does not respond after one minute, the DHCP client checks the settings on the Alternate Configuration tab of the properties of the TCP/IP protocol.
    If Automatic private IP address is selected, the DHCP client auto-configures its IP address and subnet mask by using a selected address from the Microsoft-reserved Class B network, 169.254.0.0, with the subnet mask 255.255.0.0.
    Does the switch have the dhcp function?
    What is the network setting in the MAC pro? We could manually configure the IP settings of Windows 8.1 network connection and the connection in the MAC to the switch in the same subnet, and then check if the issue still exists.
    For more information about subnet, please take a look at the following article.
    http://technet.microsoft.com/en-us/library/cc958832.aspx
    Best regards,
    Fangzhou CHEN
    Fangzhou CHEN
    TechNet Community Support

  • Remote Desktop Connection - Windows Network Level Authentication

    Hi
    I'm trying to find a piece of Remote Desktop "Manager" software for Mac which supports Network Level Authentication (NLA). When NLA is enabled on a Windows Server I am unable to connect via CoRD or Royal TSX.
    The reason I say "Manager" is because I have many, many windows servers I need to connect to and so I like to use software such as the above to save a list of all the servers for ease of access - this saves me having to type in the name of the server each time.
    At the moment, for those servers with NLA enabled, I have to fire up Remote Desktop Connection for Mac and enter the name. I realise I could save this each time but then I would have LOADS of shortcuts.
    Any ideas/proposals on pieces of software that can cater for this?
    Thanks!

    Hi!
    Royal TSX actually supports NLA but you have to use the FreeRDP plugin instead of CoRD and enable the setting in the advanced settings of your RDP connection.
    cheers,
    felix

  • My printers works fine on my home network but disappears on a remote desktop terminal connection

    As I don't really know how to post a general addition to the knowledge base, I'm doing in Jeopardy style.  Here is the question to the above answer.  Well close enough.
    Many people have reported all over the net issues with printers working just fine on their home network  but disappearing when they connect to a server via RDT.  There are some legit updates needed where windows did not see anything but LPT and COM ports for printer re-direction assignment.  There are Mr. Fix it's for those and registry patches.  When all of that fails, the information highway seems to dead end.
    Here is what I learned today via 2 specific printers:  HP1022 and HP2840 lasjerjets.
    After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others.  This problem as far as I have come across deals exclusively with HP printers.  In simple terms:  the drivers are flawed.  This 1022 is a prime example.  It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder.  Enter a remote desktop session and ALL of them populate except the 1022.  This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers.  All except the 1022. 
      Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver.  I used a 1200 PCL driver.  Now log back into your RDT server and hockus pocus! there is your printer.  Totally un-usable because the driver will not run this printer.  Caveat:  each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
    Moving on we go to the HP OfficeJet/LajerJet2840.  Same thing.  It won't pass through as remote printer in RDT.  Go local.  Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
    While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
    Hey HP?  Whats with the drivers??
    Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing.  You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

    As I don't really know how to post a general addition to the knowledge base, I'm doing in Jeopardy style.  Here is the question to the above answer.  Well close enough.
    Many people have reported all over the net issues with printers working just fine on their home network  but disappearing when they connect to a server via RDT.  There are some legit updates needed where windows did not see anything but LPT and COM ports for printer re-direction assignment.  There are Mr. Fix it's for those and registry patches.  When all of that fails, the information highway seems to dead end.
    Here is what I learned today via 2 specific printers:  HP1022 and HP2840 lasjerjets.
    After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others.  This problem as far as I have come across deals exclusively with HP printers.  In simple terms:  the drivers are flawed.  This 1022 is a prime example.  It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder.  Enter a remote desktop session and ALL of them populate except the 1022.  This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers.  All except the 1022. 
      Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver.  I used a 1200 PCL driver.  Now log back into your RDT server and hockus pocus! there is your printer.  Totally un-usable because the driver will not run this printer.  Caveat:  each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
    Moving on we go to the HP OfficeJet/LajerJet2840.  Same thing.  It won't pass through as remote printer in RDT.  Go local.  Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
    While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
    Hey HP?  Whats with the drivers??
    Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing.  You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.

  • Trouble Printing to Network Printer via Remote Desktop Connection

    Specs:
    Macbook Pro, early 2013,
    Mavericks (10.9.2),
    Microsoft Remote Desktop Connection v.8.0.5 (latest),
    Connecting to Windows Server 2008 standard
    Printer, HP LaserJet P2035n, connected via the network
    When on the Mac connected to the server, the printers from the Mac are redirected so you're supposed to be able to print from Remote Desktop to the HP printer.  However, when you select something to print, the job goes to the print and keeps printing over and over and over again until you cancel the print job, which it usually allows you to do, or turn off the printer, which you have to do when it won't let you cancel the job.
    Any advice on how to get the printer connection running normally?

    What you haven't told us is what method you use to connect/setup the printer on Windows. There are two ways - Bonjour for Windows (free software from Apple), and TCP/IP raw port 9100. If you have a problem using one, try the other.

  • Remote Desktop in Server 2012 is inaccessible from outside of LAN

    We have a server 2012 machine it was setup and accessible via Remote Desktop for months.  A few days ago we wiped it and did a fresh install of Server 2012.  Now we can not remote to the server from outside of the LAN, even though it is setup exactly
    as it was before. 
    Here is a checklist of things I have checked while trying to figure out the break:
    Router/firewall is forwarding port 3389 to the correct internal static IP of the server.  Port forward test tools online confirm the port is open.
    Windows firewall is set to allow all connections for Remote Desktop on 3389.  Also tried turning off firewall completely, does not fix the issue.
    Allow remote connections is enabled in System Properties, and users have been added to the list of allowed user
    Additional info:  The server is also a standalone Active Directory and Domain Controller.
    Remote desktop connections work fine while in the office on the LAN.  When remoting to the external IP, it doesn't work, even though it did only days before we re-did the server.
    Thanks!

    What should I check in AD?  I am by no means an expert with AD.
    Yes, I am using the same client OS.
    I am talking about RDP over the internet, like from home to the office.  We have a static IP assigned to the router from ISP.  A static internal IP assigned to the server on the LAN.  And the router port forwards 3389 to the assigned IP. 
    It was working fine before we reinstalled Server 2012.  These are the steps I took when reinstalling:
    1. format drive and install OS
    2. rename the server
    3. install SQL server
    4. Install TFS and SharePoint
    5. Add Active Directory role and promote to Domain Controller
    6. Add domain users
    7. Enable remote access on the server and add users to remote access list

Maybe you are looking for

  • Sending an email with attachments in Java using FileUpload UI Element

    Hello Experts, I'm using NWDS 7.01 SP6. I have an application that has a FileUpload ui element. The elements resource property is bound to a context node of type Resource from the Local Dictionary from uielementsdefinitions. The question I have is, h

  • Prompt for user name and password when opening an application like Internet Explorer

    Hi I often use Internet Explorer using "Run as different user".  This is achieved by holding 'Shift' and right clicking the IE icon.  This is the main reason why I use IE as my default browser is Chrome.  Signing in as a different user is helpful whe

  • How to move ringtones to new phone?

    I recently got an iPhone 5S, but did not move my ringtones at the time of purchase. I still have them on my Windows laptop, but cannot figure out a way to get them on the new phone. I pushed them up to the iCloud, I added them to iTunes (on my laptop

  • MB Pro 08 power up click at DVD, HD

    Strange situation--Leopard with Firefox 5 all updates. Firefox has continually had issues with a dozen tabs open, where there will be spinning ball and lots of page file (VM) thrashing, up to 4 GB or more in a session. Often Firefox would hang on qui

  • Multiple downloads of same album.

    Twice now, when I am downloading a album I bought off itunes it downloads 3 or more copies of the same album.  This has happened twice now with music I ordered in advance of release.  Anyone else have this problem?  I don't really mind having to dele