Re: Public/Private network problem when clustering with Server 2008

Hello PaulS,

Crossposted to:
microsoft.public.windows.server.clustering

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> When I attempt to connect two servers via a cross over cable for a
> "heartbeat" connection they detect the connection as a "Public"
> network with limited connectivity. You cannot even ping between them.
> Having then set them as "Private" communication is established. The
> problem is that when they are disconnected and reconnected they revert
> back to "Public". Is there any way to either force them to stay as
> "Private" or to customise the "Public" setting to allow communication?
> Thanks.
>

Are your heartbeat NICs configured with a default gateway?
--
Jeff Hughes, MCSE
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support (Server Core/Cluster)


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news: .com...
> Hello PaulS,
>
> Crossposted to:
> microsoft.public.windows.server.clustering
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> When I attempt to connect two servers via a cross over cable for a
>> "heartbeat" connection they detect the connection as a "Public"
>> network with limited connectivity. You cannot even ping between them.
>> Having then set them as "Private" communication is established. The
>> problem is that when they are disconnected and reconnected they revert
>> back to "Public". Is there any way to either force them to stay as
>> "Private" or to customise the "Public" setting to allow communication?
>> Thanks.
>>
>
>