Member Avatar for bondi007

I have two virtual machines, one running Server 2003 Enterprise and one running Windows XP Professional. I want these two operating systems to operate in there own network, not connected to anything else. I have been doing some research but have been getting confused and I have had no look...

Thanks
Bondi

  • 2 Contributors
  • 7 Replies
  • 197 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

Short answer: don’t use Bridged if you want an internal-only network. Create a Host‑Only or a custom VMnet and put both guests onto that virtual switch — that gives a private LAN between the VMs (optionally without the host), and is the cleanest way to run a tiny isolated network for Server 2003 + XP. (virtualizationreview.com)

How to do it (Workstation): open Edit → Virtual Network Editor, Add Network (e.g. VMnet2) and set it to Host‑only. If you want the VMs isolated from the host as well, uncheck “Connect a host virtual adapter to this network” and disable the VMnet DHCP (then use static IPs). In each VM go to VM → Settings → Network Adapter → Custom and select your VMnet. Then verify the guest NIC is “Connected” and “Connect at power on.” (pdfcoffee.com)

Example IPs and quick tests (on each guest):

Static IP: 192.168.50.10/24 and 192.168.50.11/24
Commands to run:
ipconfig /all
ping 192.168.50.11

If ping fails, common causes and fixes: make sure both guests actually have addresses on the same subnet; check the VM’s network adapter is attached to the same VMnet; temporarily disable the Windows Firewall on the XP/2003 guests or enable inbound ICMP (pings) to rule out firewall blocking; bridged mode can also behave oddly when the host is using Wi‑Fi because Workstation picks the physical adapter automatically — host‑only avoids that complexity. (manualzilla.com)

Tieback to the thread: ’s bridged suggestion will put the VMs on the physical LAN (not isolated). For your goal , create a host‑only/custom VMnet and either use the VMnet DHCP or assign simple static addresses as above — that will give you a private two‑node network with easy, testable connectivity. (virtualizationreview.com)

Recommended Answers

All 7 Replies

Member Avatar for sknake

Are they configured with a bridged ethernet adapter from your host OS? They should be able to communicate with standard TCP/IP networking.

You can firewall egress on the host OS to stop their traffic from leaving the local computer.

Member Avatar for bondi007

I just set them to bridged, I am rather new but they don't seem to see each other..., I am not sure what you mean...


Sorry, newbie here :?:


Bondi

Member Avatar for sknake

Do you have the interfaces configured on the VMs? Can they ping eachother? What are their network settings? What is the host OS' network settings? How are you testing them "seeing eachother"? What is the host OS?

Member Avatar for bondi007

Vmware installs 2 adapters on the host machine by default, I have not changed any of them, the host OS is Windows Vista Home Premium, and I am testing them by trying to connect to a domain, the both VM's can connect to the internet from the host machine though...


Bondi

Member Avatar for sknake

Ah i'm not sure about Vista. I'm still holding on to XP :) You might try freenode's irc channel for VMWare: -- channel #vmware. You can use mIRC as an IRC client: http://www.mirc.com. You can find vmWare developers and excellent support there.

Member Avatar for bondi007

I have a XP machine with VMware, would it work on there? I dont want it to contact the host for connection, just manage a little network between the VM's?


Bondi

Member Avatar for sknake

I'm not sure if it would work or not but more than likely yes. My experience with Vista is that everything breaks. I'm not knocking Vista -- it is a change that has to happen. However I haven't had good luck with it so far.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.