|
Home > Archive > Application Center Setup > November 2005 > Terminal Server and NLB
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Terminal Server and NLB
|
|
| PeisaNet 2005-10-11, 7:52 am |
| We are testing NLB. We have two Terminal Servers with W2K3 Enterprise Edition
with two networks interfaces each.
The configuration is as follows:
Server 1
----------
NIC1: IP - 192.2.104.201
Mask - 255.255.255.0
Gateway -
DNS -
Cluster Parameters:
Cluster IP - 192.2.104.230
Mask - 255.255.255.0
Cluster Operation Mode - Unicast
Dedicated IP:
IP- 192.2.104.201
Mask- 255.255.255.0
In TCP/IP Properties-Advanced we have added the 192.2.104.230 ip.
NIC2: IP - 10.0.0.1
Mask - 255.255.255.0
Gateway -
DNS -
Network Load Balancing not activated.
Server 2
----------
NIC1: IP - 192.2.104.202
Mask - 255.255.255.0
Gateway -
DNS -
Cluster Parameters:
Cluster IP - 192.2.104.230
Mask - 255.255.255.0
Cluster Operation Mode - Unicast
Dedicated IP:
IP- 192.2.104.202
Mask- 255.255.255.0
In TCP/IP Properties-Advanced we have added the 192.2.104.230 ip.
NIC2: IP - 10.0.0.2
Mask - 255.255.255.0
Gateway -
DNS -
Network Load Balancing not activated.
We have no Active Directory configurated, no DNS, four network cards are on
the same switch.
We use Network Load Balance Manager to see the cluster and the two servers
are converged. But we cannot ping the VIP either each dedicated IP address.
In fact once we add one host to the cluster, we cannot reach the other one,
we have to complete the cluster over the other NIC (NIC2).
We suppose that in order to connect the clients through Remote Desktop
Connection we have to use the Virtual IP address 192.2.104.30 to reach the
cluster, is this correct?
The only thing is when we make a nlb display, it shows a problem with NDIS
and ask us to update the NIC driver. We have the latest driver and the
network card is a RTL8139.
We think we have something bad configured, any help would be appreciate.
Thanks in advanced.
| |
| Richard Ault [MSFT] 2005-11-21, 5:51 pm |
| You might have better luck in windows nlb or terminal server newsgroups.
--
Richard Ault
Application Center Product Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"PeisaNet" <PeisaNet@discussions.microsoft.com> wrote in message
news:47D863D3-BFA5-4F00-BE3C-9F048F2278A5@microsoft.com...
> We are testing NLB. We have two Terminal Servers with W2K3 Enterprise
> Edition
> with two networks interfaces each.
> The configuration is as follows:
> Server 1
> ----------
> NIC1: IP - 192.2.104.201
> Mask - 255.255.255.0
> Gateway -
> DNS -
> Cluster Parameters:
> Cluster IP - 192.2.104.230
> Mask - 255.255.255.0
> Cluster Operation Mode - Unicast
> Dedicated IP:
> IP- 192.2.104.201
> Mask- 255.255.255.0
> In TCP/IP Properties-Advanced we have added the 192.2.104.230
> ip.
> NIC2: IP - 10.0.0.1
> Mask - 255.255.255.0
> Gateway -
> DNS -
> Network Load Balancing not activated.
> Server 2
> ----------
> NIC1: IP - 192.2.104.202
> Mask - 255.255.255.0
> Gateway -
> DNS -
> Cluster Parameters:
> Cluster IP - 192.2.104.230
> Mask - 255.255.255.0
> Cluster Operation Mode - Unicast
> Dedicated IP:
> IP- 192.2.104.202
> Mask- 255.255.255.0
> In TCP/IP Properties-Advanced we have added the 192.2.104.230
> ip.
> NIC2: IP - 10.0.0.2
> Mask - 255.255.255.0
> Gateway -
> DNS -
> Network Load Balancing not activated.
>
> We have no Active Directory configurated, no DNS, four network cards are
> on
> the same switch.
>
> We use Network Load Balance Manager to see the cluster and the two servers
> are converged. But we cannot ping the VIP either each dedicated IP
> address.
> In fact once we add one host to the cluster, we cannot reach the other
> one,
> we have to complete the cluster over the other NIC (NIC2).
>
> We suppose that in order to connect the clients through Remote Desktop
> Connection we have to use the Virtual IP address 192.2.104.30 to reach the
> cluster, is this correct?
>
> The only thing is when we make a nlb display, it shows a problem with NDIS
> and ask us to update the NIC driver. We have the latest driver and the
> network card is a RTL8139.
>
> We think we have something bad configured, any help would be appreciate.
>
> Thanks in advanced.
|
|
|
|
|