Re: Windows 2003 and Virtual Server 2005

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Well, I mean, say I'm at home with one box with virtual server 2005 ( I'm
hoping 1G of memory will suffice ) and I want to simulate being in a netork,
LAN environment. I've been reading about the Loopback Adapter. I just want to
practice with network concepts, such as DHCP, DNS, IIS, etc. I've been taking
a course in network infrastructure of windows 2003 server and I want to get
some hands-on training. So, that being said, how would I set up a virtual
network?

"neo [mvp outlook]" wrote:

1) Personal preference, but I wouldn't recommend anything less than 2GB.
(This nets me 3 Virtual Machines with enough resources left over for the
host operating system.)


2) I'm not sure how to interpret your very broad question. I can take it
that you don't know where to start, not sure that when defining the virtual
machines if you should be selecting External or Internal for the network
type, .etc.

Just so you know, I'm always behind a corporate network firewall, so I can
always use the External network type definition for VMs because I want my
VMs to reach other servers on the corporate network + internet. I can't
tell you what is best for you because I don't know what obstacles you need
to overcome.


"Dominick D." <DominickD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33BC0AFC-0E09-4F52-98C7-B867363B7E17@xxxxxxxxxxxxxxxx
Thanks for you quick response. I want to use this for educational/training
purposes and I have two questions:

1. How much memory is required on my machine to use virtual server 2005
effectively

2. How do you setup a virtual network, as if it were an actual LAN-type of
network?

I'm studying for the MCDBA and the coursework requires hands-on practice,
so
I thought this would be a good idea to load 2003 server and have a virtual
network with it to practice DHCP, DNS, RRAS, etc. Thanks for your
assistance.


Dominick


"neo [mvp outlook]" wrote:

Windows 2003 can be a guest operating system in Virtual Server 2005.

You don't have to use the loopback adapter to setup virtual networks.

"Dominick D." <DominickD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14C96EE2-E687-4214-8245-AA277EF97B91@xxxxxxxxxxxxxxxx
Hello, Folks; Does anyone know much about Virtual Server 2005? Can that
be
used to install 2003 Server and can you setup a virtual network with
it,
or
do you have to use the Loopback Adapter? Thanks.






.

Relevant Pages

  • Re: Fully parallel Scheme-based language w/ evaluator
    ... Windows Server 2003 and networks in simple - and irreverent - terms. ... If networking really is a big deal, ... Concepts and Terminology in Part I, and The Design and Deployment of Network ...
    (comp.lang.misc)
  • RE: Securing a Local Network
    ... Show the Management of your company the insecurity of the Peer to Peer ... setup and discuss what risks are they willing to accept. ... -Cost of getting the web server and the mail server internally versus having ... -Use an older box for Intrusion Detection on the internal network as well. ...
    (Security-Basics)
  • ksoftirqd causing severe network performance problems
    ... failover setup), with a new one. ... At the end of last week, the new setup had network problems and what we saw on ... the linux router was that the kernel threads ksoftirqd_CPU1 and ksoftirqd_CPU0 ... When the backup is working fine, we can't use the faulty server anymore ...
    (Linux-Kernel)
  • RDP to internal client machine?
    ... Have the router successfully setup to allow VPN to the server, ... to then RDP to other computers within the network, ... machines within the network I ...
    (microsoft.public.windows.server.sbs)
  • ksoftirqd causing severe network performance problems
    ... failover setup), with a new one. ... At the end of last week, the new setup had network problems and what we ... When the backup is working fine, we can't use the faulty server ... switching drivers and switching between kernel versions (2.4.21/2.4.22/ ...
    (comp.os.linux.networking)