Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 218
  • Last Modified:

Problems connecting to Cluster, connection ok with individual servers... 500 points


I have 2 PowerEdge 2950 connected to a PowerVault storage center.
Each terminal server is names TS01 and TS02.  I have joined these computers to the domain, and I am using NLB to build our cluster.
I am working also to implement Session Directory Services to get these fully operation.  And I may need some future help on this, but my biggest concern is why I can't connect to my cluster via RDP going to the host CS01.domain.com.
It is not a problem to get to each individual server via their Computer Name (TS01 or TS02).

The cluster is built utilizing 2 NIC in each server.  One management NIC and one Cluster NIC.
The TS01 Cluster network interface has IP 192.168.0.41/24 with gateway .1 and DNS 192.168.0.2
The TS01 Management NIC utilizes IP 192.168.168.1 with no gateway or DNS settings and has "File and Print Sharing" unchecked and "Client for Microsoft Networks" unchecked per Microsoft's Technical Documentation to nic setup on a cluster.  This NIC has a crossover cable connecting it to the TS02 Management NIC

The TS02 is configured in the same way as TS01...
The TS02 Cluster NIC has IP 192.168.0.42/24 with gateway .1 and DNS 192.168.0.2
The TS02 Management NIC has IP 192.168.168.2 configured like TS01 and connected to TS01 management NIC with the crossover cable mentioned.

The cluster was setup via NLB manager.  Unicast support and all default settings.
The cluster name is cs01.domain.com with IP address 192.168.0.40

The DNS server is verified to have the correct settings as far as I can see with CS01 with an A record to 192.168.0.40

I hope I have posted enough information, but feel free to ask further questions.

Thank you.
0
weblinktech
Asked:
weblinktech
  • 2
  • 2
1 Solution
 
oBdACommented:
You're mixing Cluster Services and Network Load Balancing. Those have nothing in common, in fact, they're mutually exclusive.
Check here on how to load balance terminal servers using NLB:

Network Load Balancing : Configuration Best Practices for Windows 2000 and Windows Server 2003
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/nlbbp.mspx

Network Load Balancing Frequently Asked Questions
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/clustering/nlbfaq.mspx

Load balancing and terminal servers
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/6a9b9e6e-e967-45a0-a2a3-9fece12b7cef.mspx

NLB Troubleshooting Overview for Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyId=9E6F4999-AEEB-40CF-867B-AF68742FFFDC&displaylang=en
0
 
weblinktechAuthor Commented:
I have gone through these articles already.

This does not assist my problem unfortunately.
0
 
weblinktechAuthor Commented:

The problem here was that I was teaming my NICs.
Once I removed this, Everything was fine.

No points should be awarded on this issue.
We were not assisted in anyway except to call Microsoft and have them work us through this issue.
0
 
oBdACommented:
JFTR: The Troubleshooting Guide specifically addresses NIC teaming and NLB.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now