Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
Hi,
I have 5 Windows 2003 Servers Enterprise. I've setup nlb on them. But it's causing issues with remote sites trying to access. Is possible to set up a single server and have users connect to that and have that server distribute connections to the cluster accordingly?
Right now, all the servers in the cluster has a single virtual ip that users hit. All users can hit each server unique IP but not everyone can hit the cluster IP.
Page 1 of 1
Question on NLB Clustering
Rate Topic:
Back to top
#2
- Gustatus similis pullus
-
- Group: Supervisor
- Posts: 10,937
- Joined: 09-September 01
- OS:Windows 7 x64
-
Country:
-
Posted 01 October 2009 - 12:00 PM
What are you load-balancing, specifically? Is it NLB for IIS, or something else?
#3
- Member
-
- Group: Members
- Posts: 127
- Joined: 09-August 06
Posted 02 October 2009 - 08:10 AM
Sorry, should've been more specific.
Load balancing terminal servers. We have 5 of them.
Load balancing terminal servers. We have 5 of them.
#4
- Gustatus similis pullus
-
- Group: Supervisor
- Posts: 10,937
- Joined: 09-September 01
- OS:Windows 7 x64
-
Country:
-
Posted 02 October 2009 - 08:54 AM
How is session directory configured and installed? It sounds like that portion of your TS farm isn't performing properly if users can't RDP to it properly and then get redirected to a farm host, or perhaps there are switch issues preventing your remote clients from hitting the NLB IP address and forwarding to the "real" server.
#5
- How do you like your Chili?
-
- Group: Members
- Posts: 995
- Joined: 16-February 05
Posted 02 October 2009 - 11:10 AM
I dont remember the exact scenario, but our remote locations could not connect using the NLB IP to our web servers. As it turned out it was a problem with arp resolutions and we had to make a static entry in our routers to map the addres.
Here is the command for a cisco router
arp [IP Address] [MAC Address ARPA]
so that would be like
arp 192.168.0.1 03bf.5900.641e ARPA
Like I said.. I dont remember the exact reasoning for this anymore. i would have to look it back up.. but the scenario was the same. Everyone could hit each individual IP but only the local clients could connect to the NLB IP
Here is the command for a cisco router
arp [IP Address] [MAC Address ARPA]
so that would be like
arp 192.168.0.1 03bf.5900.641e ARPA
Like I said.. I dont remember the exact reasoning for this anymore. i would have to look it back up.. but the scenario was the same. Everyone could hit each individual IP but only the local clients could connect to the NLB IP
#6
- Member
-
- Group: Members
- Posts: 127
- Joined: 09-August 06
Posted 08 October 2009 - 07:35 PM
chilifrei64, on Oct 2 2009, 01:10 PM, said:
I dont remember the exact scenario, but our remote locations could not connect using the NLB IP to our web servers. As it turned out it was a problem with arp resolutions and we had to make a static entry in our routers to map the addres.
Here is the command for a cisco router
arp [IP Address] [MAC Address ARPA]
so that would be like
arp 192.168.0.1 03bf.5900.641e ARPA
Like I said.. I dont remember the exact reasoning for this anymore. i would have to look it back up.. but the scenario was the same. Everyone could hit each individual IP but only the local clients could connect to the NLB IP
Here is the command for a cisco router
arp [IP Address] [MAC Address ARPA]
so that would be like
arp 192.168.0.1 03bf.5900.641e ARPA
Like I said.. I dont remember the exact reasoning for this anymore. i would have to look it back up.. but the scenario was the same. Everyone could hit each individual IP but only the local clients could connect to the NLB IP
This is what we had to do to get it resolved as well.
thanks for the input people.
- ← Any good remote access free software?
- Windows NT4/2000/2003
- vrfydsk error windows server 2003 64 bit →
Share this topic:
Page 1 of 1