locked
MED-V client loses connection to domain RRS feed

  • Question

  • Hello All,

    I've been working with a MED-V package for a single application in our enterprise as a temporary solution until the application can be upgraded.

    However, I'm running into an issue with it communicating to the domain. I can add the workspace fine and the workspace works fine for a couple days but it seems that after a couple days, particularly while not being used, it will not allow me to sign in with a domain account anymore. It simply says it cannot connect to the domain.

    What I have found is:
    The workspace is still in AD.

    I can ping the workspace by IP but not by hostname

    I have tried shared and bridged connections.

    I can ping the DNS and AD controllers from the workspace (VM).

    I have manually added the DNS servers to the NIC settings.

    The domain account under Profiles is listed as "account unknown".

    Any domain groups like "domain users" are listed by SID's and no longer by group names (an obvious sign of not connecting to the DC.)

    The DNS record has the wrong IP listed - which is why I can't ping by hostname.

    If I move the VM to a workgroup and then add back to the domain, it will work fine again, for a while.

    I do not have an OU to put the VM so that it does not get an GPO policies so it does get the GPO's. I'm wondering if it's a network issue or GPO, perhaps?

    Any ideas at all? I'm at a loss.

    Thanks!

    Tuesday, April 8, 2014 5:42 PM

Answers