Struggling with Remote Desktop to Windows 8.1 Guest OS running Win 8.1 Pro Hyper-V

Host:  Windows 8.1 Professional with Hyper-V
Guest: Windows 8.1 
Networking:
Host is running wifi
Created a internal network that is bridged to WIFI.
Host can connect to internet.
Guest can connect to internet.
Problem:
Cannot RDP from host to guest.
Note:
- Guest allow remote management is turned on
- Tried with firewalls turned off
- ping from host to guest works
- ping from guest to host works
What can I do?

The message is a generic one
Remote Desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) THe remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled
Just to note:
- I did enable remote access in guest (but maybe it did not work)
- remote computer (guest) was turned on (VM was running)
- remote computer could be pinged. Perhaps there were other problems in routing traffic into the guest

Similar Messages

  • Novell login not available with remote desktop on windows 7

    Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

    djaquays <[email protected]> wrote:
    > Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
    > in an RDP file and there's no GUI equivalent to force legacy
    > authentication.
    Microsoft's Network Level Authentication (NLA) feature is supported in
    Windows Server 2008 and later terminal servers, and supported by
    Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
    Windows XP did not ship with a MSTSC 6.x terminal client, but it is
    available optionally through Windows Update.
    The NLA authentication is essentially requiring that valid Windows
    user account credentials for the Windows Server machine must be
    provided /before/ the RDP-level terminal session connection is even
    attempted or permitted. If the Windows user credentials you're logged
    in with on the client workstation do not already satisfy this
    requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
    credentials before even attempting to open the terminal session.
    In other words, NLA doesn't directly have anything to do with whom you
    will become authenticated as within the terminal session, or whether
    you'll reconnect to some other already-running terminal session; it's
    a new default mechanism which requires Windows credentials for
    authorizing you to create an RDP connection to the Windows Server
    machine "at all."
    Unfortunately Windows Server 2008 and later don't permit you to turn
    NLA completely off. You can configure the Windows Server to always
    require NLA, which means pre-MSTSC 6.x terminal clients will be unable
    to connect. Or you can configure the Windows Server to "not require
    NLA" ("Allow connections from computers running any version or Remote
    Desktop"), but this still means Windows Server will use NLA if the
    workstation's MSTSC client supports NLA.
    The only option which has been available to "disable NLA" even when a
    Windows Server 2008 or later terminal server and a MSTSC 6.x or later
    terminal client are involved is to configure the
    "enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
    (e.g. default.rdp in the My Documents folder), in addition to
    configuring the terminal server to "not require NLA."
    Once you have "Allow connections from computers running any version or
    Remote Desktop" set on the Windows Server, and
    "enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
    the Windows XP & Windows Server 2003 behavior where an RDP terminal
    connection can be established without first having to supply NLA
    credentials, and the first thing the MSTSC client user will experience
    is the full normal credential provider-based login experience just
    like you see at the physical console of the terminal server.
    Note that if you do leave NLA enabled and supply NLA credentials
    during the MSTSC connection attempt, after successfully using those
    credentials to authorize creation of the RDP connection, the MSTSC
    client will /also/ default to using the NLA credentials as default
    credentials to attempt logging on with within the terminal session
    itself. In other words, if you successfully supply NLA credentials,
    by default you also become logged in on the terminal session and go
    straight to the desktop of the Windows user account specified in the
    NLA credentials. So even though "NLA credentials" and "whom I will
    logon as within the terminal session" are two separate things, by
    default the MSTSC client tries to use the same credentials for both.
    But it's not that the NLA credentials "must" be used for logging in on
    the terminal session; that's simply the default behavior. If you
    leave NLA enabled on the Server 2008 or later terminal server, after
    NLA credentials are successfully used to authorize creation of an RDP
    connection, if you wanted to instead be prompted within the terminal
    session with the normal credential provider login experience, enable
    the "Always prompt for password" on the Windows Server 2008 or later
    terminal server.
    (On the Server 2008 or later machine, under "Administrative Tools"
    find the "Remote Desktop Services" group and launch the "Remote
    Desktop Session Host Configuration" console. Highlight/select the
    "RDP-Tcp" connection, right-click and select "Properties". On the "Log
    On Settings" tab elect "Always prompt for password".)
    That sounds like probably the scenario which fits best for the "I have
    a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
    / authentication level:i:0." You would leave NLA enabled on the
    Server 2012 machine, but enable "Always prompt for password" in the
    RPC-Tcp connection properties on the Server 2012 machine. Such that
    after NLA authentication was performed and Windows allowed creation of
    the terminal session, instead of immediately also attempting to login
    within the terminal session as the Windows account specified in the
    NLA credentials, Windows will instead present the normal interactive
    credential provider login experience to allow the user to specify whom
    they want to login as.
    Finally, note that everything described above applies even to a
    Windows Server and Windows client workstation that do /not/ have the
    Novell Client for Windows installed. The same mechanisms remain in
    effect even once the Novell Client is installed; the presence of the
    Novell Client just changes what credential providers would be used or
    presented within the terminal session once the terminal session was
    allowed to be created. The fact that NLA is required by default and
    requires valid Windows credentials in order to authorize an RDP
    connection is still the same, regardless of whether the Novell Client
    is present or not.
    Alan Adams
    Novell Client CPR Group
    [email protected]
    Novell
    Making IT Work As One
    www.novell.com
    Upgrade to OES Community
    http://www.novell.com/communities/co.../upgradetooes/

  • Sun Ray 1 with remote desktop on windows 7 ultimate

    I have a windows 7 ultimate box. I have an unopened Sun Ray 1. Before I open the box, I want to know if I can use the Sun Ray 1 to connect to my windows 7 ultimate box. If I can, how do I do it? Is it easy?
    Thanks

    No. Sun Rays are truly thin, meaning there is no OS or clients installed on the device. You need a server to use it.

  • Problem with Remote Desktop on iPad 2 and windows 8.1 pro

    I downloaded the Microsoft Remote Desktop app from the App Store on my iPad 2. I typed in the IP address for my windows 8.1 pro computer on my iPad 2 in school to try connecting to my windows 8.1 pro computer at home. I'm having
    a hard time doing it. Do I need a rd remote gateway to access my computer from outside my local network. If so, how do I find my gateway server name? Also, I saw somewhere that I have to press accept in a pop up message on the computer your trying to connect
    to. Is this true? No one is home during the day and my iPad 2 has to stay in school. Can you please give me a step by step guide with photos to help me connect to my windows 8.1 pro computer from my iPad 2 from school, which is of course outside my local network.

    Hi,
    Please refer to the document below for the procedure to use Microsoft Remote Desktop APP of IOS APP store.
    Getting Started with Remote Desktop Client on iOS:
    http://technet.microsoft.com/en-us/library/dn473013.aspx
    Roger Lu
    TechNet Community Support

  • How to set a default printer using vbs on windows 2008 R2 with remote desktop services

    Hello
    It seems I wasn't in the right places before / threads. BIG Sorry.
    Here's the problem: I have this VBScript:
    On any computer, the Default Printer "HisBadPrinter"
    strPrinterName = "mySuperPrinter"
    Set objPrinter = Helper.CreateObject("WScript.Network")
    objPrinter.SetDefaultPrinter strPrinterName
    In Xp, Windows 7 it work perfect, The default printer is being changed.
    But in Remote Desktop on Windows Server 2008 R2 it is not working, with any type of account (Administrator, user, powerUser...) "HisBadPrinter" is always the default printer and it's always printing on it without any error messages.
    Help Please.

    Ok, here what I have in my ControlPanel > Devices and Printers
    Adobe PDF (redirected 3)
    Brother HL-4150CDN series on infovm1dc (redirected 3)
    Generic / Text Only (redirected 3)
    HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
    Microsoft XPS Document Writer
    Microsoft XPS Document Writer (redirected 3)
    PDFCreator (redirected 3)
    Now Here what I got when I executed the bit of code :
    TS011
    Adobe PDF (redirected 3)
    TS013
    Microsoft XPS Document Writer (redirected 3)
    TS012
    Generic / Text Only (redirected 3)
    TS015
    Brother HL-4150CDN series on infovm1dc (redirected 3)
    TS016
    HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
    TS014
    PDFCreator (redirected 3)
    TS002
    DIRECT - Brother HL-2460 (redirected 2)
    TS006
    PDFCreator (redirected 2)
    TS003
    Fax (redirected 2)
    TS005
    Microsoft XPS Document Writer (redirected 2)
    TS007
    Brother HL-2460 on infodc3 (redirected 2)
    TS004
    Microsoft Office Document Image Writer (redirected 2)
    TS001
    Brother HL-4150CDN series on infovm1dc (redirected 2)
    XPSPort:
    Microsoft XPS Document Writer
    There is no printer called "\\ALPHA\HP LaserJet P2015 Series PCL 6".
    OK  

  • Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

    Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server.  On 32 bit Windows
    7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

    I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
    I think Windows 8.1 is not telling the terminal server what printers it has.

  • How to connect a printer with Remote Desktop for Mac, version 8

    Hello,
    I use Microsoft Remote Desktop 8.0.3 with my Mac to connect to an application which is based on a Windows Server 2008.
    I don't find the way to print to my Mac. I don't find the menu for it :-(
    Same problem to transfert a file from the Windows Server to my Mac :-( :-(
    Can you help me ?
    Many thanks in advance
    William

    Hi William,
    Please make sure that Forward printing devices is checked. This allows you to use the local printer connects to your Mac in a remote desktop session.
    Getting Started with Remote Desktop Client on Mac
    http://technet.microsoft.com/library/dn473012
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Remote Desktop and Windows 8.1

    I may not have this in the correct form area, and if so, I apologize.
    I have Windows Sever 2012 datacenter running and until about a week ago, from my Windows 8.1 (with Update), I could remote into the unit with remote desktop connection.
    Now, when I try the window pops up that a session on my computer is already in progress (the Windows 8.1 says this).
    I can remote ok from the 8.1 to other servers and other PCs.
    I can remote from other PCs into the Server 2012.
    I can EVEN remote into the Server 2012 from the 8.1, BUT I have to use the IP address of the server in the remote connection box.
    Same subnet, same domain.  Worked fine until about two weeks ago and started after no updates or such.  Can ping to and from both units by both name and IP with no issue.
    Please advise and thank you!
    Darryl Robertson

    Similar problem found:
    a session on my computer is already in progress
    http://craigshoemaker.net/blog/avoiding-remote-desktop-connection-error-console-session-in-progress
    Need more information for the troubleshooting:
    How you start remote desktop? Shortcut or "mstsc" command?
    Try command and post result:
    mstsc /v servername /admin
    or
    mstsc /v servername /console
    Have you checked the server, is there undisconnect console session on it?

  • Ipad bluetooth keyboard not working with remote desktop

    My clients ipad bluetooth keyboard works any other time, just not when connected to his servers via the remote desktop. PC Windows 7 Servers.
    I'm trying to get the keyboard information, but any ideas?

    Are you using an app like LogMeIn Ignition to access your servers? I believe that LogMeIn Ignition requires you to tap a little keyboard button near the bottom of the screen to activate use of the keyboard (that's how it works in Splashtop Remote, can't be much different in LogMeIn Ignition.)
    Are you sure the app you have supports blue tooth keyboard support with remote desktop? (not sure if they have to, I just recall seeing this in Splashtop patch notes awhile ago.)
    HuskieN.

  • Remote desktop to windows using vpn

    I am unable to remote desktop my window based office pc from my mac book pro using VPN.
    I even tried to install rdp , but no luck.Please respond asap.Thanks.

    Try TSclientX. I got so sick and tired of MS RDP and the license crap. I mean, it comes bundled with Office, and still stops working every few weeks.
    TSclientX  just works.

  • Stuck with Remote Desktop 3 without the serial number:(

    I am the new tech assistant for my lab of 35 macs..
    The computer used for managing the lab with remote desktop has crashed.
    I have found an older model mac with remote desktop. I'd like to transfer that application
    to my newer mac...but It will ask me for the serial number of which I do not have.
    The old tech assistant has gone..and along with it...the software and document.
    I have turned this lab upside down and I've found the box Apple Remote Desktop 3
    but nothing else. I thought maybe the serial number would be on it.  But I see
    only the bar code... I am frustrated to no end. They don't answer my emails for help
    Sincerely,
    Love using Apple Remote Desktop 3 user but can not anymore:(

    IIRC the serial number was never on the outside of the box so have you looked inside the box? Do you see the booklet that came with the box? Is the Serial Number inside? The Serial Number takes this form:
    XARD-030-000-x-xxx-xxx-xxx-xxx-xxx-xxx-x
    Who is not answering your emails for help?
    Having read the terms and conditions of this forum prior to posting you'll know these are user-to-user forums and Apple are not listening, so it's difficult to see what any of us here can do to help? Perhaps if you find the purchase receipt you might be able to contact your local Apple Rep and ask if they have a record of it?
    You can still use Remote Desktop by purchasing it again from the App Store. It costs far, far less than the installer media version and does not require a serial number. All you need is an Apple ID and an associated debit or credit card.

  • Troubleshooting error with Remote Desktop 3.1

    Have OSX Server 10.4.10 on a powerPC with Remote Desktop 2.2, Security scans advise to update to Remote Desktop Client 3.1. Everytime I do this I get this error "The Remote Desktop Administrator software failed to start du to an unexpected error. The Remote Desktop software may not be installed correctly or the computer may require a restart."
    I have two machines on this network that are giving this error, one this server and the other a laptop. Version 2.2 was running and working just fine prior to the update, now its broke. Is there a log file somewhere to try to figure this error out? Has anyone else experienced this issue? I have already tried to reset permissions, and reboot, but nothing works.

    Just to confirm my understanding, you are running the ARD 2.2 Administrator on the server, and something is advising you to upgrade that system to the ARD 3.1 client? If that's the situation, then do not upgrade. The 3.x client will not work with the ARD 2.2 administrator. If you did indeed upgrade, you'll need remove ARD using the instructions here and then reinstall ARD 2.2 from your installation disks.
    Similarly, if you've upgraded any client workstation to the 3.x client, you'll need to remove it and reinstall the 2.2 client using this installer. It says it's an "updater", but it will work anyway.
    Hope this helps.

  • Remote desktop help windows 7

    Hallo
    Im work as a help desk . i use remote desktop help windows 7 but some time i have to wait 10 min to the end user because he is not in his place or ...
    can i use another software without enduser permission? if yes then wich one
    Thanx

    Hi,
    Based on my research and test, it's impossible. Even shortening time is also unreachable.
    Karen Hu
    TechNet Community Support

  • Hardware acceleration has been disabled because it is in compatible with remote desktop

    So I go and lock my pc only to come and find that after effects says hardware acceleration has been disabled because it's incompatible with remote desktop
    I have looked around and others have said to delete a certain preference file but they did not give the file location
    Does anyone know where this pref file is?

    And what is the question? C'mon, the files and folders are properly labeled. Don't make it any more complicated...
    Mylenium

  • My keyboard doesn't work when I connect to a Windows 7 computer with Remote Desktop.

    I got a new computer at work that has Windows 7 Professional 64-bit on it.  I set up a Remote Desktop connection from my iMac at home and connected.  However, when I tried to use the keyboard, nothing happened.  After a little pecking I found that the DELETE key worked.  Also, I found that the keyboard would work correctly if I held down the FUNCTION key.  Very weird.
    My old Windows XP computer was still connected so I connected to it via Remote Desktop.  The keyboard works normally there.  It has always worked in Windows XP so I was surprised when it didn't work in Windows 7.
    I've been searching but haven't found anyone with this same issue.  Any help or suggestions would be appreciated.  Thanks.
    Steve Lockridge
    iMac 21.5 inch, mid-2010
    OS X 10.7.5 (Lion)
    3.2 GHz Intel Core i3
    12 GB RAM
    Apple Wireless Keyboard

    1. Did you use Bootcamp Assistant?
    2. Did you build a USB with Windows 7 ISO and Bootcamp drivers?
    3. You should use a USB2.0 disk, not a USB3.0 disk (flash drive).
    4. What year is the Retina MBP?

Maybe you are looking for

  • The attempt to burn a disc failed. An unknown error occurred (-50)

    Hey Guys, Got the error message "The attempt to burn a disc failed. An unknown error occurred (-50) in iTunes. I'm just trying to burn a few audio CDs. Running most current verison of Mavericks, all software up to date. I've tried changing the burnin

  • Bluetooth not working on reboot

    Hi, all- Last night I had to reboot my iMac twice and each time when I reached the logon screen neither my magic mouse nor keyboard worked to allow me to log on. I had to resort to using an old Logitech USB dongle, which, amazingly, allowed my mouse

  • ISR vs Adobe forms

    Hi, How flexibel can a form be. Can i get all the fields from ISR and put it in a form. So that means That ISR decides which fields are in the form... Are there also weblogs and tutorials for WDP, ISR and Adobe forms Regards

  • Downsampling pdf's

    I have a four page pdf scan of some images that I prepared which is 53 MB and I have not been able to email this document. This originally was a four page contact sheet prepared with Aperture or Adobe Elements, I then printed to pdf with Preview and

  • Project created on Mac moved to PC

    User Scenario - Create a Premiere Pro CS6 project using a Blackmagic Intensity Shuttle capture card on a Mac OSX machine.  Edit the sequence to my liking on the Mac.  Copy the project and all its files to a PC (also using CS6 but obviously the PC ver