Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Printing over IPSec VPN

Avatar of Defianse
DefianseFlag for Canada asked on
Hardware FirewallsNetwork Management
5 Comments1 Solution2038 ViewsLast Modified:
I just implemented a Firebox X Core 550e which replaced a SnapGear SG560.  The new appliance implementation went up without a hitch and all Branch VPN's also came up without any hitches either, with one very confusing exception...

My Xerox Multifunction printers residing at the branch office won't print or, a small print job (tiny test page) can take upto 2 minutes to deliver over the vpn usually with a 'failed' message first.  When you view the job in the printer queue, the byte count is extremely slow to process.  So the larger jobs, it seems, timeout.  This odd issue exists only with the Xerox's.  My Ricoh's, Samsung's,  and Dell's (mixed Plain & Multifunction) all work fine and blazing fast but the Xerox's, all of them WorkCentre's, not so much.

Those printers work fine on their respective local networks.  It's only print jobs sent over the VPN.  It's obvious communication is the related problem because attempts (over the vpn) to bring up the Printer Properties page takes unusually long 10secs+ but it does eventually come up.  Again, only on the Xerox's.

These are regular IPSec tunnels and the issue did not exist before the new Firewall was put in.  The only difference in the tunnel config is that I am now using 3DES/SHA1 and AES256/SHA1 & DH2 where I was using 3DES/MD5 DH1 and 3DES/SHA1 DH1 before.

Idea's anyone?
Avatar of Defianse
DefianseFlag of Canada image

Our community of experts have been thoroughly vetted for their expertise and industry experience.

This problem has been solved!
Unlock 1 Answer and 5 Comments.
See Answers