| Author |
Message |
xmarcuz
Guest
|
 Posted:
Mon Jan 10, 2005 2:12 pm Post subject:
Nlb with 2 nework card |
|
|
i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks |
|
| Back to top |
|
 |
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Mon Jan 10, 2005 6:41 pm Post subject:
Re: Nlb with 2 nework card |
|
|
For NLB to work, you should have two different networks. One for the Public
and for the private. What settings are you using?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:9940C1B1-4951-4C70-86C2-D68E71246471@microsoft.com...
| Quote: | i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect
each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks |
|
|
| Back to top |
|
|
xmarcuz
Guest
|
| Posted:
Mon Jan 10, 2005 7:03 pm Post subject:
Re: Nlb with 2 nework card |
|
|
172.16.6.x public (nlb checked in network proprieties)
10.1.1.x private (nlb not checked)
"Rodney R. Fournier [MVP]" wrote:
| Quote: | For NLB to work, you should have two different networks. One for the Public
and for the private. What settings are you using?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:9940C1B1-4951-4C70-86C2-D68E71246471@microsoft.com...
i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect
each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks
|
|
|
| Back to top |
|
|
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Mon Jan 10, 2005 8:57 pm Post subject:
Re: Nlb with 2 nework card |
|
|
That should work nicely, make sure you have the same settings on both
computers. Does it converge?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:CEF2A134-6928-41DA-942B-A0702C4E5C97@microsoft.com...
| Quote: | 172.16.6.x public (nlb checked in network proprieties)
10.1.1.x private (nlb not checked)
"Rodney R. Fournier [MVP]" wrote:
For NLB to work, you should have two different networks. One for the
Public
and for the private. What settings are you using?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:9940C1B1-4951-4C70-86C2-D68E71246471@microsoft.com...
i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect
each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks
|
|
|
| Back to top |
|
|
xmarcuz
Guest
|
| Posted:
Mon Jan 10, 2005 9:09 pm Post subject:
Re: Nlb with 2 nework card |
|
|
they converge and the client connect to cluster ip, but i can't ping from the
first server (public interface) to the second and vice versa.
I read that the interface used for load balncing cannot be used for network
traffic between server in the farm.
for example if i want to know how many user are in each server i must
connect to each server or connect to another server p.e. my domain controller.
There isn't a better solution: the two network card in the same network for
example could be better?
Thanks
Marco
"Rodney R. Fournier [MVP]" wrote:
| Quote: | That should work nicely, make sure you have the same settings on both
computers. Does it converge?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:CEF2A134-6928-41DA-942B-A0702C4E5C97@microsoft.com...
172.16.6.x public (nlb checked in network proprieties)
10.1.1.x private (nlb not checked)
"Rodney R. Fournier [MVP]" wrote:
For NLB to work, you should have two different networks. One for the
Public
and for the private. What settings are you using?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:9940C1B1-4951-4C70-86C2-D68E71246471@microsoft.com...
i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect
each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks
|
|
|
| Back to top |
|
|
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Mon Jan 10, 2005 9:15 pm Post subject:
Re: Nlb with 2 nework card |
|
|
That is what your 10.x.x.x network is for. You should try and use that for
management.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:61A8B85C-8270-40AD-879D-D449FB530A2C@microsoft.com...
| Quote: | they converge and the client connect to cluster ip, but i can't ping from
the
first server (public interface) to the second and vice versa.
I read that the interface used for load balncing cannot be used for
network
traffic between server in the farm.
for example if i want to know how many user are in each server i must
connect to each server or connect to another server p.e. my domain
controller.
There isn't a better solution: the two network card in the same network
for
example could be better?
Thanks
Marco
"Rodney R. Fournier [MVP]" wrote:
That should work nicely, make sure you have the same settings on both
computers. Does it converge?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:CEF2A134-6928-41DA-942B-A0702C4E5C97@microsoft.com...
172.16.6.x public (nlb checked in network proprieties)
10.1.1.x private (nlb not checked)
"Rodney R. Fournier [MVP]" wrote:
For NLB to work, you should have two different networks. One for the
Public
and for the private. What settings are you using?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"xmarcuz" <xmarcuz@discussions.microsoft.com> wrote in message
news:9940C1B1-4951-4C70-86C2-D68E71246471@microsoft.com...
i've 3 terminal server (w2003 ent session directory)
For the terminal server here is the configuration
Server name 1st network 2nd network
TS1 172.16.6.10 10.1.1.1
ts2 172.16.6.11 10.1.1.2
ts3 172.16.6.12 10.1.1.3
Cluster name TS
Cluster ip 172.16.6.20
The client can connect to the server, but the server can't connect
each-other
I think there is a better configuration.
For you is better to have the two network card in the same network?
example
Server name 1st network 2nd network
TS1 172.16.6.10 172.16.6.30
ts2 172.16.6.11 172.16.6.31
ts3 172.16.6.12 172.16.6.32
thanks
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in