Windows 2008R2 netwwork problem

Discussion in 'Server Networking' started by ErickL, Aug 28, 2009.

  1. ErickL

    ErickL Guest

    I have a Dell PowerEdge 2950 with Win2008R2 as a testbed for Hyper-V. The
    box has a dual Broadcom NIC with one side as the management interface with
    public IP and the other as a Hyper-V external network for the VMs to use.
    The machine also has a dual Intel Pro1000 PT for iSCSI connections. The
    setup is identical to the Win2008 box that is currently running Hyper-V VMs.
    The machine is in AD and the management NIC shows it as being in a Domain
    Network. The Hyper-V network card does not appear in the network config
    because it is exclusive for Hyper-V - fine, it works. The private network
    NICs with 10.x.x.x IPs appear as a Public Network (apparently MS name for a
    private network ;- ) with no network access. The private network is
    10.x.x.x/25 with GW of 10.x.x.1 and the public network is y.y.y.y/25 with GW
    of y.y.y.1. So management NIC is a.b.c.d mask gw a.b.c.1
    iSCSI NICs are 10.b.c.d and 10.b.c.e mask no GW. Setting GW on
    management NIC creates persistent route mask GW a.b.c.1 as
    it does in 2008 (per route print.) I'm stumped - any clues?

    ErickL, Aug 28, 2009
    1. Advertisements

  2. 1. You put a Default Gateway on only one nic

    2. If a particular nic is dedicated to only the use the VMs than it does not
    need any TCP/IP Specs at all. It does not even need TCP/IP or anything else
    bound to the adapter.
    Phillip Windell, Aug 28, 2009
    1. Advertisements

  3. ErickL

    Erick Larson Guest

    1. Correct - only the management NIC has a default GW set on it. Verified.

    2. Correct - the Hyper-V has no settings. Verified.
    Erick Larson, Aug 28, 2009
  4. I guess I don't know that the question is.

    I don't know if I would even be of any help,..but no one else has
    replied,...maybe you need to make the problem more clear.
    Phillip Windell, Aug 28, 2009
  5. ErickL

    Erick Larson Guest

    the two 10.x NICs show that they are connected at 1Gb in the logs
    (expected - they are gig NICs on a Gig switch) but in NetworkSharingCenter,
    they show as having No Network Access - and they don't. iSCSI, if restricted
    to the 10.x NICs will not connect to the SAN on the same 10.x network.
    Oddly, I find that if I move the wire from the 10.x NIC to a new port that
    has never been used, it will work until the server is rebooted and then it's
    back to more of the same. When the server had 2008 on it, all of this worked
    just fine.
    Erick Larson, Aug 28, 2009
  6. I had a similar problem with a trial version of 2008R2. After two days
    never figfured it out,..gave up. I now have no plans of ever going to
    2008,..will probably refuse it like we did Vista. It just seems to be a
    repeat of the Vista mess as far as I am concerned.

    Maybe others here will have suggestions if you give them time.
    Phillip Windell, Aug 31, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.