Epson 3800, OS X 10.5 via network slow

[Wayne Fox]

I have my 3800 and my 11880 both connected via ethernet.  Recently, the 3800 has slowed to a crawl, even with no network activity or extra computer activity when printing.  Basically the head moves across and back, then pauses ... does that for about 3/4 of the print, then finishes as normal.

I have tried uninstalling/reinstalling drivers, various things with the network (computer and printer both plugged into  Time Capsule as the hub), without success.  I finally moved the printer so I could use USB ... works fine.  The 11880 works fine as well, no speed problems even with the very large files I'm sending to it.

Any thoughts?

running MacPro 8-core with 16gigs ram, 2TB and 1 TB raid, OS X 10.54

[madmanchan]

Which version of 10.5? I saw another thread about this issue somewhere, and I think the user had just upgraded to 10.5.5.

[Wayne Fox]

Which version of 10.5? I saw another thread about this issue somewhere, and I think the user had just upgraded to 10.5.5.
[a href=\"index.php?act=findpost&pid=223019\"][{POST_SNAPBACK}][/a]

Still using 10.5.4.

[francois]

Still using 10.5.4.
[a href=\"index.php?act=findpost&pid=223082\"][{POST_SNAPBACK}][/a]

Mine has been running fine (10.5.4) but it always takes 10-90 seconds before the printing actually starts. During that delay, my Mac is looking for the printer.

[madmanchan]

Wayne, which app(s) are you printing from?

[Wayne Fox]

Wayne, which app(s) are you printing from?
[a href=\"index.php?act=findpost&pid=223130\"][{POST_SNAPBACK}][/a]

CS3 and Lightroom 2.1

[madmanchan]

That is quite strange. I am printing from the same apps, same versions, to my 3800 without the funky pauses. I'm guessing you're using the latest Epson Leopard beta driver?

[francois]

Mine has been running fine (10.5.4) but it always takes 10-90 seconds before the printing actually starts. During that delay, my Mac is looking for the printer.
[a href=\"index.php?act=findpost&pid=223104\"][{POST_SNAPBACK}][/a]

I would add that once printing has started, thre's no pause. I'm using the Leopard Beta drivers.

[Doombrain]

could be packet loss, check the cable. i'd swap it for the 11880 cable.

[Wayne Fox]

could be packet loss, check the cable. i'd swap it for the 11880 cable.
[a href=\"index.php?act=findpost&pid=223359\"][{POST_SNAPBACK}][/a]

I have tried multiple cables, but after reading your suggestion decided to try experimenting with cables a little more.

It seems that the cable is not seating fully into the printer ... seems like the slightest strain on the cable causes problems.  The printer works fine if I pull it away from the wall so the cable has no strain from bending. I think the printer's connector has some issues, hopefully something I can work around.  

Thanks to all those with suggestions.

[Doombrain]

glad you got it sorted.

[JonasYip]

I came across this thread while I was experiencing the same problem: networked 3800, 10.5.5, excruciatingly slow printing where it pauses after every head pass. Although this thread was resolved, I thought I'd add to the thread since my solution turned out to be different. Perhaps it might help the next person who has a similar problem...

Anyway, I was having general networking problems, probably due to a recent logic board replacement, and had lost all communication with the 3800. I did a bunch of driver install/updates, printer add/delete, etc and finally got it working... except for the slow printing problem. I finally discovered that if I connected via Appletalk, I got the slow printing, but then if I added a new printer with the "Epson TCP/IP" version it printed fine. I had added the Appletalk version because the TCP/IP version wasn't showing up, and then did later for some reason. Anyway, something to check for...

j

[GamutGirl]

****UPDATE****
After messing around with the drivers, we found that installing the 3800s using the Line Printer Daemon Protocol under IP restored the faster printing speed. We initially had installed the driver under Internet Printing Protocol - IPP, which slowed it down considerably.


Our lab recently updated to OSX 10.5.6 and updated the 3800 drivers. First off, our 3800s can not be found using the Epson TCP/IP browser under the printer installation window. Second, the 3800 connected using the newest drivers is slow as dirt. The computers with 10.5.4 running the older drivers are fine. Besides reverting back to an older version, are there any other solutions?

I came across this thread while I was experiencing the same problem: networked 3800, 10.5.5, excruciatingly slow printing where it pauses after every head pass. Although this thread was resolved, I thought I'd add to the thread since my solution turned out to be different. Perhaps it might help the next person who has a similar problem...

Anyway, I was having general networking problems, probably due to a recent logic board replacement, and had lost all communication with the 3800. I did a bunch of driver install/updates, printer add/delete, etc and finally got it working... except for the slow printing problem. I finally discovered that if I connected via Appletalk, I got the slow printing, but then if I added a new printer with the "Epson TCP/IP" version it printed fine. I had added the Appletalk version because the TCP/IP version wasn't showing up, and then did later for some reason. Anyway, something to check for...

j

[Justan]

It appears you’ve found a solution to the problem. For future reference here’s a simple test and a not so simple test to see if the printer is having problems due to a cable or interface.

Simple test: use a tool called “ping” to test for response time and potential packet loss. First I opened a command window typed the word “ping” followed by a space, and then the ip address of the printer, then I hit the Enter key. Here’s the results:

C:\Documents and Settings\Justan>ping 10.0.0.9

Pinging 10.0.0.9 with 32 bytes of data:

Reply from 10.0.0.9: bytes=32 time<1ms TTL=64
Reply from 10.0.0.9: bytes=32 time<1ms TTL=64
Reply from 10.0.0.9: bytes=32 time<1ms TTL=64
Reply from 10.0.0.9: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

The key details here are 1) the response time which was “<1ms”  2) the data loss, which was 0 or none.  “Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)”

This is enough information to tell you if the device is responding and also if there is any data loss. With the connector faulting, you’d have likely seen slower response time and at least some data loss.

If you want to do a detailed study there is a really good protocol analyzer or “packet sniffer” that used to be called Ethereal but which has been renamed to Wireshark. Protocol analyzers provide very highly detailed information that can help you pin down exactly what is going wrong.

The documents that come with the software are pretty good, but I recommend a book called “Network Monitoring and Analysis A protocol Approach to Troubleshooting” by Ed Wilson.