I have a test environment with WinXP SP2 as the guest OS and various OSs (depending on my needs) hosted within VM Ware Infrastructure 2.0. I've noticed that two linux machines have networking problems:
RedHat Fedora 9 64 bit machine
Initially an IP address was allocated correctly through the router, however, upon rebooting a couple of times an IP4 ip address is not even available (see guestVM.JPG). Initially I could ping local addresses but when connecting to an ftp server on the local network an error message was being displayed indicating some routing problem.
On the RHS bottom the icon (see guestVM.JPG) displaying 'Connected to Bridged network on Server' seems unusual, what does this mean? I've found no options to install VMWare Tools; I'm aware I had problems finding the correct version of VMWare tools for certain UX flavors when I used VMWare Workstation 6; and, I'm not sure whether this is already installed on my VM.
I tried changing the network type from bridged to host only, and this enabled the host machine to have an IP4 network address, but there is no connection (e.g. ping) between the host and other points on the network (i.e. router @ 192.168.2.1, guest machine @ 192.168.2.201 which also has an ftp server, which is running successfully). Pinging from guest to this machine is fine, but not pinging from the machine to the guest.
Ubuntu 8.10 Server machine
The only interface that is loaded is the local host. eth0 fails to load upon startup and when running manual commands. Initially, I've resolved the networking issue by configuring the network interface on the host machine; however the IP address is not always retrieved when rebooting the virtual machine using ux commands. (see http://ubuntuforums.org/showthread.php?p=6293000#post6293000).
An IPv4 address is not being assigned, hence, there is no network connection to the virtual machine when the machine is reset (power off, then start up); An IPv4 address is not allocated to the machine (intermittently) upon booting up or reboot.
+Last resolution+s
Whilst in Bridge mode, a network interface eth2:avahi with an IPv4 address starting with 169.x.x.x.x, shows up, and when I take it down eth2 has an IPv4 network address (allocated by the router @ 192.168.2.1), but, I get 'destination host unreachable' errors when pinging.
Whilst in Bridge mode, I restarted the eth2 network interface, and network connection was available to the internal network but not to the Internet (foreign stream). This implies some issue with the router itself, although a software incompatibility issue with VMWare Server is not excluded.
WinXP SP3 machine
IP initially attained by the machine was 169.x.x.x. Tried to update a static IP address myself to no avail. Routing does not pass through my router (when doing traceroute). Updating network card to retrieve IP address automatically leaves the machine with zero values for IP address and Subnet mask. DHCP server value is: 255.255.255.255; I did not update any DHCP server values afaik.
pinging does not work both ways, i.e. both from guest to host and
vice versa. Pinging router from 192.168.117.129 (host) > 192.168.2.1
fails. Ftp connetion to guest fails with an "unknown error". Strangely
enough UNC paths to the guest machine are successfully working,
although I cannot run commands over the network; copying of folders
across the network is successful.
Network connection in bridged mode.
Attachments:
guestVM.JPG - screenshot of RedHat machine
host-ipconfig.txt - ip configuration on host (WinXP x64)
Note: There seems to be some limitation in uploading more attachments.
Similar issues have been reported to occur in the past, presumably for VMWare Server 1.0 (http://communities.vmware.com/docs/DOC-7680), and at the time the user was claiming that it was a software bug. On the other hand, Since I sorted out one of the issues (Ubuntu machine) through a
configuration within the client, this could be a problem from the machines themselves.
Your help in sorting out this issue would be appreciated.
Message was edited by: jon80
RedHat Fedora 9 64 bit machine
Initially an IP address was allocated correctly through the router, however, upon rebooting a couple of times an IP4 ip address is not even available (see guestVM.JPG). Initially I could ping local addresses but when connecting to an ftp server on the local network an error message was being displayed indicating some routing problem.
On the RHS bottom the icon (see guestVM.JPG) displaying 'Connected to Bridged network on Server' seems unusual, what does this mean? I've found no options to install VMWare Tools; I'm aware I had problems finding the correct version of VMWare tools for certain UX flavors when I used VMWare Workstation 6; and, I'm not sure whether this is already installed on my VM.
I tried changing the network type from bridged to host only, and this enabled the host machine to have an IP4 network address, but there is no connection (e.g. ping) between the host and other points on the network (i.e. router @ 192.168.2.1, guest machine @ 192.168.2.201 which also has an ftp server, which is running successfully). Pinging from guest to this machine is fine, but not pinging from the machine to the guest.
Ubuntu 8.10 Server machine
The only interface that is loaded is the local host. eth0 fails to load upon startup and when running manual commands. Initially, I've resolved the networking issue by configuring the network interface on the host machine; however the IP address is not always retrieved when rebooting the virtual machine using ux commands. (see http://ubuntuforums.org/showthread.php?p=6293000#post6293000).
An IPv4 address is not being assigned, hence, there is no network connection to the virtual machine when the machine is reset (power off, then start up); An IPv4 address is not allocated to the machine (intermittently) upon booting up or reboot.
+Last resolution+s
Whilst in Bridge mode, a network interface eth2:avahi with an IPv4 address starting with 169.x.x.x.x, shows up, and when I take it down eth2 has an IPv4 network address (allocated by the router @ 192.168.2.1), but, I get 'destination host unreachable' errors when pinging.
Whilst in Bridge mode, I restarted the eth2 network interface, and network connection was available to the internal network but not to the Internet (foreign stream). This implies some issue with the router itself, although a software incompatibility issue with VMWare Server is not excluded.
WinXP SP3 machine
IP initially attained by the machine was 169.x.x.x. Tried to update a static IP address myself to no avail. Routing does not pass through my router (when doing traceroute). Updating network card to retrieve IP address automatically leaves the machine with zero values for IP address and Subnet mask. DHCP server value is: 255.255.255.255; I did not update any DHCP server values afaik.
pinging does not work both ways, i.e. both from guest to host and
vice versa. Pinging router from 192.168.117.129 (host) > 192.168.2.1
fails. Ftp connetion to guest fails with an "unknown error". Strangely
enough UNC paths to the guest machine are successfully working,
although I cannot run commands over the network; copying of folders
across the network is successful.
Network connection in bridged mode.
Attachments:
guestVM.JPG - screenshot of RedHat machine
host-ipconfig.txt - ip configuration on host (WinXP x64)
Note: There seems to be some limitation in uploading more attachments.
Similar issues have been reported to occur in the past, presumably for VMWare Server 1.0 (http://communities.vmware.com/docs/DOC-7680), and at the time the user was claiming that it was a software bug. On the other hand, Since I sorted out one of the issues (Ubuntu machine) through a
configuration within the client, this could be a problem from the machines themselves.
Your help in sorting out this issue would be appreciated.
Message was edited by: jon80
Attachments:
- host-ipconfig.txt (2.2 K)
-
guestVM.JPG (171.8 K)
