Unicast and destination host host unreachable.

Terminal Server Configured to NLB with Unicast.
Server functioning is working properly but when we connect to NETWORK
LOAD BALANCING MANAGER
When it try to other node it showed destination host unreachable,
error connecting to "2ndHOST NAME".
Can some one tell me what is missing here?

Do you have a second NIC configued as the management interface?

--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
"Rush" <rasikaf@gmail.com> wrote in message
news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
> Terminal Server Configured to NLB with Unicast.
> Server functioning is working properly but when we connect to NETWORK
> LOAD BALANCING MANAGER
> When it try to other node it showed destination host unreachable,
> error connecting to "2ndHOST NAME".
> Can some one tell me what is missing here?
>

On Aug 21, 9:59 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
wrote:
> Do you have a second NIC configued as the management interface?
>
> --
> Chuck Timon, Jr.
> Microsoft Corporation
> Windows Server 2008 Readiness Team
> This posting is provided 'AS IS" with no warranties, and confers no rights."Rush" <rasi...@gmail.com> wrote in message
>
> news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
>
>
>
> > Terminal Server Configured to NLB with Unicast.
> > Server functioning is working properly but when we connect to NETWORK
> > LOAD BALANCING MANAGER
> > When it try to other node it showed destination host unreachable,
> > error connecting to "2ndHOST NAME".
> > Can some one tell me what is missing here?- Hide quoted text -
>
> - Show quoted text -

Management interface ? You mean for heat beat ? Yes with a cross
cable . I can ping Private and Public IPs from each nodes.

The Ip config like this

***Node A

*NIC 1
10.198.X.18/24
GW 10.198.x.125
DNS 10.198.x.60

**NIC 2
60.60.60.60/24
GW none
DNS none


***Node B

*NIC1
10.198.X.19/24
GW 10.198.x.125
DNS 10.198.x.60

**NIC 2
60.60.60.61/24
GW none
DNS none

A 'common misperception' with NLB clusters. Heartbeats and crossover cables
do not apply to NLB Clusters...only to Server Clusters. So, I would connect
those second NICs to a switch, give them some addresses and use them as
Management interfaces for you NLB cluster.

--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.

"Rush" <rasikaf@gmail.com> wrote in message
news:1187747862.592540.24080@r23g2000prd.googlegroups.com...
> On Aug 21, 9:59 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
> wrote:
>> Do you have a second NIC configued as the management interface?
>>
>> --
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Windows Server 2008 Readiness Team
>> This posting is provided 'AS IS" with no warranties, and confers no
>> rights."Rush" <rasi...@gmail.com> wrote in message
>>
>> news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
>>
>>
>>
>> > Terminal Server Configured to NLB with Unicast.
>> > Server functioning is working properly but when we connect to NETWORK
>> > LOAD BALANCING MANAGER
>> > When it try to other node it showed destination host unreachable,
>> > error connecting to "2ndHOST NAME".
>> > Can some one tell me what is missing here?- Hide quoted text -
>>
>> - Show quoted text -
>
> Management interface ? You mean for heat beat ? Yes with a cross
> cable . I can ping Private and Public IPs from each nodes.
>
> The Ip config like this
>
> ***Node A
>
> *NIC 1
> 10.198.X.18/24
> GW 10.198.x.125
> DNS 10.198.x.60
>
> **NIC 2
> 60.60.60.60/24
> GW none
> DNS none
>
>
> ***Node B
>
> *NIC1
> 10.198.X.19/24
> GW 10.198.x.125
> DNS 10.198.x.60
>
> **NIC 2
> 60.60.60.61/24
> GW none
> DNS none
>
>
>

Thank you very much for the Answer. It makes sense to me. Instead of
management port Can I add additional connection (get removed from
Heartbeat) to same router which other port is connected and make a
Teaming and configure servers with NLB. This server is in Trusted and
users are connected by VPN. As this is in Trusted we can use to manage
from Trusted.


On Aug 22, 9:06 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
wrote:
> A 'common misperception' with NLB clusters. Heartbeats and crossover cables
> do not apply to NLB Clusters...only to Server Clusters. So, I would connect
> those second NICs to a switch, give them some addresses and use them as
> Management interfaces for you NLB cluster.
>
> --
> Chuck Timon, Jr.
> Microsoft Corporation
> Windows Server 2008 Readiness Team
> This posting is provided 'AS IS" with no warranties, and confers no rights.
>
> "Rush" <rasi...@gmail.com> wrote in message
>
> news:1187747862.592540.24080@r23g2000prd.googlegroups.com...
>
>
>
> > On Aug 21, 9:59 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
> > wrote:
> >> Do you have a second NIC configued as the management interface?
>
> >> --
> >> Chuck Timon, Jr.
> >> Microsoft Corporation
> >> Windows Server 2008 Readiness Team
> >> This posting is provided 'AS IS" with no warranties, and confers no
> >> rights."Rush" <rasi...@gmail.com> wrote in message
>
> >>news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
>
> >> > Terminal Server Configured to NLB with Unicast.
> >> > Server functioning is working properly but when we connect to NETWORK
> >> > LOAD BALANCING MANAGER
> >> > When it try to other node it showed destination host unreachable,
> >> > error connecting to "2ndHOST NAME".
> >> > Can some one tell me what is missing here?- Hide quoted text -
>
> >> - Show quoted text -
>
> > Management interface ? You mean for heat beat ? Yes with a cross
> > cable . I can ping Private and Public IPs from each nodes.
>
> > The Ip config like this
>
> > ***Node A
>
> > *NIC 1
> > 10.198.X.18/24
> > GW 10.198.x.125
> > DNS 10.198.x.60
>
> > **NIC 2
> > 60.60.60.60/24
> > GW none
> > DNS none
>
> > ***Node B
>
> > *NIC1
> > 10.198.X.19/24
> > GW 10.198.x.125
> > DNS 10.198.x.60
>
> > **NIC 2
> > 60.60.60.61/24
> > GW none
> > DNS none- Hide quoted text -
>
> - Show quoted text -

Make a connection to the switch using the NICs that had been connected via a
crossover cable, assign IP addresses and use those NICs for management. Do
not use NIC Teaming for NLB.....unless, of course, you like 'pain'. So, you
will be loading balancing VPN connections? Or, what service(s) are you load
balancing?

--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.

"Rush" <rasikaf@gmail.com> wrote in message
news:1187861535.380214.37930@x40g2000prg.googlegroups.com...
> Thank you very much for the Answer. It makes sense to me. Instead of
> management port Can I add additional connection (get removed from
> Heartbeat) to same router which other port is connected and make a
> Teaming and configure servers with NLB. This server is in Trusted and
> users are connected by VPN. As this is in Trusted we can use to manage
> from Trusted.
>
>
> On Aug 22, 9:06 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
> wrote:
>> A 'common misperception' with NLB clusters. Heartbeats and crossover
>> cables
>> do not apply to NLB Clusters...only to Server Clusters. So, I would
>> connect
>> those second NICs to a switch, give them some addresses and use them as
>> Management interfaces for you NLB cluster.
>>
>> --
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Windows Server 2008 Readiness Team
>> This posting is provided 'AS IS" with no warranties, and confers no
>> rights.
>>
>> "Rush" <rasi...@gmail.com> wrote in message
>>
>> news:1187747862.592540.24080@r23g2000prd.googlegroups.com...
>>
>>
>>
>> > On Aug 21, 9:59 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
>> > wrote:
>> >> Do you have a second NIC configued as the management interface?
>>
>> >> --
>> >> Chuck Timon, Jr.
>> >> Microsoft Corporation
>> >> Windows Server 2008 Readiness Team
>> >> This posting is provided 'AS IS" with no warranties, and confers no
>> >> rights."Rush" <rasi...@gmail.com> wrote in message
>>
>> >>news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
>>
>> >> > Terminal Server Configured to NLB with Unicast.
>> >> > Server functioning is working properly but when we connect to
>> >> > NETWORK
>> >> > LOAD BALANCING MANAGER
>> >> > When it try to other node it showed destination host unreachable,
>> >> > error connecting to "2ndHOST NAME".
>> >> > Can some one tell me what is missing here?- Hide quoted text -
>>
>> >> - Show quoted text -
>>
>> > Management interface ? You mean for heat beat ? Yes with a cross
>> > cable . I can ping Private and Public IPs from each nodes.
>>
>> > The Ip config like this
>>
>> > ***Node A
>>
>> > *NIC 1
>> > 10.198.X.18/24
>> > GW 10.198.x.125
>> > DNS 10.198.x.60
>>
>> > **NIC 2
>> > 60.60.60.60/24
>> > GW none
>> > DNS none
>>
>> > ***Node B
>>
>> > *NIC1
>> > 10.198.X.19/24
>> > GW 10.198.x.125
>> > DNS 10.198.x.60
>>
>> > **NIC 2
>> > 60.60.60.61/24
>> > GW none
>> > DNS none- Hide quoted text -
>>
>> - Show quoted text -
>
>

Thank you for your information. We are load balancing the entire 3389
load which coming for Terminal Server.
What we was looked for High availability for our Terminal Server. But
realize Majority Node Cluster doesn't fictional with Terminal servers
and thought NLB will be idle.
Enabled the Session Directory also. Anyway thank you very much for
your great help and its working fine now & highly appreciated.





On Aug 23, 9:33 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
wrote:
> Make a connection to the switch using the NICs that had been connected via a
> crossover cable, assign IP addresses and use those NICs for management. Do
> not use NIC Teaming for NLB.....unless, of course, you like 'pain'. So, you
> will be loading balancing VPN connections? Or, what service(s) are you load
> balancing?
>
> --
> Chuck Timon, Jr.
> Microsoft Corporation
> Windows Server 2008 Readiness Team
> This posting is provided 'AS IS" with no warranties, and confers no rights.
>
> "Rush" <rasi...@gmail.com> wrote in message
>
> news:1187861535.380214.37930@x40g2000prg.googlegroups.com...
>
>
>
> > Thank you very much for the Answer. It makes sense to me. Instead of
> > management port Can I add additional connection (get removed from
> > Heartbeat) to same router which other port is connected and make a
> > Teaming and configure servers with NLB. This server is in Trusted and
> > users are connected by VPN. As this is in Trusted we can use to manage
> > from Trusted.
>
> > On Aug 22, 9:06 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
> > wrote:
> >> A 'common misperception' with NLB clusters. Heartbeats and crossover
> >> cables
> >> do not apply to NLB Clusters...only to Server Clusters. So, I would
> >> connect
> >> those second NICs to a switch, give them some addresses and use them as
> >> Management interfaces for you NLB cluster.
>
> >> --
> >> Chuck Timon, Jr.
> >> Microsoft Corporation
> >> Windows Server 2008 Readiness Team
> >> This posting is provided 'AS IS" with no warranties, and confers no
> >> rights.
>
> >> "Rush" <rasi...@gmail.com> wrote in message
>
> >>news:1187747862.592540.24080@r23g2000prd.googlegroups.com...
>
> >> > On Aug 21, 9:59 pm, "Chuck [MSFT]" <cti...@online.microsoft.com>
> >> > wrote:
> >> >> Do you have a second NIC configued as the management interface?
>
> >> >> --
> >> >> Chuck Timon, Jr.
> >> >> Microsoft Corporation
> >> >> Windows Server 2008 Readiness Team
> >> >> This posting is provided 'AS IS" with no warranties, and confers no
> >> >> rights."Rush" <rasi...@gmail.com> wrote in message
>
> >> >>news:1187686558.427811.50500@x40g2000prg.googlegroups.com...
>
> >> >> > Terminal Server Configured to NLB with Unicast.
> >> >> > Server functioning is working properly but when we connect to
> >> >> > NETWORK
> >> >> > LOAD BALANCING MANAGER
> >> >> > When it try to other node it showed destination host unreachable,
> >> >> > error connecting to "2ndHOST NAME".
> >> >> > Can some one tell me what is missing here?- Hide quoted text -
>
> >> >> - Show quoted text -
>
> >> > Management interface ? You mean for heat beat ? Yes with a cross
> >> > cable . I can ping Private and Public IPs from each nodes.
>
> >> > The Ip config like this
>
> >> > ***Node A
>
> >> > *NIC 1
> >> > 10.198.X.18/24
> >> > GW 10.198.x.125
> >> > DNS 10.198.x.60
>
> >> > **NIC 2
> >> > 60.60.60.60/24
> >> > GW none
> >> > DNS none
>
> >> > ***Node B
>
> >> > *NIC1
> >> > 10.198.X.19/24
> >> > GW 10.198.x.125
> >> > DNS 10.198.x.60
>
> >> > **NIC 2
> >> > 60.60.60.61/24
> >> > GW none
> >> > DNS none- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -