SBS2003 on VMWARE - network

Hi,

I know this is really more of a VMWARE issue really, but just wondering if
anyone has any advice or has tried this already.

I've an SBS 2003 Premium virtual machine, trying to move all my older test
lab systems onto VM now and just have current stuff on the hardware.

I've got it running OK with ISA 2004 connected to the physical network and
it runs on the internet OK.

Question, how do I configure a virtual PC or otherwise to connect to the
other virtual network on the virtual SBS2003 server ?

At the moment I can only get the virtual PC to connect to the same physical
network as the NIC #2 on the virtual SBS 2003 server which is what ISA 2004
is connected to.

Basically physical network is 192.168.2.0

Physical Router/Firewall is 192.168.2.1 (physical gateway)

Virtual SBS 2003 NIC#1 is 192.168.16.2
NIC#2 is 192.168.2.3 (Gateway is 192.168.2.1) ..works OK

Virtual XP PC is currently set to get a lease and it getting that currently
from the physical Router/Firewall.

How do I get this configured so that it connects to the virtual LAN on
192.168.16.0 on the SBS 2003 and gets a lease from there instead ?

Am I missing some virtual components ?

Jim wrote:

> Hi,
>
> I know this is really more of a VMWARE issue really, but just
> wondering if anyone has any advice or has tried this already.
>
> I've an SBS 2003 Premium virtual machine, trying to move all my older
> test lab systems onto VM now and just have current stuff on the
> hardware.
>
> I've got it running OK with ISA 2004 connected to the physical
> network and it runs on the internet OK.
>
> Question, how do I configure a virtual PC or otherwise to connect to
> the other virtual network on the virtual SBS2003 server ?
>
> At the moment I can only get the virtual PC to connect to the same
> physical network as the NIC #2 on the virtual SBS 2003 server which
> is what ISA 2004 is connected to.
>
> Basically physical network is 192.168.2.0
>
> Physical Router/Firewall is 192.168.2.1 (physical gateway)
>
> Virtual SBS 2003 NIC#1 is 192.168.16.2
> NIC#2 is 192.168.2.3 (Gateway is 192.168.2.1) ..works
> OK
>
> Virtual XP PC is currently set to get a lease and it getting that
> currently from the physical Router/Firewall.
>
> How do I get this configured so that it connects to the virtual LAN
> on 192.168.16.0 on the SBS 2003 and gets a lease from there instead ?
>
> Am I missing some virtual components ?

No, you have everything you need.

What you need to do is configure a virtual network for the "internal"
SBS network to sit on.

In theory, this can be done without the host having access to this
network, but in practice, it depends on what VMWare product you're
using (eg Server v2 is a PITA on this front).

Once you have your virtual network, you bind the "internal" virtual nic
on your SBS VM to it, and then do the same with the VMs that you want
as SBS clients.

You should have a link to manage Virtual Networks with your other
VMWare management tools.

You may want to read up on virtual networks more too (searching for
"vmware virtual networks" gets plenty of useful results).

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

Thanks Steve, I'll have another look, just wanted to make sure I was on the
right track.

I think the problem stems from the fact that I'm authoring the VM's on
VMWARE Server and then copying them to another machine with better resources
and running them in a VMWARE Player.

I think I need to go back to the VMWARE Server and loof for/add the virtual
network yes ?

I'm using the latest downloads for both.

Thanks

Jim.




"Steve Foster" wrote:

> Jim wrote:
>
> > Hi,
> >
> > I know this is really more of a VMWARE issue really, but just
> > wondering if anyone has any advice or has tried this already.
> >
> > I've an SBS 2003 Premium virtual machine, trying to move all my older
> > test lab systems onto VM now and just have current stuff on the
> > hardware.
> >
> > I've got it running OK with ISA 2004 connected to the physical
> > network and it runs on the internet OK.
> >
> > Question, how do I configure a virtual PC or otherwise to connect to
> > the other virtual network on the virtual SBS2003 server ?
> >
> > At the moment I can only get the virtual PC to connect to the same
> > physical network as the NIC #2 on the virtual SBS 2003 server which
> > is what ISA 2004 is connected to.
> >
> > Basically physical network is 192.168.2.0
> >
> > Physical Router/Firewall is 192.168.2.1 (physical gateway)
> >
> > Virtual SBS 2003 NIC#1 is 192.168.16.2
> > NIC#2 is 192.168.2.3 (Gateway is 192.168.2.1) ..works
> > OK
> >
> > Virtual XP PC is currently set to get a lease and it getting that
> > currently from the physical Router/Firewall.
> >
> > How do I get this configured so that it connects to the virtual LAN
> > on 192.168.16.0 on the SBS 2003 and gets a lease from there instead ?
> >
> > Am I missing some virtual components ?
>
> No, you have everything you need.
>
> What you need to do is configure a virtual network for the "internal"
> SBS network to sit on.
>
> In theory, this can be done without the host having access to this
> network, but in practice, it depends on what VMWare product you're
> using (eg Server v2 is a PITA on this front).
>
> Once you have your virtual network, you bind the "internal" virtual nic
> on your SBS VM to it, and then do the same with the VMs that you want
> as SBS clients.
>
> You should have a link to manage Virtual Networks with your other
> VMWare management tools.
>
> You may want to read up on virtual networks more too (searching for
> "vmware virtual networks" gets plenty of useful results).
>
> --
> Steve Foster
> For SSL Certificates, Domains, etc, visit.:
> https://netshop.virtual-isp.net
> .
>

>>(eg Server v2 is a PITA on this front).


Oh lordy... I see what you mean..


Starting to go grey looking for the place to edit the VMnetworks...

Have read the help umpteen times..still can't see the bit I'm supposed to be
clicking on..virtual network editor...???? where is this ???

"Jim" wrote:

> Thanks Steve, I'll have another look, just wanted to make sure I was on the
> right track.
>
> I think the problem stems from the fact that I'm authoring the VM's on
> VMWARE Server and then copying them to another machine with better resources
> and running them in a VMWARE Player.
>
> I think I need to go back to the VMWARE Server and loof for/add the virtual
> network yes ?
>
> I'm using the latest downloads for both.
>
> Thanks
>
> Jim.
>
>
>
>
> "Steve Foster" wrote:
>
> > Jim wrote:
> >
> > > Hi,
> > >
> > > I know this is really more of a VMWARE issue really, but just
> > > wondering if anyone has any advice or has tried this already.
> > >
> > > I've an SBS 2003 Premium virtual machine, trying to move all my older
> > > test lab systems onto VM now and just have current stuff on the
> > > hardware.
> > >
> > > I've got it running OK with ISA 2004 connected to the physical
> > > network and it runs on the internet OK.
> > >
> > > Question, how do I configure a virtual PC or otherwise to connect to
> > > the other virtual network on the virtual SBS2003 server ?
> > >
> > > At the moment I can only get the virtual PC to connect to the same
> > > physical network as the NIC #2 on the virtual SBS 2003 server which
> > > is what ISA 2004 is connected to.
> > >
> > > Basically physical network is 192.168.2.0
> > >
> > > Physical Router/Firewall is 192.168.2.1 (physical gateway)
> > >
> > > Virtual SBS 2003 NIC#1 is 192.168.16.2
> > > NIC#2 is 192.168.2.3 (Gateway is 192.168.2.1) ..works
> > > OK
> > >
> > > Virtual XP PC is currently set to get a lease and it getting that
> > > currently from the physical Router/Firewall.
> > >
> > > How do I get this configured so that it connects to the virtual LAN
> > > on 192.168.16.0 on the SBS 2003 and gets a lease from there instead ?
> > >
> > > Am I missing some virtual components ?
> >
> > No, you have everything you need.
> >
> > What you need to do is configure a virtual network for the "internal"
> > SBS network to sit on.
> >
> > In theory, this can be done without the host having access to this
> > network, but in practice, it depends on what VMWare product you're
> > using (eg Server v2 is a PITA on this front).
> >
> > Once you have your virtual network, you bind the "internal" virtual nic
> > on your SBS VM to it, and then do the same with the VMs that you want
> > as SBS clients.
> >
> > You should have a link to manage Virtual Networks with your other
> > VMWare management tools.
> >
> > You may want to read up on virtual networks more too (searching for
> > "vmware virtual networks" gets plenty of useful results).
> >
> > --
> > Steve Foster
> > For SSL Certificates, Domains, etc, visit.:
> > https://netshop.virtual-isp.net
> > .
> >

Found it, it's in the flippin Start Menu>Programs

Been looking all over for it in the web console..



"Jim" wrote:

> >>(eg Server v2 is a PITA on this front).
>
>
> Oh lordy... I see what you mean..
>
>
> Starting to go grey looking for the place to edit the VMnetworks...
>
> Have read the help umpteen times..still can't see the bit I'm supposed to be
> clicking on..virtual network editor...???? where is this ???
>
> "Jim" wrote:
>
> > Thanks Steve, I'll have another look, just wanted to make sure I was on the
> > right track.
> >
> > I think the problem stems from the fact that I'm authoring the VM's on
> > VMWARE Server and then copying them to another machine with better resources
> > and running them in a VMWARE Player.
> >
> > I think I need to go back to the VMWARE Server and loof for/add the virtual
> > network yes ?
> >
> > I'm using the latest downloads for both.
> >
> > Thanks
> >
> > Jim.
> >
> >
> >
> >
> > "Steve Foster" wrote:
> >
> > > Jim wrote:
> > >
> > > > Hi,
> > > >
> > > > I know this is really more of a VMWARE issue really, but just
> > > > wondering if anyone has any advice or has tried this already.
> > > >
> > > > I've an SBS 2003 Premium virtual machine, trying to move all my older
> > > > test lab systems onto VM now and just have current stuff on the
> > > > hardware.
> > > >
> > > > I've got it running OK with ISA 2004 connected to the physical
> > > > network and it runs on the internet OK.
> > > >
> > > > Question, how do I configure a virtual PC or otherwise to connect to
> > > > the other virtual network on the virtual SBS2003 server ?
> > > >
> > > > At the moment I can only get the virtual PC to connect to the same
> > > > physical network as the NIC #2 on the virtual SBS 2003 server which
> > > > is what ISA 2004 is connected to.
> > > >
> > > > Basically physical network is 192.168.2.0
> > > >
> > > > Physical Router/Firewall is 192.168.2.1 (physical gateway)
> > > >
> > > > Virtual SBS 2003 NIC#1 is 192.168.16.2
> > > > NIC#2 is 192.168.2.3 (Gateway is 192.168.2.1) ..works
> > > > OK
> > > >
> > > > Virtual XP PC is currently set to get a lease and it getting that
> > > > currently from the physical Router/Firewall.
> > > >
> > > > How do I get this configured so that it connects to the virtual LAN
> > > > on 192.168.16.0 on the SBS 2003 and gets a lease from there instead ?
> > > >
> > > > Am I missing some virtual components ?
> > >
> > > No, you have everything you need.
> > >
> > > What you need to do is configure a virtual network for the "internal"
> > > SBS network to sit on.
> > >
> > > In theory, this can be done without the host having access to this
> > > network, but in practice, it depends on what VMWare product you're
> > > using (eg Server v2 is a PITA on this front).
> > >
> > > Once you have your virtual network, you bind the "internal" virtual nic
> > > on your SBS VM to it, and then do the same with the VMs that you want
> > > as SBS clients.
> > >
> > > You should have a link to manage Virtual Networks with your other
> > > VMWare management tools.
> > >
> > > You may want to read up on virtual networks more too (searching for
> > > "vmware virtual networks" gets plenty of useful results).
> > >
> > > --
> > > Steve Foster
> > > For SSL Certificates, Domains, etc, visit.:
> > > https://netshop.virtual-isp.net
> > > .
> > >

Jim wrote:

> Thanks Steve, I'll have another look, just wanted to make sure I was
> on the right track.
>
> I think the problem stems from the fact that I'm authoring the VM's
> on VMWARE Server and then copying them to another machine with better
> resources and running them in a VMWARE Player.
>
> I think I need to go back to the VMWARE Server and loof for/add the
> virtual network yes ?
>
> I'm using the latest downloads for both.

I can't see any reason to use VMWare Player.

But you'll need to configure the virtual networking wherever the VMs
are actually running.

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net

Jim wrote:

> >>(eg Server v2 is a PITA on this front).
>
>
> Oh lordy... I see what you mean..

Actually, no, that's not what I meant. With Server v2, the network
management tool won't properly configure a "guest-only" network (which
should be allowed) - it only properly manages networks where there's
either an associated real nic, or you add VMWare virtual nic adapter(s)
to the host, both of which allow [at least] the host access to that
virtual network.

I've had to resort to manually configuring the virtual networking
before now.

--
Steve Foster
For SSL Certificates, Domains, etc, visit.:
https://netshop.virtual-isp.net