>
>
> "DP" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi,
> > We've recently set up a new Hyper-V (v6.0.6001.17101) on Win2008 SP1.
> > There
> > are 3 VM's set up on the server, and they seem to be running fine.
> > However,
> > the VM's cannot talk to each other or the VM host server, and vice versa
> > (via
> > 'ping', 'tracert', etc). They can access other servers in our network just
> > fine, and v.v.
> >
> > The physical VM server has 2 network ports, but only one is active. We
> > have
> > one virtual NIC going to this physical port, and all the VM's are using
> > it.
> >
> > I believe the issue is with how the network connections are set up on the
> > VM
> > host server, but I'm not sure how they should be set. The phyiscal network
> > interface was created before we config'd Hyper-V, and the virtual network
> > interfaces were created automatically when installing Hyper-V.
> >
> > Any suggestions would be much appreciated. Thanks.
>
> If the virtual machines can all see the machines on the physical LAN,
> they must be in the same network and IP subnet as each other and the
> physical machines. The most likely cause is firewall settings on the vms
> and the host rather than networking problems.
>
>
> .
>

> Hi,
> We've recently set up a new Hyper-V (v6.0.6001.17101) on Win2008 SP1.
> There
> are 3 VM's set up on the server, and they seem to be running fine.
> However,
> the VM's cannot talk to each other or the VM host server, and vice versa
> (via
> 'ping', 'tracert', etc). They can access other servers in our network just
> fine, and v.v.
>
> The physical VM server has 2 network ports, but only one is active. We
> have
> one virtual NIC going to this physical port, and all the VM's are using
> it.
>
> I believe the issue is with how the network connections are set up on the
> VM
> host server, but I'm not sure how they should be set. The phyiscal network
> interface was created before we config'd Hyper-V, and the virtual network
> interfaces were created automatically when installing Hyper-V.
>
> Any suggestions would be much appreciated. Thanks.

> Bill,
> Thanks for the reply. We figured out the culprit and you were correct. The
> problem was due to our Symantec Endpoint Protection installation (it has
> built-in firewall features). We've yet to narrow down what exactly in
> Symantec caused it, but once we uninstalled it, the issue was gone. Thanks
> again.
>
>
>
> "Bill Grant" wrote:
>
>>
>>
>> "DP" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi,
>> > We've recently set up a new Hyper-V (v6.0.6001.17101) on Win2008 SP1.
>> > There
>> > are 3 VM's set up on the server, and they seem to be running fine.
>> > However,
>> > the VM's cannot talk to each other or the VM host server, and vice
>> > versa
>> > (via
>> > 'ping', 'tracert', etc). They can access other servers in our network
>> > just
>> > fine, and v.v.
>> >
>> > The physical VM server has 2 network ports, but only one is active. We
>> > have
>> > one virtual NIC going to this physical port, and all the VM's are using
>> > it.
>> >
>> > I believe the issue is with how the network connections are set up on
>> > the
>> > VM
>> > host server, but I'm not sure how they should be set. The phyiscal
>> > network
>> > interface was created before we config'd Hyper-V, and the virtual
>> > network
>> > interfaces were created automatically when installing Hyper-V.
>> >
>> > Any suggestions would be much appreciated. Thanks.
>>
>> If the virtual machines can all see the machines on the physical LAN,
>> they must be in the same network and IP subnet as each other and the
>> physical machines. The most likely cause is firewall settings on the vms
>> and the host rather than networking problems.
>>
>>
>> .
>>

> Bill,
> Thanks for the reply. We figured out the culprit and you were correct. The
> problem was due to our Symantec Endpoint Protection installation (it has
> built-in firewall features). We've yet to narrow down what exactly in
> Symantec caused it, but once we uninstalled it, the issue was gone. Thanks
> again.
>
>
>
> "Bill Grant" wrote:
>
> >
> >
> > "DP" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > > Hi,
> > > We've recently set up a new Hyper-V (v6.0.6001.17101) on Win2008 SP1.
> > > There
> > > are 3 VM's set up on the server, and they seem to be running fine.
> > > However,
> > > the VM's cannot talk to each other or the VM host server, and vice
> > > (via
> > > 'ping', 'tracert', etc). They can access other servers in our network
> > > fine, and v.v.
> > >
> > > The physical VM server has 2 network ports, but only one is active. We
> > > have
> > > one virtual NIC going to this physical port, and all the VM's are
> > > it.
> > >
> > > I believe the issue is with how the network connections are set up on
> > > VM
> > > host server, but I'm not sure how they should be set. The phyiscal
> > > interface was created before we config'd Hyper-V, and the virtual
> > > interfaces were created automatically when installing Hyper-V.
> > >
> > > Any suggestions would be much appreciated. Thanks.
> >
> > If the virtual machines can all see the machines on the physical LAN,
> > they must be in the same network and IP subnet as each other and the
> > physical machines. The most likely cause is firewall settings on the
> > and the host rather than networking problems.
> >
> >
> > .
> >