VMware Communities
Mike101
Contributor
Contributor
Jump to solution

How to configure vmware workstation and Suse 10 server as guest OS

Hi, I have installed vmware workstation 6.5 on vista and Suse 10 as guest OS. I keep Suse as default (No any network configuration). I have modified the vmware default gateway as 192.168.2.1 keep same as window default gateway settings. I have also changed to subnet to 192.168.2.0. The IP address is changed to 192.168.2.128. My Vista's IP address is 192.168.2.4 and DNS server is 4.4.4.1 and 4.4.4.2.

I tried to ping from host to guest and guest to host but always got "destination host unreachable" error. It does not matter using host only or NAT mode.

Any Documents available? Any advices? Do I need to configure Suse network.?

THanks,

Ming

Reply
0 Kudos
1 Solution

Accepted Solutions
AWo
Immortal
Immortal
Jump to solution

Host:

Wireless LAN adapter Wireless Network Connection:

IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Ethernet adapter VMware Network Adapter VMnet1:

IPv4 Address. . . . . . . . . . . : 192.168.17.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Ethernet adapter VMware Network Adapter VMnet8:

IPv4 Address. . . . . . . . . . . : 192.168.30.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

For guest infor:

eth0 Link encap:Ethernet HWaddr 00:0c:29:8E:1F:01

inet addr:192.168.30.128 Bcast:192.168.30.255 Mask:255.255.255.0

If the guest IP address is set correct you use VMnet8, not VMnet1. That should work but that is not the "host-only" network. That's what I need the .vmx file for. If this shows that the virtual NIC is configured as "host-only" the guest IP address is wrong. It must be 192.168.17.x in this case.

However...try to ping the IP address, not the name. According to the configuration you posted you should try to ping the 192.168.30.1 from the guest and 192.168.30.128 from the host. Remember that can only work if your guest is configured to use VMnet8 instead of VMnet1. If it is really configured to use VMnet1 you have to change the guest IP as I wrote above.

If the host and the guest have firewalls enabled disable them for testing purposes.

By the way, by default VMware installs a DHCP service for VMnet1 and VMnet8. So if this service ist still running on your host, you can set the guest to DHCP and it gets the correct IP for the appropriate network automatically.

I do not how to open *.vmx in text format. I have noticed that vmnet1 IP address from DOS's side is 192.168.17.1 But on guest side it is set up as 192.168.20.0.

It is a text file. Just open it in an editor and copy-and-paste it or attach the file to your next post.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

Reply
0 Kudos
19 Replies
AWo
Immortal
Immortal
Jump to solution

Welcome to the forums!

If you want the guest to participate in the same IP network as the host you need to use bridged networking. Change the vNIC adapter type from "NAT" or "host-only" to "bridged". By using this mode the guest is its own instance in the network.

"Host-only" is an isolated network where onle guests and the host con communicate together.

When you use "NAT" the host acts as a proxy for the guest. The guest itself doesn't appear on the network and all packets originating from it will appear to come from the hoest instead. You can't reach the guests NAT network IP address from teh outside and if you want to connect to some services (Web for example) you need to reroute incoming packets to the guest.

By the way, even if VMWare takes care about this itself, check that after you configured your VMware networks that the "NAT" (default: VMnet8) and the "host-only" (default: VMnet1) networks do not use the same IP address range as the physical network uses.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

Thanks for your response.

My issue is that I could not make communication between host(Vista) and guest(Suse server 10) ,which means failed to setup network between those two. The error is "Destination host unreachable". It happened on both ways while I tried to ping the IP addresses.

I have tried to use NAT or Hostonly after modified the default gateway, and IP address to match the host IP address. But no luck. Do I need to setup DNS? How do I setup default gateway on guest? How to setup IP address on guest OS? (All my settings correct from my original post?) Do I need to setup anything on Suse's network settings. Assuming I am using hostonly mode.

Any clarification will be greatly appreciated.

Thanks,

Mike10

Reply
0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution

Did you try temporarily disabling the Windows Firewall to test?

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

My issue is that I could not make communication between host(Vista) and guest(Suse server 10) ,which means failed to setup network between those two. The error is "Destination host unreachable". It happened on both ways while I tried to ping the IP addresses.

If your host has a physical connection you can use a bridged vNIC if the guest should communicate to other hosts, as well. But that only works if the physical adapter has an active link!

You also can use "host-only" if the guest don't need to communicate to the outside or you do not have an active physical network connection all the time. But then the guest can only communicate to the host.

I have tried to use NAT or Hostonly after modified the default gateway, and IP address to match the host IP address. But no luck. Do I need to setup DNS? How do I setup default gateway on guest? How to setup IP address on guest OS? (All my settings correct from my original post?) Do I need to setup anything on Suse's network settings. Assuming I am using hostonly mode.

In all configurations you don't need a default gateway as the host and the guest are (should be) always in the same IP network. You also do not need DNS. You can use the IP addresses to ping or connect. Of course DNS is more convenient. For you purpose I wouldn't use DNS (can you add DNS entries to the DNS server?), I would use the "hosts" file which is always queried before DNS. You must use it if you can't add DNS entries to whatever DNS server you use.

Please post "ipconfig /all" (Windows) or "ifconfig -a" (Linux) from host AND guest and screenshots of your virtual network setup, if possible. Maybe you mixed up the default settings a little bit.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Mike101
Contributor
Contributor
Jump to solution

I am using hostonly now and disabled the NAT. I am able to ping from host to guest but not from guest to host.

Here is the host info:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Compuman

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Belkin

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : 802.11n USB Wireless LAN Card

Physical Address. . . . . . . . . : 00-08-54-86-76-D7

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::8d52:5af2:eefb:6012%12(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.2.4(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Wednesday, January 14, 2009 10:12:06 PM

Lease Expires . . . . . . . . . . : Sunday, February 21, 2145 4:55:33 AM

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 4.2.2.2

4.2.2.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet

Physical Address. . . . . . . . . : 00-23-54-1F-C5-36

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

1

Physical Address. . . . . . . . . : 00-50-56-C0-00-01

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::ac5e:c255:c8e5:866%13(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.2.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : isatap.Belkin

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : isatap.{B39FFFF1-AE40-4014-954C-D2D36ED87

5B0}

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 02-00-54-55-4E-01

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

This is Suse info:

eth0 Link encap:Ethernet HWaddr 00:0C:29:8E:1F:01

inet addr:192.168.2.128 Bcast:192.168.2.255 Mask:255.255.255.0

inet6 addr: fe80::20c:29ff:fe8e:1f01/64 scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:15 errors:0 dropped:0 overruns:0 frame:0

TX packets:15 errors:0 dropped:0 overruns:0 frame:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:890 (890.0 b)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:250.0.0

inet6 addr: ::1/128 Scope:Host

UPLOOPBACK RUNNING MTU:16436 Xetric:1

RX packets:812 errors:0 dropped:0 overruns: 0 frame:0

TX packets:812 errors:0 dropped:00 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:70135 (68.4 kb) TX bytes:70135 (38.4 kb)

sito Link encap:IPv6-in-IPV4

NOARP XTU:1480 Xetric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

I cannot copy and paste from guest side and type the info. Please have a look at it to see why can not ping from guest side.

Thanks. Mike10

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

You use the same network address (192.168.2.0) for your wireless and the VMnet1 network. That is wrong. If you try to ping the guest from the host it uses the wireless to send out the packets so they don't reach the virtual guest. Change one of the network addresses to 192.168.3.0 for example.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

I still have one thing not quite clear. Where do you find the host and guest IP address are same: 192.168.2.0? It seems to me the host for vm adapter is 192.168.2.1 and the guest is 192.168.2.128.

They suppose to be in the same subnet.

Please correct me if I am wrong.

Thanks.

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

I still have one thing not quite clear. Where do you find the host and guest IP address are same: 192.168.2.0? It seems to me the host for vm adapter is 192.168.2.1 and the

guest is 192.168.2.128.

I found that by looking at the wireless IP address and the guest one. You wrote that you use "host-only" so the IP network address from the guest should not be the one from the wireless.

They suppose to be in the same subnet.

No. If you use "host-only" only the VMnet1 (if you haven't changed the default) adapter from the host and the guest shluld be in one subnet.

By the way, by default VMware checks the IP address ranges in use and selects not used ranges address ranges for VMnet1 and VMnet8.

Please correct me if I am wrong.

I did. Smiley Wink

Thanks.

You're welcome.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

I am sorry I still not quite sure how to look at the IP addresses. The Host wireless IP address appears which is 192.168.2.4 and the Virtual adapter for host only is 192.168.2.1. For guest OS, I only can find IP address is 192.168.2.128. I did not count the local loop IP address/ adapters. Are those right?

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

I am sorry I still not quite sure how to look at the IP addresses. The Host wireless IP address appears which is 192.168.2.4 and the Virtual adapter for host only is 192.168.2.1. For

guest OS, I only can find IP address is 192.168.2.128. I did not count the local loop IP address/ adapters. Are those right?

You just answered that yourself:

The host wireless has: 192.168.2.4

The host VMnet1 has: 192.168.2.1

The guest has: 192.168.2.128

The mask is: 255.255.255.0

That leads to an IP network address of 192.168.2.0

That means you have three adapter is the same IP subnet of 192.168.2.0!

That is O.K. for the guest adapter and the VMnet1 host adapter as these are in the same network and therefore they must share the sam IP network address. But the wireless is in a different network and MUST have a different subnet address. So you MUST change one of these IP network addresses.

This is basic network and TCP/IP knowledge. You have networks and nodes within networks (just like houses (nodes) in streets (networks) where the streets have names and the houses have numbers). The IP address is a combination of both. The IP network mask tells you which part of the IP address is the network and which is the node. Each network must have its own network address (as each street must have its own name and this should exist only once, otherwise the postman doesn't know which street to go). Each host within a network must have its own node address (like each house in a street must hae its own unique number, otherwise the postman doesn't know where to put the letter in, again). Of course, node numbers must not be unique across the networks (as house numbers must not be unique across streets as the combination of street and number makes an address).

You have three networks, your physical one (incl. the wireless), VMnet1 and VMnet8. Each of these separate networks needs its own network number. To connect different IP networks you need a router between them.

What you actually have is two adapters on the same machine (host) in two separate networks which have the same IP network address. That is not allowed and leads to problems, as you're facing, now.

To keep the explanation easy: the TCP/IP stack sees two adapters (wireless and VMnet1) with the same IP network address. Where should it know which one to use to reach the recipient host?


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Mike101
Contributor
Contributor
Jump to solution

It is helpful to learn all the message above. When I refer to an IP address, I meant that it is a node otherwise it will be a sub net. Now my question is could I put the three or four IP addresses (host, guest and VMnet1 or VMnet8) at same sub net so that will easier to do configuration? I never did router configure before. All those three or four nodes are at same physical machine. If put them at three different sub net, do I need to only configure the wireless router which I have now or need to add other routers - do they have virtual routers?

Thanks.

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

Now my question is could I put the three or four IP addresses (host, guest and VMnet1 or VMnet8) at same sub net so that will easier to do configuration?

No. You need to have three subnets, your physical one, VMnet1 and VMnet8. Each one must have an unique network address.

For example:

physical (wireless): 192.168.2.0

VMnet1: 192.168.20.0

VMnet8: 192.168.30.0

You can set these addresses in the Virtual Network Editor under VMware Workstation for VMnet1 and VMnet8. You can also set which physical adapter the "bridged" virtual network interfaces should use (called VMnet0).

I never did router configure before.

Why do you need a router? What do you want to achieve?

If you want that your guest can communicate with the host and all other systems and the Internet maybe, use bridged networking. That makes the guest a part of the physical network. Following the above example it must receive an IP address of 192.168.2.x. Guest-Host communication is only possible as long as you have a physical active network link.

If you only want to have communication between the guest and the host use VMnet1 (host-only). Following the above example the guest must have an IP address of 192.168.20.x. Because this is a virtual network it will work even without a physical network link.

Combinations of both are possible, but I don't explain that, yet. First let's see what you need.

do they have virtual routers?

No.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

I have tried to seperate the three network according to suggested. My host is vista and my guest is Linux server 10. They are on the same machine. I have set host as static IP address and vmnet1 and vmnet8 as dynamic but sub net is 192.168.20.0 for vmnet1 and 192.168.30.0 for vmnet8.

Some how when I tried to ping from linux to host, I always received message: "network can not be reached". My host IP address is 192.168.2.8 and my vmnet8 is 192.168.30.128. How to make them work together?

Thanks.

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

Post "ipconfig /all" from your host and "ifconfig -a" from the Linux guest and the content of the .vmx file of the guest.

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

Here is my host infor:

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : 802.11n USB Wireless LAN Card

Physical Address. . . . . . . . . : 00-08-54-86-76-D7

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::3d20:b4ef:b9c:22c4%12(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Wednesday, January 21, 2009 8:21:04 PM

Lease Expires . . . . . . . . . . : Sunday, February 28, 2145 5:54:29 AM

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : Belkin

Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet

Physical Address. . . . . . . . . : 00-23-54-1F-C5-36

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

1

Physical Address. . . . . . . . . : 00-50-56-C0-00-01

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::dd84:5011:eef4:f5c0%13(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.17.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet

8

Physical Address. . . . . . . . . : 00-50-56-C0-00-08

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::dd:2594:234c:52e7%14(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.30.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : isatap.Belkin

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:......

For guest infor:

eth0 Link encap:Ethernet HWaddr 00:0c:29:8E:1F:01

inet addr:192.168.30.128 Bcast:192.168.30.255 Mask:255.255.255.0

inet6 addr: fe80:20c:29ff:fe8e:1f01/64 Scope:Link

UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1

RX packets:2303 errors:0 dropped:0 overruns:0 frame:0

TX packets:752 errors:14 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1795124(1.7Mb) TX bytes:157764 (154.0 kb)

Interrup:59 Base address:0x2000......

I do not how to open *.vmx in text format. I have noticed that vmnet1 IP address from DOS's side is 192.168.17.1 But on guest side it is set up as 192.168.20.0.

Thanks.

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

Host:

Wireless LAN adapter Wireless Network Connection:

IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Ethernet adapter VMware Network Adapter VMnet1:

IPv4 Address. . . . . . . . . . . : 192.168.17.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Ethernet adapter VMware Network Adapter VMnet8:

IPv4 Address. . . . . . . . . . . : 192.168.30.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

For guest infor:

eth0 Link encap:Ethernet HWaddr 00:0c:29:8E:1F:01

inet addr:192.168.30.128 Bcast:192.168.30.255 Mask:255.255.255.0

If the guest IP address is set correct you use VMnet8, not VMnet1. That should work but that is not the "host-only" network. That's what I need the .vmx file for. If this shows that the virtual NIC is configured as "host-only" the guest IP address is wrong. It must be 192.168.17.x in this case.

However...try to ping the IP address, not the name. According to the configuration you posted you should try to ping the 192.168.30.1 from the guest and 192.168.30.128 from the host. Remember that can only work if your guest is configured to use VMnet8 instead of VMnet1. If it is really configured to use VMnet1 you have to change the guest IP as I wrote above.

If the host and the guest have firewalls enabled disable them for testing purposes.

By the way, by default VMware installs a DHCP service for VMnet1 and VMnet8. So if this service ist still running on your host, you can set the guest to DHCP and it gets the correct IP for the appropriate network automatically.

I do not how to open *.vmx in text format. I have noticed that vmnet1 IP address from DOS's side is 192.168.17.1 But on guest side it is set up as 192.168.20.0.

It is a text file. Just open it in an editor and copy-and-paste it or attach the file to your next post.


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

Yes, ping from both side works. I did not know I need to use the 192.168.30.1 for host. I thought I need to use 192.168.2.2 as host IP address. Also I need to turn off both host and guest's fire wall.

Thanks a lot.

Reply
0 Kudos
Mike101
Contributor
Contributor
Jump to solution

You are right. but I do not know how to assign points to you. I did not see help button there. Sorry about it.

Reply
0 Kudos
AWo
Immortal
Immortal
Jump to solution

Some reading which help you in the future:

http://en.wikipedia.org/wiki/Internet_Protocol

http://en.wikipedia.org/wiki/TCP/IP_model

http://www.windowsnetworking.com/articles_tutorials/tcpip.html

http://www.tech-pro.net/intro_tcp.html


If you found this information useful, please consider awarding points for "Correct" or "Helpful" answers/replies. Thanks!!

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
Reply
0 Kudos