This indicates your linux vm's eth0 isn't setup correctly. Do ifconfig -a and see if 192.168.164.229 if binded to eth0 and see if eth0 is up.
I assume eth0 is configured in vmnet8, eth1 is configured in vmnet1.
Regards,
Shan Jing
Unix Group - Americas
Deutsche Bank
2 Gatehall Drive, 3rd Floor
Parsippany, New Jersey, USA
shan.jing@xxxxxx
973.682.3463
"Abiezer Matos
Reyes (Ext.2413)" To: <shrike-list@xxxxxxxxxx>
<a.matos@servicob cc: <shrike-list-admin@xxxxxxxxxx>
ros.com> Subject: RE: Conet to inernet via vmware
Sent by:
shrike-list-admin
@redhat.com
11/12/03 04:08 PM
Please respond to
shrike-list
Hey, I do all you said, now I can try to attempt it's relly work...
In my xp host I tried to ping mi vm linux virtual machine(excusme mi
ignorance, I'm a programmer not a lan-manager :)):
C:\>ping 192.168.164.229
Pinging 192.168.164.229 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.164.229:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
So, you are exelent teacher... What is the next step??
Thank u a lot.
-----Original Message-----
From: Shan Jing [mailto:shan.jing@xxxxxx]
Sent: Wednesday, November 12, 2003 4:12 PM
To: shrike-list@xxxxxxxxxx
Cc: shrike-list@xxxxxxxxxx; shrike-list-admin@xxxxxxxxxx
Subject: RE: Conet to inernet via vmware
vmnet8 is NAT network
vmnet1 is host-only network.
vmnet8's gateway will lead vm linux machine to the outside world.
In your case, you need to check your vm linux's ip and default gateway.
I would do the following:
0. verify linux vm's eth0, make sure it got ip from vmnet8's dhcp. For
redhat linux, you normally have trouble getting it automatically (don't
know why), you will need to manually " ifconfig eth0 192.168.154.229
netmask 255.255.255.0 up" 1. in the vm linux machine, add 192.168.154.1
as default gateway; 2. in window XP command prompt, find out your dns
server's ip ("nslookup" will show); 3. in the vm linux machine, ping the
outside dns server (the server's ip you got from xp's nslookup ); 4. if
linux vm's ip and gateway are correct, you should be able to ping the
outside world's dns server.
Regards,
Shan Jing
Unix Group - Americas
Deutsche Bank
2 Gatehall Drive, 3rd Floor
Parsippany, New Jersey, USA
shan.jing@xxxxxx
973.682.3463
"Abiezer Matos
Reyes (Ext.2413)" To:
<shrike-list@xxxxxxxxxx>
<a.matos@servicob cc:
<shrike-list-admin@xxxxxxxxxx>
ros.com> Subject: RE: Conet to
inernet via vmware
Sent by:
shrike-list-admin
@redhat.com
11/11/2003 09:30
AM
Please respond to
shrike-list
8 fails, there's my ipconfig in xp host... What can I do now. (thanks
for all the info, I appreciate)
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.154.
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.26.1
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : phlegal.com
IP Address. . . . . . . . . . . . : 172.16.0.240
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.16.0.254
-----Original Message-----
From: Shan Jing [mailto:shan.jing@xxxxxx]
Sent: Friday, November 07, 2003 8:34 PM
To: shrike-list@xxxxxxxxxx
Cc: shrike-list@xxxxxxxxxx; shrike-list-admin@xxxxxxxxxx
Subject: Re: Conet to inernet via vmware
If your virtual machine running Linux 9 isn't connecting to the
Internet, please try the following:
1. In vmware, set the linux 9 virtual machine's NIC to NAT;
2. boot the linux 9 virtual machine;
3. For redhat linux 9, run redhat-config-network and set eth0 to dhcp;
4. restart network service - /etc/init.d/network stop ,
/etc/init.d/network start
5. check to see if eth0 gets an IP, should be one from dhcp subnet in
vmare
6. For redhat linux, most vm machine dhcp client will fail, I don't know
why. (anyone knows?) If your vm's eth0 didn't get IP, you need to
manually config one for eth0, make sure it's in the same subnet. After a
manual configure, you need to bounce the network service again.
7. verify routing table, netstat -nr, make sure default route points to
x.x.x.1 where x.x.x is dhcp subnet
8. do nslookup or dig, see if you can resolve anything, eg www.yahoo.com
9. if 8 fails, manually enter dns server in /etc/resolv.conf, you should
get an dns server from window XP's nslookup, use the same.
Regards,
Shan Jing
Unix Group - Americas
Deutsche Bank
2 Gatehall Drive, 3rd Floor
Parsippany, New Jersey, USA
shan.jing@xxxxxx
973.682.3463
"John Meagher"
<jmeagher@patriot To:
<shrike-list@xxxxxxxxxx>
.net> cc:
Sent by: Subject: Re: Conet to
inernet via vmware
shrike-list-admin
@redhat.com
11/06/2003 09:16
PM
Please respond to
shrike-list
----- Original Message -----
From: "Abiezer Matos Reyes (Ext.2413)" <a.matos@xxxxxxxxxxxxxxx>
> Excuseme, I don't understand very well, I speak Spanish :)
> I don't connect with my host xp from my virtual machine Linux 9.0
yet...
> I'm rookie in a Linux world, please some body speak spanish in the
list?
> Or other better explanation?
You're doing fine. The message you replied to wasn't in English. I
couldn't understand it either. But if you're not using vmware you
should change the subject to match your problem. Do you need a linux
client to talk to a windows network? Take a look at man smbclient.
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
--
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
