|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
11-25-2008
| #1 (permalink) |
| | RE: cannot connect virtual network adapter Quote: > Virtual Server 2005 R2 > > When a virtual machine is configured with the "Always automatically turn on > virtual machine" option the NIC of that virtual machine reports "network > cable unplugged". If the virtual machine is then reconfigured to the default > "Never automatically turn on virtual machine" the NIC works fine. > > The event log massage is... > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > because either the virtual network is invalid or access was denied. This > virtual network adapter will be left disconnected." > > The documentation says to use an account with read, write, and execute > permission on the virtual machine configuration file but this does not work. > This only works if the startup account used is a domain admin. What am I > missing? How do I make this work using a domain user or host local user > account? > The fix appears to be simple... for me it was a pain. If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. The VM start up account MUST have admin provledges on the HOST system. Poof, it works! Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com |
My System Specs |
|
02-13-2009
| #2 (permalink) |
| | RE: cannot connect virtual network adapter giving a account every right there is in the world is no fix! You should NEVER give admin rights to any program or human just because it works that way. VS guest autoboot account works fine once you set the correct rights on the files as descriped in microsoft documents. Those correct ones are hard to find though. In this case, rights were given on the machine files but not to the VNC-file. Just make sure the account can read the VNC-file "Brad Rosse" wrote: Quote: > Quote: > > Virtual Server 2005 R2 > > > > When a virtual machine is configured with the "Always automatically turn on > > virtual machine" option the NIC of that virtual machine reports "network > > cable unplugged". If the virtual machine is then reconfigured to the default > > "Never automatically turn on virtual machine" the NIC works fine. > > > > The event log massage is... > > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > > because either the virtual network is invalid or access was denied. This > > virtual network adapter will be left disconnected." > > > > The documentation says to use an account with read, write, and execute > > permission on the virtual machine configuration file but this does not work. > > This only works if the startup account used is a domain admin. What am I > > missing? How do I make this work using a domain user or host local user > > account? > > > > The fix appears to be simple... for me it was a pain. > > If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. > > The VM start up account MUST have admin provledges on the HOST system. > > > Poof, it works! > > Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com > |
| My System Specs |
|
02-13-2009
| #3 (permalink) |
| | RE: cannot connect virtual network adapter test. "Brad Rosse" wrote: Quote: > Quote: > > Virtual Server 2005 R2 > > > > When a virtual machine is configured with the "Always automatically turn on > > virtual machine" option the NIC of that virtual machine reports "network > > cable unplugged". If the virtual machine is then reconfigured to the default > > "Never automatically turn on virtual machine" the NIC works fine. > > > > The event log massage is... > > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > > because either the virtual network is invalid or access was denied. This > > virtual network adapter will be left disconnected." > > > > The documentation says to use an account with read, write, and execute > > permission on the virtual machine configuration file but this does not work. > > This only works if the startup account used is a domain admin. What am I > > missing? How do I make this work using a domain user or host local user > > account? > > > > The fix appears to be simple... for me it was a pain. > > If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. > > The VM start up account MUST have admin provledges on the HOST system. > > > Poof, it works! > > Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com > |
| My System Specs |
|
02-13-2009
| #4 (permalink) |
| | RE: cannot connect virtual network adapter test "Brad Rosse" wrote: Quote: > Quote: > > Virtual Server 2005 R2 > > > > When a virtual machine is configured with the "Always automatically turn on > > virtual machine" option the NIC of that virtual machine reports "network > > cable unplugged". If the virtual machine is then reconfigured to the default > > "Never automatically turn on virtual machine" the NIC works fine. > > > > The event log massage is... > > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > > because either the virtual network is invalid or access was denied. This > > virtual network adapter will be left disconnected." > > > > The documentation says to use an account with read, write, and execute > > permission on the virtual machine configuration file but this does not work. > > This only works if the startup account used is a domain admin. What am I > > missing? How do I make this work using a domain user or host local user > > account? > > > > The fix appears to be simple... for me it was a pain. > > If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. > > The VM start up account MUST have admin provledges on the HOST system. > > > Poof, it works! > > Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com > |
| My System Specs |
|
02-13-2009
| #5 (permalink) |
| | RE: cannot connect virtual network adapter Giving admin rights is NEVER good thing. Specially when you only do it to go around issue like this. Just like it isn't wise to tell your account dept the administrator password, just because they might like to have it. in this case the guest account was given rights to the virtual machine file but not to the virtual network configuration (VNC). Giving read&execute rights on the file will solve the issue without the need to open all possible doors. "Brad Rosse" wrote: Quote: > Quote: > > Virtual Server 2005 R2 > > > > When a virtual machine is configured with the "Always automatically turn on > > virtual machine" option the NIC of that virtual machine reports "network > > cable unplugged". If the virtual machine is then reconfigured to the default > > "Never automatically turn on virtual machine" the NIC works fine. > > > > The event log massage is... > > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > > because either the virtual network is invalid or access was denied. This > > virtual network adapter will be left disconnected." > > > > The documentation says to use an account with read, write, and execute > > permission on the virtual machine configuration file but this does not work. > > This only works if the startup account used is a domain admin. What am I > > missing? How do I make this work using a domain user or host local user > > account? > > > > The fix appears to be simple... for me it was a pain. > > If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. > > The VM start up account MUST have admin provledges on the HOST system. > > > Poof, it works! > > Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com > |
| My System Specs |
|
02-13-2009
| #6 (permalink) |
| | RE: cannot connect virtual network adapter Giving administrator rights is NEVER a fix! and in this case surely isn't needed AND you MUST NOT give such powers out when not needed. In this case, the user just forgot to give read&execute rights on the Virtual Network Configuration (VNC) file. "Brad Rosse" wrote: Quote: > Quote: > > Virtual Server 2005 R2 > > > > When a virtual machine is configured with the "Always automatically turn on > > virtual machine" option the NIC of that virtual machine reports "network > > cable unplugged". If the virtual machine is then reconfigured to the default > > "Never automatically turn on virtual machine" the NIC works fine. > > > > The event log massage is... > > "The virtual machine "machine_name" cannot connect virtual network adapter 1 > > because either the virtual network is invalid or access was denied. This > > virtual network adapter will be left disconnected." > > > > The documentation says to use an account with read, write, and execute > > permission on the virtual machine configuration file but this does not work. > > This only works if the startup account used is a domain admin. What am I > > missing? How do I make this work using a domain user or host local user > > account? > > > > The fix appears to be simple... for me it was a pain. > > If you setup the VM to start automatically like I did, I used an acccount to start the VM with. The Account MUST be a local administrator on the the HOST system. If not, you will get network unplugged, because the VM start up actions are running the VM under an account that does not have privledges for the host. > > The VM start up account MUST have admin provledges on the HOST system. > > > Poof, it works! > > Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Virtual PC cannot share network adapter when VPN is connected | Virtual PC | |||
| Managing network adapter availability for virtual machines | Virtual PC | |||
| Fails to connect to network on boot, have to reset network adapter | Vista networking & sharing | |||
| Trouble getting Hyper-V Virtual Network to work with second Network Adapter | Virtual Server | |||
| Virtual network adapter disappearing | Virtual Server | |||
