I have hosted two images (both 2003 servers) from my VMServer. Including my desktop (xp-pro) there are three host.
I would like to connect them in a network (local LAN) without a physical switch.
Is there any software switch so that I can run in my desktop OS and let images use that interface to get IP automatically so that I can access Images from desktop OS?
Well you could use dynamips (+ GNS3), but just use VMware's virtual infrastructure:
http://www.virtualizationadmin.com/articles-tutorials/vmware-esx-and-vsphere-articles/installation-deployment/vmware-understanding-virtual-switch.html
i.e. You need to upgrade to at least ESX, now it's vSphere.
edit: Oh you really are on very basics of using a virtual machine: just use bridged networking:
http://www.vmware.com/support/ws55/doc/ws_net_configurations_bridged.html
Related
I have created and I am happily using a virtual lab with Hyper-V software on my Windows 8 professional.
The lab include four servers:
Windows Server with Active Directory and DNS
Windows Server with SQL Server 2012
Windows Server with SharePoint 2013 server
All the servers have the following network configuration
IP Address: 192.168.10.x
Subnet Mask: 255.255.255.0
Everything works as expected. Now I need to make something to make the lab access the internet. By reading here and there I have found a post which explains how to setup the ICS.
I suspect however that this will not work in my case because the configuration of the IP address used by ICS which is in a different subnet (192.168.137.1).
How can I do to make the lab access the internet for windows updates?
Thanks
EDIT:
I have added a small simple diagram to explain the scenario.
You could create another virtual switch which is external. Add another network interface to your devices and conect the external virtual switch. Just activate the network interface when you need to update so it won't interfere with your lab enviroment.
I am using OSX Mavericks and VMWare Fusion v6.0.2.
I am running two Virtual machines, one Windows 7 Pro, and the other Debian Sid.
I do not wish to use NAT networking through the Host, I prefer to have the VMs sitting directly on the network, but I am having a problem getting the bridged networking functionality of VMWare Fusion working correctly. I have set the VMWare Network preferences page to Bridge the VMs to the Mac internal WiFi adapter.
Both VMs can ping the router, and they both get valid DHCP assigned IP addresses for the LAN. They can both connect to the Internet over the network bridge and browse and download files.
My problem is when I wish to communicate between the VM->Host, Host->VM, or VM->VM over other ports. For example if I try to SSH from OSX Host to the Debian VM, the request times out. The Windows 7 VM has a SQL Server running on it, but I cannot connect to it from the OSX host, or from the Debian VM. The Debian VM has a xsp4 web-server running on port 8080, but neither the OSX host nor the Debian VM can access it.
I can ping from Host->VM, VM->Host, and VM->VM with no issue, they can all see each other on the network, and the OSX host is sharing network folders to the Windows 7 VM without a hitch. It seems like it is allowing some communication, such as DHCP requests, Ping requests, Windows Network Shares, and Web Browsing, but is not allowing anything else.
I have turned off the Windows Firewall, OSX Mavericks firewall is turned off, and the Debian VM doesn't have selinux or iptables firewalls installed.
I have found several similar question threads while researching this problem, but a lot of them are for much older versions of VMWare Fusion, or are for VMWare Workstation which has different network preferences.
I can get these scenarios working to a degree if I switch VMWare's network settings to use NAT instead of bridging, but that messes up the IP addresses of the VMs, I want to keep them on the same network.
For what its worth, I did eventually come up with an answer for this.
There are two different versions of VMWare Fusion 6.x, Standard and Professional.
I was using the Standard version.
I changed the licence for a Professional licence, which allows you to add new network configurations in VMWare Preferences (and other cool things like that).
I added a new network with the default options, then assigned all of my VMs to that new network interface. I also turned on Promiscious mode in settings, but that might not have changed anything.
I then rebooted the VMs, set them up correctly to work on their new IP addresses, and Lo and Behold, I was able to establish connections between VM->Host and VM->VM. Exactly what I wanted.
I realize that this post is several years old, but since I had such a hard time with an issue similar to this, I wanted to post my answer as well, though I am not positive it really solved my issue. No problems still.
My setup:
MacBook Pro (Retina, 15-inch, Mid 2015)
OS X El Capitan
My problem:
In order to allow me to clone my private school git repository using ssh keys, I have to run a bridged network connection for my Windows 10 Eduction VM using VMWare Fusion.
What I've Tried:
http://www.kapilarya.com/windows-sockets-registry-entries-required-for-network-connectivity-is-missing
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016466
And several other blog posts and forum replies, all attempting to do somewhat the same thing.
Answer:
After numerous attempts to reset just about everything you could, I took a step back and brainstormed. Then I thought, if my host machine (Macbook Pro) could connect wirelessly to the internet, this bridged connection should still work. I checked the Network Adapter's MAC Assigned to the VM's Network Adaptor and it was different from my host computer's wifi address (MAC Address). I then entered my host machine's wifi network address (MAC Address) in as the effective MAC Address for the Windows VM Network Adaptor and..voila, internet.
I'm running Apache etc (actually MAMP at the moment, but soon to be replaced by individual Apache, PHP, MySQL...) on my Mac, for testing my websites locally/offline.
I want to be able to test all my local sites (domains *.dev) from any and all of the following, without having to update the hots file on each device (some of which, such as un-rooted phones, don't even allow editing of the hosts file):
Obviously, my Mac itself...
Any device on any local network to which my mac is connected (My Mac doesn't necessarily always have the same IP address)
Any virtual machine running on my Mac (in Parallels) – primarily, various versions of Windows (my Mac does always have the same IP address on Parallels Shared Networking)
Now, I read that dnsmasq may be able to help, and have installed it on my Mac using Homebrew. I set it up to start on startup, and my dnsmasq.conf reads as follows:
address=/.dev/127.0.0.1
This has the effect of allowing any domain *.dev to work on my Mac itself, which is a start.
Next I tried to make it work in a Parallels VM by setting the DNS server to be the local IP address of my Mac. However, this doesn't work – because dnsmasq returns 127.0.0.1 as the IP for any lookup for *.dev, but of course this makes the VM look for the site on the VM itself, rather than on my Mac... which obviously doesn't work.
So I'm a bit stumped. Can anyone give me any tips? Is there a way to set up dnsmasq to do what I want, or should I be looking at another method?
Thanks!
I don't have any experience with Parallels but with Virtualbox you can set up a bridged network connection. I presume Parallels has something similar. This will set up an internal network (e.g. on 192.168.1.*) and you can probably assign fixed IP addresses to that. Like this you can give the Mac a fixed IP address which you can also use in your dnsmasq configuration - but you might want to have two TLDs for this so that .dev can keep pointing to 127.0.0.1 while .devel points to 192.168.1.xx.
I have a dedicated virtual debian server running with my website, and now have a copy of that so that I can try some configurations by running it virtually on my own PC. It runs fine, but I'm unable to access the machine through http.
The problem is that my machine has a fixed ip, something like 194.247.x.x . My home network however has computers in the range of 192.168.1.x
Is it possible to not change anything in my virtual machine and still configure vmware networking so that I'm able to access the websites it's running?
The only way I can see this happening for you is to use NAT (Network Address Translation) between your home network and your VM.
To do this, you could use a free software based router - something like Vyatta (www.vyatta.org) - and create a VM with two NICs - one with an IP on your home network, and the other with an IP on the same network as your VM. You then configure NAT to translate your home IP to your web server IP and then you're done.
There's nothing 'de-facto' VMware that will allow you to do this (other than using vShield - which will do NAT'ing anyway)...
I'm writing TCP/IP code for a DHCP enabled network device. Is there a universal way this device can announce its hostname in-the-wild that pretty much all web browsers (on osx/linux/win) can access it by name? (e.g. http://mydevice/index.htm)
A solution that allows the end-user to use their "stock" computer without stringent requirements like installing packages such as bonjour for windows, have a dns server on their network, etc.
zeroconf/dns-sd doesn't work on windows machines that don't have bonjour (or similar) service installed and LLMNR doesn't work on osx machines out of the box.
If there is no single way of doing this, would conforming to both dns-sd and LLMNR cover most of the installed OS base out there?
From what I can gather, in order to cover hostname resolution in a dns-less network, ZeroConf/mDns/Dns-Sd and NetBios (NetBt) are required to cover windows based, and Osx based system (most linux systems also suppor ZeroConf).
NetBt doesn't support IpV6, and LLMNR is supported by Vista and onwards Microsoft developed operating systems. So a "universal" name resolution method might have to implement all three.