F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

vrivoire_97090's avatar
vrivoire_97090
Icon for Nimbostratus rankNimbostratus
Oct 29, 2008
Solved

MS Print servers

Hi all,     I am planning to use my new F5 LTM to load balance Windows Server 2003 print servers. For the moment, it doesn't work for me: I can see the shared printer but I can't map it. ...
microsoft
partner
  • Christopher_Boo's avatar
    Christopher_Boo
    Feb 05, 2014

    Here's the new link to the guide for creating the WMI monitor. As I recall it was pretty straightforward. I'm even using the same interval and timeout. Looking at my monitor properties, the only thing I see that is different is my alias service port is 3389 and the external program path is /usr/bin/monitors. Also, you'll need to enable remote WMI requests on the win2k8 boxes if not already enabled.

     

    Monitoring WMI Services from Big-IP

     

Anonymous25's avatar
Anonymous25
Icon for Nimbostratus rankNimbostratus
Jun 28, 2019

As an additional update, it does not matter if I use the NPath iApp or build a virtual server. If I map to the printer directly through the print server, I have no issues, when trying to map through the F5, either via NPath or virtual server, I get an error on the Print Server using Wireshark stating, OpenprinterEx reponse, invalid printer name. it doesn't matter if I add it through the VIP or DNS name, I always get this issue.

 

Thanks.

Anonymous25's avatar
Anonymous25
Icon for Nimbostratus rankNimbostratus
Jul 02, 2019

Sure!

Version:

BIG-IP 13.1.0.1 Build 0.0.8 Point Release 1

 

ltm virtual VS_MSPrint {

  destination 10.41.18.252:any

  ip-protocol tcp

  mask 255.255.255.255

  pool Pool_MSPrint

  profiles {

    tcp { }

  }

  source 0.0.0.0/0

  source-address-translation {

    type automap

  }

  translate-address enabled

  translate-port disabled

  vs-index 24

 

 

ltm pool Pool_MSPrint {

  members {

    10.41.18.236:any {

      address 10.41.18.236

    }

 

I know I don't have any monitors setup right now as this is just a proof of concept function with a test server.

 

 

 

As far as registry/server changes, I have tried pretty much all of them in a variety of combinations

*Created Loopback adapter with same IP address as the F5 VIP

*Set the WeakHost settings for Net and Loopback adapters

*Set the Loopback Metric to 254

*Disabled Loopback check

*Disable Strict Name Chacking

*Optional Names

*DnsOnWire

*Disabled NetBios (with DNS entry on VIP)

*Modified the Hosts File with DNS names

 

Happy to make any changes or test things to see if we can get this working.

 

Thanks.