You need to add the VMWare tools nic driver to the winPE image.

You can add drivers using this article from MS. http://technet.microsoft.com/en-us/library/cc74935...

The VMTools drivers can be found @ http://www.vmware.com/download/ search for vmware tools download.

Hi, thanks for the answer.
I add the drivers with the PXE cinfugration utility. I also looked at the mounted boot.wim with waik tool. There i can find the network driver from my vmware tools.

If i use ipconfig -all it looks like, winpe installed the drivers. But something issn't correct. The WinPE didn't get a IP adress from my dhcp and i can't renew or release the adress.

Please take a look on the following picture. I hope it will uploaded correctly.

Can you ping the gateway, can you ping the DS server? Is F:\ being mapped to the server? What vmnetwork are you on? Is it connected to or able to route to the DS server/subnet?

Hi. Actually my vmware is down. But i have a screenshoot from yesterday. Please take look.

Here you can see ipconfig -renew and release. Normaly the IP-Range for the VMWare is 10.1.1.11 - 10.1.1.254. VMWare Server is version 1.0.6...
If my Vmware Server is up again, i will test what you has tell me.

Hi again. The VMWare-server is up and running again.
Here are the results of my tests:

On the first picture you see results of:
f: share issnt mapped / g: issnt mapped. Net use doesn't work.
My gateway have the IP 10.1.1.1 and you see, that i cannot ping him.

Tracert also doesn't work.

My deploymentshare have the IP 10.1.1.5 and you see that i cannot ping him.

Hello.
Are there enyone who have a idea what i can do?
Its really crazy. I found a second problem in my network. In the PXE bootup, sometimes the clients getting the correct IP adress 10.1.1.x and sometimes the clients getting a adress from 192.168.238.x.
In my vmware i configured all clients with Host only.

System error 1231 has occurred. The network location cannot be reached.

Symptom: When using net view \\computername, you may receive System error 1231.

Resolutions:
1) Make sure Client for MS Networks is enabled
2) Make sure you have permission to access it.

Ref: http://www.chicagotech.nethttp://www.chicagotech.n...

-----

Hmm.. Cheap & nasty site at least on that page eh?! Like it says though check the account you are linking to it has permissions when setting/resetting up the mappings.

You could also check on the deployment console itself (rdp) and do this;
Start > Programs > Altiris > Deployment Solution > Configuration

Then from there
Options > Drive Mappings

And add the same mappings into there. I've been advised to do this before and it (with any chance) might help you out. If not it might inspire someone else with an idea/solution.

It could be the winpe firewall is enabled. if you created the winpe image with Boot Disk Creator make sure the firewall option is unchecked.

When you add ethernet0.virtualDev="e1000" to your vm make sure VMware is not running. I did not have to use the vmware tools for this to work and have done this in VM worstation, ESX and ESXi.

nelo

I found the mistake in my environment.
It was the vmwareserver. On my vmware-server were 3 dhcp servers are running. I disabled the two who are unused and now my clients are getting the right ip-adress.

Thanks for everyone.