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
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Erick Larson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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.
>
> "Phillip Windell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>> "Erick Larson" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> 1. Correct - only the management NIC has a default GW set on it.
>>> Verified.
>>>
>>> 2. Correct - the Hyper-V has no settings. Verified.
>>>
>>> "Phillip Windell" <(E-Mail Removed)> wrote in message
>>> news:#(E-Mail Removed)...
>>>> "ErickL" <(E-Mail Removed)> wrote in message
>>>> news:92FB6D41-B0FC-4DB4-911E-(E-Mail Removed)...
>>>>>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 255.255.255.128 gw a.b.c.1 iSCSI NICs
>>>>>are 10.b.c.d and 10.b.c.e mask 255.0.0.0 no GW. Setting GW on
>>>>>management NIC creates persistent route 0.0.0.0 mask 0.0.0.0 GW a.b.c.1
>>>>>as it does in 2008 (per route print.) I'm stumped - any clues?
>>>>
>>>> 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.
>>>>
>>
>>
|
Similar Threads
Linear Mode
