Seems i solved the problem! I found out through the Vmnetconfig utility (in same folder of the player) that VMnet0 was not mapping the correct network interface, so finally can go online through my laptop :)

Therefore for the next presentation I am ready;)

Saimon69

Actually Kalamatee is right here, forget my previous ramblings.

blah..whatever

I suggest you both go and read the vmware documentation since you clearly dont understand what its adapters do.

vmnet0 is its bridged adapter, vmnet1 is a private network only visible to the virtual machines, vmnet8 is a NAT adapter used to SHARE the hosts IP address.

Ok, compared to my vmwaros settings then you should
set your aros network settings via ConfigIP to:

*inside netdb-myhost -file

HOST 192.168.80.211 (doesn't need to be 211 just a free one)
DOMAIN arosnet 192.168.80
NAMESERVER 192.168.1.1 (your router, if this doesn't work try 192.168.80.1)

*Inside Interaces -file

192.168.80.211 UP (for the PCnet.device)

*Inside static-routes -file

DEFAULT GATEWAY 192.168.80.1

* try first to ping between your arosbox and PC or to the router 192.168.1.1

(PS.I remember having some odd thing once. I needed to boot aros twice before the network settings worked right after I had altered them.)

@manu
my vmnet8 has ip address 192.168.80.1

therefore what i need to do?

Saimon69

@Kalamatee

Well my virtual machine history incluides a first attempt to install vmware server and then vmware player becausei was unable to set stuff in the net and thought the player only might solve it, so right now have only the player in my machine and no way to change the ethernet settings...

will try to put 192.168.1.1 again at home when go back after work

Saimon69

@ saimon

Your original settings where correct except for the NAMESERVER. Revert them and correct it to 192.168.1.1
You should NOT be using the addresses VMWare uses for its bridge(s) - nor should you be changing them from their default DHCP configured addresses.

If you still have problems after correcting these settings there are a number of possible reasons.

First I would check in PCITool that you version of vmware is indeed using the pcnet32 NIC and not the intel gigabit NIC. If it is listed as the intel NIC you will need to manually edit your vmware config files for the virtual machine and change it to use pcnet.

Secondly I would check that VMWare is correctly bound to your wireless adapter - in vmware go to Edit -> Virtual Network Editor. Goto the "Host Virtual Network Mapping" tab.

Check the option chosen for VMnet0. It will most likely be set to "Bridged to an automatically chosen adapter". If this is the case you may want to untick "Automatically choosen an available physical network adapter to bridge to VMnet0" on the "Automatic Bridging" tab, and then change the VMnet0 option to explicitly use your wireless adapter.

I will tell you how it works on my PC.

I have only Player installed. If I look at networks, I have VMNet1 and VMNet8.

VMNet8 has the ip range 192.168.2.0/24. VmWAROS VE unpacked and run by the player and the network works fine.

If i look at the configurations inside VmwAROS it points towards VMNet8. So the configuration is (default)

*inside netdb-myhost -file

HOST 192.168.2.211
DOMAIN arosnet 192.168.2
NAMESERVER 192.168.2.1

*Inside Interaces -file

192.168.2.211 UP (for the PCnet.device)

*Inside static-routes -file

DEFAULT GATEWAY 192.168.2.1

Just run IPCONFIG under prefs and set it towards the
net you have specified under VMNet8 (if you have one)

Don't try to ping DNS names at first ping your router for example to see if it starts to work. And try to ping from your PC towards 192.168.2.211 see if it answers.

Quote:

Can you ping 192.168.1.1 from your aros box?