main logo
Subject: Re: [ProLinux] VM XP talking to "outer" Linux machine
Author: Kevin Cully
Posted: 2007/02/28 14:31:10
 
View Entire Thread
New Search


Wouldn't you know it. I disabled the firewall and I can now ping the
host computer.

If I unplug my network cable however, I can no longer ping the host
computer, even though the host and guest machines still retain their IP
address. It's beyond me.

Carl Karsten wrote:
> Kevin Cully wrote:
>> Carl Karsten wrote:
>>> host: linux and MySql
>>> guest: XP and VFP
>> Yes, that's correct.
>>
>>> What is the hostname and IPs of host and guest? (the host will have a bunch -
>>> post the whole ifconfig.)
>> Here's my ifconfig settings:
>> ===================================
>> eth0 Link encap:Ethernet HWaddr 00:A0:D1:5A:76:7F
>> inet addr:192.168.15.125 Bcast:192.168.15.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:203324 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:225811 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:93678657 (89.3 MiB) TX bytes:52389643 (49.9 MiB)
>>
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:2938 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:2938 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:1221142 (1.1 MiB) TX bytes:1221142 (1.1 MiB)
>>
>> vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
>> inet addr:172.16.24.1 Bcast:172.16.24.255 Mask:255.255.255.0
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:271 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>> ===================================
>>
>>> Try to ping the host from a dos window in the guest.
>> I'm currently running in Host-only mode and the IP address of the guest
>> VM is 172.16.24.128.
>>
>> When I try to ping 172.16.24.1, I'm getting "Request timed out."
>
> try ping 192.168.15.125
>
>>> btw - why vmware-server and not player? (the player ui is more responsive, but
>>> server lets you run with no UI, so I can see various reasons for each.)
>> Hm. I thought that only the server was free, but I see that player is
>> free as well. So far the performance isn't too bad though.
>
> apt-get install vmware-player.
>
> the install scripts may magically fix your networking problem.
>
>
>
>
[excessive quoting removed by server]


 
©2007 Kevin Cully
<-- Prior Message New Search Next Message -->