| Author |
Message |
Marlon Brown
Guest
|
 Posted:
Fri Jan 14, 2005 4:06 am Post subject:
Newbie NLB - Ping times out - please help |
|
|
I have two Win2003 Ent. Server boxes. I follow the configuration below. From
Server1 I am able to ping the private IP address of the Server2 OK.
From my workstation I can ping both Server1 and Server IP addresses.
However, ping to <virtualIP=163.7.9.5> times out.
Also, I notice that I have Termina Services installed on both servers, but
as soon as I enable the "Network Load Balance", I can't connect to those
servers anymore via TS. What's wrong ?
) Imagine I have two identical servers, Two NIC's per server.
Nic1Server1Public I will input my public IP address, let's 163.7.9.x. Then
on that Network Adapter properties I select "Network Load Balancing". I
click advance and input "ClusterIPAddress = 163.7.9.5".
b) I go to Nic1Server2Public I will input my public IP address, let's
163.7.91. Then on that Network Adapter properties I select "Network Load
Balancing". I click advance and input "ClusterIPAddress", it should be one
that I used on the other server = 163.7.9.5".
Then I put a crossover cable between the two servers and configure
PrivateNIC's respectively as something like 192.168.0.1 and on the other
server PrivateNIC = 192.168.0.2. |
|
| Back to top |
|
 |
Gerald Aigenbauer
Guest
|
| Posted:
Fri Jan 14, 2005 6:19 pm Post subject:
Re: Newbie NLB - Ping times out - please help |
|
|
hi marlon!
have you implemented a port rule for the terminal server rdp-port in the nlb
cluster? is there any port-rule?
gerald aigenbauer.
"Marlon Brown" <marlon_brown@hotmail.com> schrieb im Newsbeitrag
news:%23AUARvb%23EHA.3700@tk2msftngp13.phx.gbl...
| Quote: | I have two Win2003 Ent. Server boxes. I follow the configuration below.
From
Server1 I am able to ping the private IP address of the Server2 OK.
From my workstation I can ping both Server1 and Server IP addresses.
However, ping to <virtualIP=163.7.9.5> times out.
Also, I notice that I have Termina Services installed on both servers, but
as soon as I enable the "Network Load Balance", I can't connect to those
servers anymore via TS. What's wrong ?
) Imagine I have two identical servers, Two NIC's per server.
Nic1Server1Public I will input my public IP address, let's 163.7.9.x. Then
on that Network Adapter properties I select "Network Load Balancing". I
click advance and input "ClusterIPAddress = 163.7.9.5".
b) I go to Nic1Server2Public I will input my public IP address, let's
163.7.91. Then on that Network Adapter properties I select "Network Load
Balancing". I click advance and input "ClusterIPAddress", it should be one
that I used on the other server = 163.7.9.5".
Then I put a crossover cable between the two servers and configure
PrivateNIC's respectively as something like 192.168.0.1 and on the other
server PrivateNIC = 192.168.0.2.
|
|
|
| Back to top |
|
|
Marlon Brown
Guest
|
| Posted:
Fri Jan 14, 2005 10:53 pm Post subject:
Re: Newbie NLB - Ping times out - please help |
|
|
This setup is not working. WLBS query <IP> fails.
In the NIC-Public where I select "Network Load Balancing", I also configured
TCP/IP Properties and I input an unique static IP for each server. This is
the complete configuration. What am I doing wrong ?
Server 1 NIC 1 (Public)
TCP/IP Properties=174.6.6.1/24
NLB Cluster IP Address IP=174.6.6.7/24
Clustername (input on internal DNS server as)=myowa.mydomain.com
Unicast, no remote control configuration, no Dedicated IP
Server 1 NIC 2
TCP/IP Properties=192.168.1.3/24 (No DNS, No default gateway config)
Server 2 NIC 1 (Public)
TCP/IP Properties=174.6.6.2/24
NLB Cluster IP Address IP=174.6.6.7/24
Clustername (input on internal DNS server as)=myowa.mydomain.com
Unicast, no remote control configuration, no Dedicated IP
Server 2 NIC 2
TCP/IP Properties=192.168.1.4/24 (No DNS, No default gateway config)
"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:%23LyP3Mj%23EHA.2104@TK2MSFTNGP14.phx.gbl...
| Quote: | hi marlon!
have you implemented a port rule for the terminal server rdp-port in the
nlb
cluster? is there any port-rule?
gerald aigenbauer.
"Marlon Brown" <marlon_brown@hotmail.com> schrieb im Newsbeitrag
news:%23AUARvb%23EHA.3700@tk2msftngp13.phx.gbl...
I have two Win2003 Ent. Server boxes. I follow the configuration below.
From
Server1 I am able to ping the private IP address of the Server2 OK.
From my workstation I can ping both Server1 and Server IP addresses.
However, ping to <virtualIP=163.7.9.5> times out.
Also, I notice that I have Termina Services installed on both servers,
but
as soon as I enable the "Network Load Balance", I can't connect to those
servers anymore via TS. What's wrong ?
) Imagine I have two identical servers, Two NIC's per server.
Nic1Server1Public I will input my public IP address, let's 163.7.9.x.
Then
on that Network Adapter properties I select "Network Load Balancing". I
click advance and input "ClusterIPAddress = 163.7.9.5".
b) I go to Nic1Server2Public I will input my public IP address, let's
163.7.91. Then on that Network Adapter properties I select "Network Load
Balancing". I click advance and input "ClusterIPAddress", it should be
one
that I used on the other server = 163.7.9.5".
Then I put a crossover cable between the two servers and configure
PrivateNIC's respectively as something like 192.168.0.1 and on the other
server PrivateNIC = 192.168.0.2.
|
|
|
| Back to top |
|
|
Ryan Sokolowski [Avanade]
Guest
|
| Posted:
Sat Jan 15, 2005 8:10 am Post subject:
Re: Newbie NLB - Ping times out - please help |
|
|
Marlon - I replied to another of your posts with this, but here is a
document that I wrote that may help you step-by-step:
Follow these directions for simplicity - This is a document I wrote a year
or so ago and it should apply to both Windows 2000 and Windows Server 2003.
How-To: Configure Network Load Balancing (NLB) with Two Network Adapters
1.. Assign appropriate IP addresses to each NIC, placing them in separate
subnets.
· Node1 -
o "Public" NIC
§ IP address: 10.10.2.17
§ Subnet: 255.255.255.0
§ Gateway: 10.10.2.1
§ DNS: as appropriate
o "NLB" NIC
§ IP address: 192.168.1.1
§ Subnet: 255.255.255.0
§ Gateway: N/A
§ DNS: N/A
· Node2 -
o "Public" NIC
§ IP address: 10.10.2.18
§ Subnet: 255.255.255.0
§ Gateway: 10.10.2.1
§ DNS: as appropriate
o "NLB" NIC
§ IP address: 192.168.1.2
§ Subnet: 255.255.255.0
§ Gateway: N/A
§ DNS: N/A
2.. On the "Public" NICs, click "Advanced" and add an additional IP
address as the Virtual IP Address which clients will connect to from the
Public network (i.e. - 10.10.2.177)
3.. Install "Network Load Balancing" as an additional service from the
"Public" adapter properties.
a.. Click "Install.." and then select "Service" in the upper-window and
click "Add."
b.. Select "Network Load Balancing" in the upper-window and click "OK"
c.. Answer any prompts and provide the correct path to installation
media.
4.. Once NLB is installed, return to the Properties page for the "Public"
NIC and select the check-box next to "Network Load Balancing." This enables
the service globally.
5.. Next, select the item "Network Load Balancing" and click "Properties"
6.. Configure the NLB Cluster properties according to your parameters,
using the following example steps as a guide.
· Node1 -
o "Public" NLB Cluster Parameters tab
§ Primary IP address: 10.10.2.177
§ Subnet: 255.255.255.0
§ Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
§ Priority: 1
§ Dedicated IP address: 10.10.2.17
§ Subnet: 255.255.255.0
· Node2 -
o "Public" NLB Cluster Parameters tab
§ Primary IP address: 10.10.2.177
§ Subnet: 255.255.255.0
§ Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
§ Priority: 2
§ Dedicated IP address: 10.10.2.18
§ Subnet: 255.255.255.0
7.. MultiCast support can be optional in this configuration.
8.. You can also now take time to create a static Host record (A record)
in your scenario's DNS infrastructure to provide appropriate name resolution
to the NLB cluster name (i.e. - mail.domain.com or just mail).
9.. Your NLB cluster should be up and running.
10.. An external client should now be able to ping the IP address of the
NLB cluster (i.e. - 10.10.2.177) as well as each of the individual node
addresses (i.e. - 10.10.2.17 & -.18).
11.. Many good diagnostic commands can be found by typing "wlbs /?" in a
command window. For example, "wlbs query" shows the status and convergence
state of the cluster.
12.. IMPORTANT NOTE: In this configuration, each individual node is NOT
able to ping the other node's Public physical IP address (i.e - 10.10.2.17
cannot ping 10.10.2.18 and vice-versa). I believe this is expected
behavior, as the NLB cluster is now responding to requests on the Virtual
Cluster address (i.e. - 10.10.2.177).
--
Ryan Sokolowski
MCSE, CCNA, CCDA, BCFP
Avanade
http://www.Avanade.com
"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marlon Brown" <marlon_brown@hotmail.com> wrote in message
news:%23UiQ1kl%23EHA.2076@TK2MSFTNGP15.phx.gbl...
| Quote: | This setup is not working. WLBS query <IP> fails.
In the NIC-Public where I select "Network Load Balancing", I also
configured
TCP/IP Properties and I input an unique static IP for each server. This is
the complete configuration. What am I doing wrong ?
Server 1 NIC 1 (Public)
TCP/IP Properties=174.6.6.1/24
NLB Cluster IP Address IP=174.6.6.7/24
Clustername (input on internal DNS server as)=myowa.mydomain.com
Unicast, no remote control configuration, no Dedicated IP
Server 1 NIC 2
TCP/IP Properties=192.168.1.3/24 (No DNS, No default gateway config)
Server 2 NIC 1 (Public)
TCP/IP Properties=174.6.6.2/24
NLB Cluster IP Address IP=174.6.6.7/24
Clustername (input on internal DNS server as)=myowa.mydomain.com
Unicast, no remote control configuration, no Dedicated IP
Server 2 NIC 2
TCP/IP Properties=192.168.1.4/24 (No DNS, No default gateway config)
"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:%23LyP3Mj%23EHA.2104@TK2MSFTNGP14.phx.gbl...
hi marlon!
have you implemented a port rule for the terminal server rdp-port in the
nlb
cluster? is there any port-rule?
gerald aigenbauer.
"Marlon Brown" <marlon_brown@hotmail.com> schrieb im Newsbeitrag
news:%23AUARvb%23EHA.3700@tk2msftngp13.phx.gbl...
I have two Win2003 Ent. Server boxes. I follow the configuration below.
From
Server1 I am able to ping the private IP address of the Server2 OK.
From my workstation I can ping both Server1 and Server IP addresses.
However, ping to <virtualIP=163.7.9.5> times out.
Also, I notice that I have Termina Services installed on both servers,
but
as soon as I enable the "Network Load Balance", I can't connect to
those
servers anymore via TS. What's wrong ?
) Imagine I have two identical servers, Two NIC's per server.
Nic1Server1Public I will input my public IP address, let's 163.7.9.x.
Then
on that Network Adapter properties I select "Network Load Balancing". I
click advance and input "ClusterIPAddress = 163.7.9.5".
b) I go to Nic1Server2Public I will input my public IP address, let's
163.7.91. Then on that Network Adapter properties I select "Network
Load
Balancing". I click advance and input "ClusterIPAddress", it should be
one
that I used on the other server = 163.7.9.5".
Then I put a crossover cable between the two servers and configure
PrivateNIC's respectively as something like 192.168.0.1 and on the
other
server PrivateNIC = 192.168.0.2.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in