cancel
Showing results for 
Search instead for 
Did you mean: 

LTM load balance for printing

Henry_Lau
Nimbostratus
Nimbostratus

We just configured F5 for printing load balance(standard VS, Not DSR). Loopback adoptors have been installed in 2 printer servers and run the netsh on interfaces.

netsh interface ipv4 set interface "Ethernet1" weakhostreceive=enabled

netsh interface ipv4 set interface "Loopback" weakhostreceive=enabled

netsh interface ipv4 set interface "Loopback" weakhostsend=enabled

 

Server registry DisableLoopbackCheck=1 has been done

 

Installed the same print queue to both print servers

 

All print queues can be browsed but not able to connect to and returned windows 0000079 errors.

 

Is it the problem on the LTM configurations? or missing something in print servers?

3 REPLIES 3

PeteWhite
F5 Employee
F5 Employee

You're going to have to provide more information than this - I suggest you start by looking at statistics to see whether the VS is being used and traffic sent to the backend server. If this doesn't show anything then you can run tcpdump to see the actual data being sent and you should be able to trace whether the issue is with LTM or not.

Henry_Lau
Nimbostratus
Nimbostratus

LTM can handle the 445 & 135 but not the Windows printing dynamic ports range 49152-65535

 

10.x.x.x(my pc IP):60450 10.x.x.x(LTM VIP):445 10.x.x.x(LTM VIP):60450 10.x.x.x(print server IP):445 tcp 0 (tmm:1) none

 

10.x.x.x(my pc IP):60488 10.x.x.x(LTM VIP):49162 10.x.x.x(my pc IP):60488 10.x.x.x(LTM VIP):49162 tcp 1 (tmm:0) none

 

LTM has been configured with the port 135 & 445 only. Does it require to config more ports in LTM?

ltm pool xxxxx_135 {

  description "xxxxx"

  members {

    printserver1_10.x.x.A:epmap {

      address 10.x.x.A

      description "xxxxx"

      session monitor-enabled

      state up

    }

    printserver2_10.x.x.B:epmap {

      address 10.x.x.B

      session monitor-enabled

      state up

    }

  }

  monitor tcp

}

ltm pool xxxxx_445 {

  description "xxxxx"

  members {

    printserver1_10.x.x.A:microsoft-ds {

      address 10.x.x.A

      description "xxxxx"

      session monitor-enabled

      state up

    }

    printserver2_10.x.x.B:microsoft-ds {

      address 10.x.x.B

      description "xxxxx"

      session monitor-enabled

      state up

    }

  }

  monitor tcp

}

Yes, configure a virtual server listening on port 0 ( all ports ), or use a port list. You may have to consider persistence ie add a persistence profile with Match Across Services