Cannont Print .pdf files across subnet

Hello

I have a network separated into 2 subnets.  I cannot print .pdf file to an Lanier LP 126cn (direct attached to network) on the different subnet.  I can print all other file types that I've tried.  I've change the driver on the printer to no avail.  The router is a sonicwall TZ 170 with the subnet attached to the optional port.

Any ideas?
LVL 3
m1crochipAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

claymanscherCommented:
More information is needed:
1) Do you see an error message, or does the print job just seem to fall into a black hole?
2) From what application are you attempting to print the PDF? Full Acrobat? Reader? What version?
3) Have you tried printing to a different printer (either locally-connected or on the local subnet) to see whether you have a generic PDF printing issue rather than a networking issue?
0
m1crochipAuthor Commented:
Sorry - yes the error is "Could not start print job"  this occurs after a very long delay in which acrobat (from which I am printing) seems hung.  Computers on the same subnet as the printer can print .pfds fine, and all other computers can print all other files except .pdf.  I am guessing that there is some kind of packet size issue or something ...
0
claymanscherCommented:
Are you using a PostScript driver or a PCL driver? Both are available from Lanier at http://www.lanier.com/page.php/downloads?agree=n%2Fa&agree=true&model=LP126cn -- whatever you're using now, try the other. If you're using PostScript, you might want to try experimenting with Adobe's PostScript printing options such as PostScript level and optimization for portability. Sometimes the older (lower) PostScript levels work more reliably than the newer (higher) ones.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

m1crochipAuthor Commented:
I've tried  both drivers (actually 3) and have played with numerous postscript settings with no effect.  Is there something unique about .pdf file packet size that would stop them at the router interface?  I can't find any relevent info on the internet.  I read something about the size of .pdf files being transmitted over the network - but the local computers print fine, so I was thinking that it is some kind of router issue ...
0
m1crochipAuthor Commented:
Two dialog boxes pop up with the errors.  One says "The document could not be printed" and the next one says "Could not start print job".  
0
claymanscherCommented:
Since Acrobat is using the same printer driver as other applications that are printing without difficulty, I wouldn't expect it to have anything to do with packet size. The network drivers should produce the same packet structure for PDFs as they do for any other document type.

Is there anything unique about the manner in which Acrobat is executed? Is it running under different user credentials, or as a system process? Is it running in a browser window rather than its native window?

You said the printer connects directly to the network, so I assume it is configured on the workstation through a TCP/IP port connection rather than a Windows share. Check the associated port configuration to see that its IP address is properly specified. Also check what protocol it is using (Raw or LPR); Raw is port-number-dependent, but LPR isn't, so if you're in Raw mode, try LPR (you'll need its queue name, which may be simply "lp"). I'd expect these things to affect other applications too, not just Acrobat, but you never know for sure until you try.
0
orlg001Commented:
Is this happening when printing directly from Acrobat reader or Acrobat reader via Internet Explorer?
0
m1crochipAuthor Commented:
When printing from both.
0
m1crochipAuthor Commented:
The problem is Acrobat.  I downloaded a different reader and printed from it with no problems.  I would still like to get this resolved since everyone has acrobat and the plugin for IE.
0
m1crochipAuthor Commented:
Forget that last comment - I just verified that the pdf does NOT print from the other pdf viewer.  The print screen from acrobat moves very slowly, but this new reader is fast and does not give any errors, but the pdf fails to print.
0
m1crochipAuthor Commented:
After checking the event log, it looks like the connection to the printer is being terminated because of too many open tcp requests.  netstat has many entries to the printer that are not established.  In apps besides pdf ones like acrobat, there is eventually one that is established.  I guess that the pdf readers are requesting more than other apps.  

Any ideas??
0
Stuart OramIT Technical Lead (Project Sites)Commented:
I'm afraid I can't help with a solution, but I have experienced the same problem, so I doubt it is something specific to your machine or network, the problem must lie elsewhere.
0
claymanscherCommented:
Have you tried different versions of Acrobat? Did the problem arise after upgrading?
0
Stuart OramIT Technical Lead (Project Sites)Commented:
Certainly I've used the latest version of Acrobat with no joy - had to print to MS Document Image Writer and then print from there to network printer.
0
claymanscherCommented:
I was the first one to jump onto this question, so I'll add my final comments at this time.

I've dealt with many PDF printing issues, but I've never seen a print job overload a TCP stack, which m1crochip's responses suggest is happening in this case. However, I've experienced dropped connection problems that randomly affected all kinds of network traffic, not just print jobs from a particular type of document. Dropped TCP connections can result from network switches having too little store-and-forward capacity to handle peak traffic levels on a heavily loaded network backbone. Such problems typically occur sporadically and wouldn't produce the consistent failures that m1crochip claims to be experiencing, unless other traffic on the backbone is consistently high enough to maintain a backlog of packets in the switches. I'd expect that to affect many other things, not just PDF printing.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.