1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Virtual Network on Win Server 2003 R2 x64 on Hyper-V

Discussion in 'Windows Home Server' started by Marc B., Aug 31, 2009.

  1. Marc B.

    Marc B. Guest

    Hello,

    i installed Windows Server 2003 R2 SP2 x64 on Hyper-V (2008 R2). And i have
    an unknow Device in Device Manager...and i have no Network connectivity..so
    i guess it's this one is Unknow.
    I read somewhere on the Hyper-V's Help, that Win2003 x64 doesnt support
    Legacy network driver on Hyper-V...so i guess it's that why i don't have
    Network connectivity...
    I need an External Virtual network on my Win2003 Server...
    there is so no way to have it on Win2003 x64 on Hyper-V ?
    if not, then i will run x86 editions..

    Thanks to let me know,

    Regards,

    Marc.
     
    Marc B., Aug 31, 2009
    #1
  3. Bill Grant

    Bill Grant Guest

    "Marc B." <marc.berger@live.fr> wrote in message
    news:#2VjWooKKHA.4236@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hello,
    >
    > i installed Windows Server 2003 R2 SP2 x64 on Hyper-V (2008 R2). And i
    > have an unknow Device in Device Manager...and i have no Network
    > connectivity..so i guess it's this one is Unknow.
    > I read somewhere on the Hyper-V's Help, that Win2003 x64 doesnt support
    > Legacy network driver on Hyper-V...so i guess it's that why i don't have
    > Network connectivity...
    > I need an External Virtual network on my Win2003 Server...
    > there is so no way to have it on Win2003 x64 on Hyper-V ?
    > if not, then i will run x86 editions..
    >
    > Thanks to let me know,
    >
    > Regards,
    >
    > Marc.
    ><!--colorc--><!--/colorc-->

    You are correct. There is no 64-bit driver for the legacy NIC in Hyper-V.
    The legacy NIC was the one use in VPC/Virtual Server and is a emulation of a
    very old DEC/Intel card.

    You can use the new synthetic NIC. The driver for this will be installed
    when you install the integration components. If your server is already at
    SP2 this should not be a problem.
     
    Bill Grant, Aug 31, 2009
    #2
  4. Marc B.

    Marc B. Guest

    Hello,

    what you mean by new synthetic NIC ?
    I'm already in SP2 anyways

    thanks for the help,

    Marc.

    "Bill Grant" <not.available@online> wrote in message
    news:ei7Lh5pKKHA.1492@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >
    > "Marc B." <marc.berger@live.fr> wrote in message
    > news:#2VjWooKKHA.4236@TK2MSFTNGP04.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Hello,
    >>
    >> i installed Windows Server 2003 R2 SP2 x64 on Hyper-V (2008 R2). And i
    >> have an unknow Device in Device Manager...and i have no Network
    >> connectivity..so i guess it's this one is Unknow.
    >> I read somewhere on the Hyper-V's Help, that Win2003 x64 doesnt support
    >> Legacy network driver on Hyper-V...so i guess it's that why i don't have
    >> Network connectivity...
    >> I need an External Virtual network on my Win2003 Server...
    >> there is so no way to have it on Win2003 x64 on Hyper-V ?
    >> if not, then i will run x86 editions..
    >>
    >> Thanks to let me know,
    >>
    >> Regards,
    >>
    >> Marc.
    >><!--colorc--><!--/colorc-->
    >
    > You are correct. There is no 64-bit driver for the legacy NIC in
    > Hyper-V. The legacy NIC was the one use in VPC/Virtual Server and is a
    > emulation of a very old DEC/Intel card.
    >
    > You can use the new synthetic NIC. The driver for this will be installed
    > when you install the integration components. If your server is already at
    > SP2 this should not be a problem.
    >
    > <!--colorc--><!--/colorc-->
     
    Marc B., Sep 1, 2009
    #3
  5. Bill Grant

    Bill Grant Guest

    The default NIC in a Hyper-V guest is the synthetic NIC. Unlike the legacy
    NIC, it is not an emulation of any physical NIC, hence the "synthetic" tag.

    If you install the integration components in the vm, the driver for this
    NIC will be loaded (along with a lot of other goodies to improve the
    operation of the OS in a virtual environment). Server 2003 was shipped long
    before Hyper-V, so the OS is not Hyper-V aware. It needs the ICs to function
    smoothly in a vm under Hyper-V.


    "Marc B." <marc.berger@live.fr> wrote in message
    news:OQDoTJtKKHA.4376@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hello,
    >
    > what you mean by new synthetic NIC ?
    > I'm already in SP2 anyways
    >
    > thanks for the help,
    >
    > Marc.
    >
    > "Bill Grant" <not.available@online> wrote in message
    > news:ei7Lh5pKKHA.1492@TK2MSFTNGP03.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >>
    >>
    >> "Marc B." <marc.berger@live.fr> wrote in message
    >> news:#2VjWooKKHA.4236@TK2MSFTNGP04.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Hello,
    >>>
    >>> i installed Windows Server 2003 R2 SP2 x64 on Hyper-V (2008 R2). And i
    >>> have an unknow Device in Device Manager...and i have no Network
    >>> connectivity..so i guess it's this one is Unknow.
    >>> I read somewhere on the Hyper-V's Help, that Win2003 x64 doesnt support
    >>> Legacy network driver on Hyper-V...so i guess it's that why i don't have
    >>> Network connectivity...
    >>> I need an External Virtual network on my Win2003 Server...
    >>> there is so no way to have it on Win2003 x64 on Hyper-V ?
    >>> if not, then i will run x86 editions..
    >>>
    >>> Thanks to let me know,
    >>>
    >>> Regards,
    >>>
    >>> Marc.
    >>><!--colorc--><!--/colorc-->
    >>
    >> You are correct. There is no 64-bit driver for the legacy NIC in
    >> Hyper-V. The legacy NIC was the one use in VPC/Virtual Server and is a
    >> emulation of a very old DEC/Intel card.
    >>
    >> You can use the new synthetic NIC. The driver for this will be installed
    >> when you install the integration components. If your server is already at
    >> SP2 this should not be a problem.
    >>
    >><!--colorc--><!--/colorc-->
    >
    > <!--colorc--><!--/colorc-->
     
    Bill Grant, Sep 1, 2009
    #4
  6. Marc B.

    Marc B. Guest

    Well, indeed i installed The Integration Services Setup, and it works very
    well!

    thanks dude

    Regards,

    Marc


    "Bill Grant" <not.available@online> wrote in message
    news:%23awzsatKKHA.1376@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > The default NIC in a Hyper-V guest is the synthetic NIC. Unlike the
    > legacy NIC, it is not an emulation of any physical NIC, hence the
    > "synthetic" tag.
    >
    > If you install the integration components in the vm, the driver for this
    > NIC will be loaded (along with a lot of other goodies to improve the
    > operation of the OS in a virtual environment). Server 2003 was shipped
    > long before Hyper-V, so the OS is not Hyper-V aware. It needs the ICs to
    > function smoothly in a vm under Hyper-V.
    >
    >
    > "Marc B." <marc.berger@live.fr> wrote in message
    > news:OQDoTJtKKHA.4376@TK2MSFTNGP03.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Hello,
    >>
    >> what you mean by new synthetic NIC ?
    >> I'm already in SP2 anyways
    >>
    >> thanks for the help,
    >>
    >> Marc.
    >>
    >> "Bill Grant" <not.available@online> wrote in message
    >> news:ei7Lh5pKKHA.1492@TK2MSFTNGP03.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>>
    >>>
    >>> "Marc B." <marc.berger@live.fr> wrote in message
    >>> news:#2VjWooKKHA.4236@TK2MSFTNGP04.phx.gbl...
    >>>> Hello,
    >>>>
    >>>> i installed Windows Server 2003 R2 SP2 x64 on Hyper-V (2008 R2). And i
    >>>> have an unknow Device in Device Manager...and i have no Network
    >>>> connectivity..so i guess it's this one is Unknow.
    >>>> I read somewhere on the Hyper-V's Help, that Win2003 x64 doesnt support
    >>>> Legacy network driver on Hyper-V...so i guess it's that why i don't
    >>>> have Network connectivity...
    >>>> I need an External Virtual network on my Win2003 Server...
    >>>> there is so no way to have it on Win2003 x64 on Hyper-V ?
    >>>> if not, then i will run x86 editions..
    >>>>
    >>>> Thanks to let me know,
    >>>>
    >>>> Regards,
    >>>>
    >>>> Marc.
    >>>>
    >>>
    >>> You are correct. There is no 64-bit driver for the legacy NIC in
    >>> Hyper-V. The legacy NIC was the one use in VPC/Virtual Server and is a
    >>> emulation of a very old DEC/Intel card.
    >>>
    >>> You can use the new synthetic NIC. The driver for this will be
    >>> installed when you install the integration components. If your server is
    >>> already at SP2 this should not be a problem.
    >>>
    >>><!--colorc--><!--/colorc-->
    >>
    >> <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
    Marc B., Sep 1, 2009
    #5

Share This Page