Are you able to create a new guest on this Datastore?
Tried to remove the datastore and add it again.
Did the guest have had a regular shutdown? Or are there stale lockfiles?
Yes, the guest was properly shutdown.
And no, the datastore is not accessible neither, like the VM. However, it's already there, and I have to remove and the datastore and the VM, then add the datastore again to be able to add virtual machine from this repository. The behaviour is the same without start/stop the VM at all.
But I don't want do such thing every time I bounce the host, do I ?
You did not write about your host.
What kind of OS? Windows or Linux?
Are you sure, that the NAS (Share as Drive or connected as UNC?) is connected before VMware Server is started?
Any chance to connect the NAS with NFS instead of CIFS?
Thanks for replying.
My host OS is Windows XP SP2. The NAS is connected as well before the VM Server is started, yes.
I tried to share a directory as drive, and mount on my host (network drive), but VMWare doesn't want to create a datastore to this directory like that. Only within the CIFS settings.
Did you created your VMs with UNC names like
NAS\share\...? And are your services running with user credentials? This should work. A process with system credentials can only connect to nul session shares or the process have to connect within a batch file with 'net use
NAS\share password /user:user'.
Ok I have the same problem (listed with other issues on http://communities.vmware.com/message/887249)
Always have to remove and reisnert my vms. Casue my Server is mostly up it doesn't disturb for most times, though it's somehow anoying.
Did someone find a solution to this problem?
I narrowed it down to a single problem sniffing my network with Ethereal.
1) my first problem: on normal datastore creation it didn't do that, but on computer-restart it sends "NetrShareGetInfo request
File-share-IP, foldername" to my Fileshare computer and got back "NetrShareGetInfo response ACCESS Denied". And here it stopped. I noticed that from my VMWare computer from normal explorer I could connect to
File-share-IP\foldername, but I couldn't connect to
File-share-IP directly to see what shares are provided. I never tried this, because there are only a few shares I accessed directly. And I didn't know that VMWare is complaining about this. I could set up some directions using gpedit.msc, but as I'm behind a Router and NAT I didn't mind setting instead HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\RestrictAnonymous to 0 on the computer holding the datastore. So Anonymous Access isn't restricted anymore. On my other computer it wasn't restricted anyway. Perhaps it has to do with this oem-version (the datastore-computer has oem-version, the vmware-computer has no oem-version of windows) or I changed it myself because of a "good tip" somewhere before I set up a home network. Nevertheless this brought me a step closer to the solution. Now the "NetrShareGetInfo request" works and VMWare server goes a step further.
2) The second problem: If I enter CIFS, I enter host, computer, username, password. After this a connection to //File-share-IP/IPC$ is established //File-share-IP/IPC$ -connection seems to work without special password. (The NTLMSSP_AUT within session negotiation has no user/password in it) Then a new session with //File-share-IP/filefolder is established (here NTLMSSP_AUT-value contains the username and something which looks like a scrambled pwd.) when I reboot the machine there is only one session connection (without credentials!) and it connects at first to //File-share-IP/IPC$ and then to //File-share-IP/filefolder.
//File-share-IP/filefolder doesn't like having no credentials and so it refuses.
I think there is somehow a problem, I haven't seen the datastoreuser/password in any of the vmware-config files (ok seeing the password somewhere would be a security issue). And I think this is the problem why (on restart) it doesn't send any datastoreuser/password and so it refuses. Is this normal? Is no one except we two experiencing these problems. Is it an WinXP Prof SP2 Problem? Or is it normal that VMWare doesn't use a user/password to access the remote-directory on reboot? Any solutions?
1 person found this helpful
have you tried to run the "VMware Host Agent" service with user credentials? This should be the service, that is starting the VMs after power on. May be the "VMware Virtual Infrastructure Web Access" service should also start with user credentials. You have to take care, that this user has enough rights on the local system. Administrator should be enough.
C'mon folks, let's see what the Beta 2 will bring up. It should be available this evening.
Woh quite fast answer!
the problem I had, where I had to set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\RestrictAnonymous to 0 seems to get some overall information like space of datastore. If I let this at a value of 1 it can't get the datstore size and so it displays some funny numbers of some petabyte or something like that. So I have to set this too (or change my local rules in gpedit.msc).
Back to my main problem:
Yeah it did read your previous post and so I start "VMWare Host agent"
now with user rights (instead of local rights) after my post. Now it works, the
smb-session between the two computers is negotiated and connection to
IPC$ and to my folder works with this user. Everything works fine, but one thing I'm still asking. In CIFS-dialog of datastore-add I enter datastore-computer, datastore-folder, datastore-localuseraccount, datastore-userpasswd and my vmware server logs in to my datastore computer with datastore-localuseraccount and datastore-userpasswd, and everything works fine. After restart of my server computer it seems to use the local service user (which doesn't seem to work) or the local vmwareserver-user to which I changed (which works). But it doesn't use the datstore-localuseraccount any more. Why did I have to enter it if it only uses it once? It could be well an issue because it is a datastore-localuser, but I haven't seen anything complaining about this while sniffing. So I think it is an VMWare related bug.
Nevertheless and no matter if it connects through datastoreuser or vmware-local user with admin permissions, it works :D. Thanks for the tip with the user.
Funny things are happening!
If you want to use the plugin directly you also have to start "VMware Authorization Service" with the same administrative user. Normally I use ssh and vnc, and so this wouldn't be a big problem for me (except if ssh and vnc don't work for any reason)
Otherwise you get an error saying wrong user/password. (even though everything else works)