Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not sure if this post belongs here, but here it is. This is a dedicated win 2003.
Host: Win server 2003
Guest: Ubuntu server
Host: IS able to ping guest. Firewall is OFF. NOT able to access guest (which is a web-server) at browser.
Guest: NOT able to ping host. Running a web server, you can check the website: (pegajosa.com) is running under that virtual linux server.
Problem: guest needs to access host's sql database and/or any resources.
The guest's address, as specified, is not in the subnet of either vmnet virtual adapter that you have specified. From what I see, it looks like you have specified the external IP address of the client system, which presumably is how it is accessed from outside. I do know that if I enter that IP in a browser I do get to a site, presumably yours.
I presume you are doing forwarding somehow (I don't know how it is done in Windows Server) to forward from the external address to the internal guest address.
Alternatively, you have defined the guest as having the specified external address, in which case it is not part of a subnet with the host, and this is why you can't connect with the host. If this is the case, you need to set up the routing table on the guest system properly.
You also haven't specified the version of VMWare. I think that the default configuration of VMWare has vmnet0 as bridged, vmnet1 as host-only, and vmnet8 as NAT.
You apparently don't have a vmnet0, and have not provided enough information to identify whether vmnet1 and vmnet8 are as defined by default.
From the information you have provided, I can't tell a thing.
I need to see ifconfig -a for the Linux client, and the complete routing tables for both the host and the client.
jiml8, thanks for trying to help me. below is the information you requested, let me know if you need more information.
I don't think I'm doing forwarding. This win server has various IPs assign to it. This is a dedicated server. I took one of the IPs .163 from the available IP list this host provider assigned.
1. Version of VMware:
VMware Infrastructure Web Access
VMware Server
Version 2.0.0
Build 128374
2. You are right I only have vmnet1 and vmnet8.
3. How do I find out your question: "have not provided enough information to identify whether vmnet1 and vmnet8 are as defined by default."
4. Do I need a vmnet0?
you should put the information in code tags so that it will be spaced properly. Much easier to read.
I was right. Your Linux guest has no route to find the Windows host, and you have directly assigned it an internet-facing address.
Your guest is only showing one interface, and that interface is directly facing the internet. With that configuration, I don't think you will be able to get your guest to see the host at all since the host is on a 192.168 subnet which is non-routable.
Your choices, I think, are to use the VMWare networking setup to bind an additional virtual network adapter into your linux guest, then route to the host through that. VMWare Server 2.0 supports up to 10 virtual network connections per virtual machine.
Alternatively, you may reconfigure your network so that your guest system has a 192.168 address. It then will be able to see the host since it is on the same subnet, and you can use the host's facilities to masquerade the internal 192.168 guest address to the desired external 208.85 address. This is certainly possible using Windows Server and, if I was sitting in front of the computer I am sure I could figure it out, but from here I can't tell you because it has been a decade since I've used Windows Server.
I think the simpler choice is to add the new virtual network adapter to the guest and assign it a 192.168 address. The guest's network setup should then handle all the details, and if it doesn't, one new line in the routing table would be all you'd need. The VMWare networking wizard will take you right through all the setup stuff for the additional network adapter.
I think the simpler choice is to add the new virtual network adapter to the guest and assign it a 192.168 address. The guest's network setup should then handle all the details, and if it doesn't, one new line in the routing table would be all you'd need. The VMWare networking wizard will take you right through all the setup stuff for the additional network adapter.
i tried assigning the new virtual adapter: eth1 (i created this as bridge).
i made it 192.168.240.1 / 255.255.255.0
i follow these instructions: http://en.kioskea.net/faq/979-having...er-ubuntu-8-10
after restarting the network, i got disconnected and everything went down: website, ssh, vmware console.
i had to revert to a snapshot.
maybe i'm doing something wrong, can you assist? thanks..
You have nothing to bridge to. you don't want to add a bridge; you want to add a host-only network adapter. You won't want to assign it as 192.168.240.1 (though you could...) because that normally would be the gateway address, and VMWare will most probably assign it to the vmnet# virtual adapter that it creates in the host machine.
The description in the first link you provided tells you what is happening. VMWare sets up a virtual switch. Think of it as being a physical box, and your host as one physical computer and your guest as another physical computer. In this case, you need two cables: one from the guest to the switch and the other from the host to the switch. Thus, you obviously need two addresses: one for the host and one for the guest.
Of course, the host and the guest and the switch aren't in distinct physical boxes, so all of this is virtual. That it is virtual makes it nonetheless real. You don't need physical cables to hook things together; you need virtual ones - and VMWare will handle that for you unless you over-think it.
So, VMWare will assign a non-routable address to the vmnet# adapter it provides for the host, and you have to tell it to provide another network adapter in the guest, and you have to provide an address on the same subnet for the adapter in the guest.
The point is to put both the host and the client on the same subnet so that they can talk to each other.
Your host configuration already shows a vmnet1 (which VMWare usually defines as host-only...though you might have changed that...) with an address of 192.168.239.1 and that would be fine for you. Just set up a host-only adapter in the guest and assign it with a 192.168.239.xxx address and you should be good to go.
You set up the adapter in the guest using the Preferences requester in the virtual machine's settings options. I don't know exactly how it is done in Server since I have Workstation.
That looks right. You now have to assign an address to eth1. The address should be a 192.168.239.xxx address, and specify a default gateway for it of 192.168.239.1.
Also, the Preferences should be on the VMWare server system, which is running on the host. Like I say, I use Workstation here, not server, so I don't know exactly how server does things.
That looks right. You now have to assign an address to eth1. The address should be a 192.168.239.xxx address, and specify a default gateway for it of 192.168.239.1.
do I assign this at the linux virtual box or at the host network management?
when i try to ping 192.168.239.1, I get:
From 192.168.239.101 icmp_seq=2 Destination Host Unreachable
From 192.168.239.101 icmp_seq=3 Destination Host Unreachable
From 192.168.239.101 icmp_seq=4 Destination Host Unreachable
i would communicate to the host by using this ip: 192.168.239.1(win host)
this is my interfaces file:
You have specified a second name for eth0. You don't want to do that because that is sending your communications out of eth0, and thus onto the net regardless of destination, and the 192.168 address range is not routable, so those packets don't find their way to the host.
Your Windows host already has an internal vmnet adapter (vmnet1) that has the address 192.168.239.1. You want to connect with THAT adapter.
Get rid of eth0:1. Install a virtual network interface into your virtual machine using VMWare's networking, identify that interface as eth1, and make eth1 have the address 192.168.239.101.
The guest system's networking setup should then figure out that anything going to 192.168.239.0/24 should go through eth1. If it doesn't figure that out, tell it with a route add command.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
