+ Post New Thread
Results 1 to 4 of 4
Internet Related/Filtering/Firewall Thread, Smoothwall & NLB Connection Broker in Technical; Hi, We are using smoothwall and it is working perfectly with our single terminal server 2008 R2 to provide connectivity ...
  1. #1

    Join Date
    Apr 2012
    Thank Post
    Thanked 1 Time in 1 Post
    Rep Power

    Smoothwall & NLB Connection Broker


    We are using smoothwall and it is working perfectly with our single terminal server 2008 R2 to provide connectivity to staff at home. Our smoothwall is setup with a forward rule of:

    Source port 60000 Destination port 3389 external ip any internal ip "internal ip of our rds server"

    We have recently added a second terminal server and are trying to load balance between the two. We can get it working fine internally with no problems at all but of course the issues arise when we try it from outside. The first connection is OK as it is sending it to our first server which smoothwall has a port forward rule to recognise, it is the second connection that is the issue because when it tries to forward it on to the other server it loses the connection.

    Is there anyway around this without having to add a second port forward rule to make this second server visible from the internet? I have looked into token redirection in session host but not sure whether this is the right way to do it.

    If anyone has managed to make this work through smoothwall please could you let me know how you did it? I have also tried adding duplicate port forward rules to load balance through smoothwall but this doesn't work either.


  2. #2

    john's Avatar
    Join Date
    Sep 2005
    Thank Post
    Thanked 1,069 Times in 934 Posts
    Rep Power
    Have you not got the TS Load Balancer internally? That way you point people at the balancer and it sorts it out for itself I believe but maybe I misunderstood how that works?

  3. #3

    Join Date
    Feb 2007
    Thank Post
    Thanked 807 Times in 722 Posts
    Rep Power
    I'd set up an RDS Gateway with Connection Broker and point your Smoothwall rule to that (using port 443) and it will deal with the load balancing of the internal remote desktop services servers for you.

    From the outside you hit the RDS Gateway and it deals with which RD server you land on internally.
    Last edited by kmount; 18th June 2014 at 03:16 PM.

  4. #4

    Ephelyon's Avatar
    Join Date
    Aug 2008
    Cheshire, England
    Thank Post
    Thanked 392 Times in 249 Posts
    Rep Power
    Here's a good guide on getting an NLB IP set up on both boxes; you could then just tell SmoothWall to forward to that "virtual IP":

    Setting up NLB on Windows Server 2008 R2 | bretty.me.uk

+ Post New Thread

Similar Threads

  1. Windows Server 2008 R2 RDS Connection Broker and HP thin clients
    By localzuk in forum Thin Client and Virtual Machines
    Replies: 10
    Last Post: 15th January 2013, 10:49 AM
  2. Server 2008 RD Connection broker - preferred server
    By Lee_K_81 in forum Windows Server 2008 R2
    Replies: 8
    Last Post: 27th December 2012, 05:52 PM
  3. Smoothwall Express 3 refusing connections
    By dgsmith in forum Internet Related/Filtering/Firewall
    Replies: 6
    Last Post: 30th September 2010, 02:34 PM
  4. Smoothwall Crippling with >30 connections
    By farquea in forum Internet Related/Filtering/Firewall
    Replies: 3
    Last Post: 20th June 2009, 12:50 AM
  5. Replies: 1
    Last Post: 25th January 2009, 07:31 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts