The basic conversion process worked fine and also the reconfiguration, except that if we checked the checkbox to change the identity of the clone (I can't remember the exact wording here) we were required to get some extra software stuff from the Internet, so we skipped that part.
(Now after the fact I have searched "everywhere" for information on exactly which tools we were supposed to download, but could not find it mentioned anywhere. Seems like the only place it is mentioned is inside the reconfiguration program when you are half way through...

Anyway, after we finished and tried starting the created VM in Player we had to supply an activation key (of course, since the hardware had changed so much). Then it started up like on the laptop.

But after looking around we noted that the guest had no less than 3 network adapters, none of which worked...

Ipconfig /all revealed that they all had fixed IP addresses in the 192.168.x.x ranges (all on different subnets).

It is impossible to ping guest-host or host-guest, we get either "host unreachable" or timeouts. I believe we got timeouts after we changed the loopback adapter on the host to be in the same subnet as one of the guest NIC:s. Changing the network type between Bridged/NAT/Host on each of the three NIC:s in the guest changes nothing either.

This makes no sense to me at all because I am running several guests in VMWare WS 6 with no issues at all.

Is there a limitation in Player that blocks the network access?
We tried Player because my collegue does not have a WorkStation license and the guest files are massive (40 Gb) so I don't want to bring it over to my PC just for testing, either.

What could we do to rectify this situation? Either in the (limited) menus of Player or directly editing the vmx file?

/Bo