Hallo Arlekino,
erste Frage vorweg, musst Du mit NAT arbeiten?
Zweite Frage,
wenn alles wirklich so eingestellt ist, wie von Dir angegeben ist, sind alle Maschinen mittels den physischen und der BRIDGED Netzwerkkarte der virtuellen Maschine untereinanader erreichbar, da sie sich im gleichen Netz befinden. Also prüfe das bitte nochmal. Die Verbindung muss stehen.
Wenn Du mit NAT arbeiten willst, folgenden Hinweis:
NAT verwendet VMnet 8 für das Sharing der Host-IP Adresse. Im Virtuell Network Manager kannst Du nachsehen, welche IP-Range für NAT verwendet wird. Dafür vergibt VMware auch die entsprechenden IP-Adressen automatisch.
Aber merke, NAT funktioniert zwischen Host und Guest, da dafür entsprechende Mechanismen (virtuelle Netze) vorhanden sind.
Deine andere Maschine hat nur eine physische Netzwerkkarte. Sie hat keine weitere Netzwerkkarte, die in die IP-Range verbunden ist, die in das (virtuelle) Netzwerk zeigt, in dem NAT auf dem Host und zwischen dem Gast läuft.
Das NAT Gateway ist im übrigen daher eine höhere IP-Adresse als die NAT-Adresse des Hosts. Daher kommst Du nicht in das virtuelle NAT-Netzwerk auf dem Host hinein.
Und daher geht das nicht.
Die von mir beschriebenen Einstellungen kannst Du im Virtuell Network Manager nachvollziehen, einfach mal ein Blatt Papier nehmen und die NEtze aufzeichnen, dann wird es deutlich.
Also mache es mit Bridged Netzwerkkarten, dann geht das.
Zur Info hier noch 2 Artikel von VMware:
http://www.vmware.com/support/ws45/doc/ ... ml#1061809
....If you use NAT, your virtual machine does not have its own IP address on the external network. Instead, a separate private network is set up on the host computer. Your virtual machine gets an address on that network from the VMware virtual DHCP server. The VMware NAT device passes network data between one or more virtual machines and the external network. It identifies incoming data packets intended for each virtual machine and sends them to the correct destination.
If you select NAT, the virtual machine can use many standard TCP/IP protocols to connect to other machines on the external network. For example, you can use HTTP to browse Web sites, FTP to transfer files and Telnet to log on to other computers. In the default configuration, computers on the external network cannot initiate connections to the virtual machine. That means, for example, that the default configuration does not let you use the virtual machine as a Web server to send Web pages to computers on the external network...
http://www.vmware.com/support/ws45/doc/ ... ml#1061951
...Selecting IP Addresses on a Host-Only Network or NAT Configuration
A host-only network uses a private virtual network. The host and all virtual machines configured for host-only networking are connected to the network through a virtual switch. Typically all the parties on this private network use the TCP/IP protocol suite, although other communication protocols may be used.
A network address translation (NAT) configuration also sets up a private network, which must be a TCP/IP network. The virtual machines configured for NAT are connected to that network through a virtual switch. The host computer is also connected to the private network used for NAT via a host virtual adapter.
Each virtual machine and the host must be assigned addresses on the private network. This is typically done using the DHCP server that comes with VMware Workstation. Note that this server does not service virtual (or physical) machines residing on bridged networks.
Addresses can also be assigned statically from a pool of addresses that are not assigned by the DHCP server.
When host-only networking is enabled at the time VMware Workstation is installed, the network number to use for the virtual network is automatically selected as an unused private IP network number. To find out what network is used on a Windows host, choose Edit > Virtual Network Settings and check the subnet number associated with the virtual network. On a Linux host, run ifconfig in a terminal.
A NAT configuration also uses an unused private network automatically selected when you install VMware Workstation. To find out what network is used on a Windows host, choose Edit > Virtual Network Settings and check the subnet number associated with the virtual network. On a Linux host, run ifconfig in a terminal.
Using DHCP to assign IP addresses is simpler and more automatic than statically assigning them. Most Windows operating systems, for example, come preconfigured to use DHCP at boot time, so Windows virtual machines can connect to the network the first time they are booted, without additional configuration. If you want your virtual machines to communicate with each other using names instead of IP addresses, however, you must set up a naming convention, a name server on the private network, or both. In that case it may be simpler to use static IP addresses.
In general, if you have virtual machines you intend to use frequently or for extended periods of time, it is probably most convenient to assign them static IP addresses or configure the VMware DHCP server to always assign the same IP address to each of these virtual machines.
Configuring the DHCP Server on a Linux Host
On a Linux host, you configure the host-only DHCP server by editing the DHCP configuration file for VMnet1 (/etc/vmware/vmnet1/dhcp/dhcp.conf). To configure the DHCP server for the NAT network, edit the configuration file for VMnet8 (/etc/vmware/vmnet8/dhcp/dhcp.conf).
Editing the DHCP server configuration file requires information that is best obtained directly from the DHCP server documentation. Consult the manual pages dhcpd ( 8 ) and dhcpd.conf ( 8 )....
Hartmut Schaumburg
