Mainframe LPR Printing

Unanswered Question
Jul 21st, 2010

The WAAS doesn't play nicely with old legacy mainframe LPR printing. I'm not mainframe guy, which is why I don't know the exact details to how the application was written. I was hoping this was resolved in 4.2.1 but we're still running into the same issue, work around is to bypass it completely. The problem is for every new print job it uses the same source port 721 or 722 and connects on port 515. You will have multiple syns that show up as either 721 or 722 continuously.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Michael Korenbaum Tue, 07/27/2010 - 05:34

This is still the correct behavior for the TFO Auto Discovery function.  If a WAE sees a SYN with a 4 tuple (src and dst ip and port) that it already has a connection for this new SYN will be dropped.


Mike Korenbaum

Cisco WAAS PDI Help Desk


This Discussion