The recent messages on bugs related to client/server printing seem to be related to a known bug 130472.
But FYI. I have often seen that Ethernet ports on HP jet direct printers are less tolerant of low budget ethernet hubs and ethernet switches. Lots of random problems as described on this list. To solve random print problems: plug your printer, server, client and print server into a Cisco/3com hub, switch, and many such random print problems go away. Sometimes the problems stay. But it is a good way to get some sanity. This has do do with HP building closer to the Ethernet specs and leaving less room for error. I like the way this works. Your printer can be the Canary in the mine, it warms you early before everything dies. My HP Ethernet printers helped me determine all our ATI switches had a major bug, and ATI admitted fault and paid to send me new ones ASAP. I got to keep the old ones for a long time and then send them back at my leisure. With the fixed switches installed, suddenly a lot of other random problems were solved. My best story ever. Just wanted to share. So printing problems may not be the fault of Edubuntu clients/servers. > and although this feature works for the first print job , immediately > afterwards port 9100 is no longer available. which means I have to > reboot the thin clients and then they print a page and reboot again. > This is not a solution , so I was hoping someone else may have seen the > same thing. Bug #130472, I've posted some code in there that fixes the problem. It will be included in Gutsy. Cheers, Scott -- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
