|
Blue Forest http://www.lslnet.com at 20:18 on April 6, 2006
[Updated ]VM have details of the NIC not ping通 FreeBSD Host:winxp
Guest:freebsd
Vmware 5.0
Xwindow not enter, and that the guest pass shorter Senat Internet links to the mainframe of ping
However, the mainframe is not ping通 guest host. . .
I do not care is what opened the FreeBSD? It should not be cause of ping
Note : hardware equipment are good (a few days ago still used, in order to minimize installation, I reloading) |
[Updated ]VM have details of the NIC not ping通 FreeBSD Nobody can answer? |
[Updated ]VM have details of the NIC not ping通 FreeBSD Senat guest use, not of ping guest hosts |
[Updated ]VM have details of the NIC not ping通 FreeBSD I wonder if your network.
I do
VM4.5.2 freebsd ip192.168.160.3
CLIENT 1811-1834 192.168.160.1 public network 10.186.0.124
Senat change |
[Updated ]VM have details of the NIC not ping通 FreeBSD I now use Senat.
HOST:winxp, ip:192.168.0.111
GUEST:FB5.4, ip:192.168.0.12 (not support dhcp)
VM 5.0:vm 8:192.168.0.1 ()
GUEST HOST : This configuration can of ping. GUEST HOST of ping not.
Another way :
HOST:winxp, ip:192.168.0.111
GUEST:FB5.4, ip:192.168.75.128 gateway:192.168.75.2
(Support dhcp)
VM 5.0:vm 8:192.168.0.1, DHCP:192.168.75.2
GUEST HOST : This configuration of ping not. GUEST HOST of ping can, through HOST online.
FB into X-WINDOW not now. No firewall configuration. |
| |