Link to home
Start Free TrialLog in
Avatar of victory2201
victory2201

asked on

NLB - Session Host Configuration

Hello,

We recently purchased a Barracuda LB 340Vx for our terminal server load balancing.

I have configured the unit based on the guidelines provided in this link.

The load balancing feature is working as it should, however there is a quirky problem I am seeing upon initial connection. When I enter the Virtual IP address for the LB, it directs me to a server in the farm, then redirect's me again to another farm server before allowing me to log on.

Once I get logged on, I can reconnect with the same user from another machine and reopen the same session, as intended.

Example:

- Open mstsc.exe
- Connect to : x.x.x.x
- Shows connecting to Srvr1. Accept unregistered cert.
- Now points me to Srvr2 or Srvr3, accept again and we connect to the second server.


Any help that can be provided would be great.

Thanks!
Avatar of Mahesh
Mahesh
Flag of India image

So, what you mean is you are connecting to LB VIP and redirected to one server and actually get connected to another server ?

Have you configured session directory server in your environment ?
Avatar of victory2201
victory2201

ASKER

Correct. Its seems to be functioning as intended, since the LB is assigning sessions to each server accordingly. The cert acceptance screen was triggering twice for each server after it redirected a second time.

After further investigation, I noticed this was happening when it tried to hit a server with more current sessions then another.

I was able to get around this prompt by going into the settings for Remote Desktop and changing the advanced value under server authentication to "Connect and don't warn me".

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Mahesh, thank you for your assistance. All is working well now. :)

(And yes, I have already assigned a static entry in DNS for the VIP)