Topic: SME 5.1.2 and Printing

[Fred Knight]

Any help with the following would be appreciated.
12 clients all WinXP connected to SME 5.1.2 server and all functions working OK except printing.
There are 2 printers connected to the server, a HP 820CXi to the parallel port and a Epson C20 to USB1.
If I log onto a client PC as admin I can print through both printers from any application with out any problems.
If I log onto a client PC as a user I can print through the HP 820CXi from any application without any problems, but trying to print through the Epson C20 fails on all applications with the error message  “Could not start Print Job”  except for MS Word which prints out fine.  
Strange.
Fred Knight

[Amir]

I've had LOTS of problems printing with 5.12 i installed 5.0 and all is well.  with 5.12 jobs would go but nothing the printer registered no activity.

migh be worth a go.

[Charlie Brady]

Amir wrote:

> I've had LOTS of problems printing with 5.12 i installed 5.0
> and all is well.  with 5.12 jobs would go but nothing the
> printer registered no activity.

Have you reported your problems with printing in 5.1.2 to bugs@e-smith.com?

Charlie

[Amir]

Nope  I did'nt because I downloaded 5.12 and did'nt pay for it. I guessed that meant I would not qualify for reporting bugs/support ?

Amir

[Robert Field]

Same here but with Win2K.  problems with printers attached directly to the server.  

It's not just SME5.1.2 it's also happening on SME5.0 and E-smith 4 after I had upgraded SAMBA, so guess its really a SAMBA issue.  Win98 clients not effected

Have solved it by reinstalling Win2k and adding the machine to the domain.  Not a good solutuion but it is a least working.

Have not tried just adding to domain without install, but I guess it will work.

Hope this helps.

Rob

[Fred Knight]

Further only to admin being able to print through the USB on the server
I have just found that if I add users to Printer Admin in smb.conf through a custom template as

Printer admin = admin user1 user2

then these users can print through the server using both the parallel port and USB on the server. All other users can only print throught the parallel port.
Anybody have any ideas on what is hapening ? where to go next !
 Fred

[Steve]

I have similar problems, and have even tried upgrading Samba to 2.2.3a with no effect.

Seems to be a XP - Samba Issue. My 98 machines have no problem. XP commonly reports "Unable to Connect - Access Denied".

I have tried Guest OK = yes in the Printers config... figuring this should bypass and authentication issues... it does not fix it.

I have tried adding explicit names to the printer admin, sometimes this works, but mostly not.

Seems the only thing that will have any effect is to restart Samba. This sometimes lets me print for a bit.

I have this same issue with 2 SME boxes.. on 2 sites. Both may sadly end up in the bin if I can fix this soon.

I have no Win2k machines, so do not know if problem effects them, but from the many reports I have seen, it would seem it does.

[brian read]

Did anyone get a solution to this?

I am now having similar problems, with a network printer, and a local printer, giving me "access denied, unable to connect" on the Workstation.

Is their somewhere I can look on the SMEserver to see what is happening?

Using XP Pro.

After a re-boot, here are some relevent(?) entries from the log:

Aug  9 10:33:26 SMEServer papd[1556]: Authentication disabled: Ron's bubble jet
Aug  9 10:33:26 SMEServer papd[1556]: register Ron's bubble jet:LaserWriter@*
Aug  9 10:33:26 SMEServer afpd[1561]: SMEServer:AFPServer@* started on 65280.146:252 (1.5pre7)
Aug  9 10:33:26 SMEServer afpd[1561]: ASIP started on 192.168.3.4:548(2) (1.5pre7)
Aug  9 10:33:26 SMEServer afpd[1561]: uam : Loading (/etc/atalk/uams/uams_clrtxt.so)
Aug  9 10:33:26 SMEServer afpd[1561]: uam: uams_clrtxt.so loaded
Aug  9 10:33:26 SMEServer afpd[1561]: uam : Loading (/etc/atalk/uams/uams_dhx.so)
Aug  9 10:33:26 SMEServer afpd[1561]: uam: uams_dhx.so loaded
Aug  9 10:33:26 SMEServer afpd[1561]: uam : Loading (/etc/atalk/uams/uams_pgp.so)
Aug  9 10:33:26 SMEServer afpd[1561]: uam: uams_pgp.so loaded
Aug  9 10:33:26 SMEServer afpd[1561]: uam: "PGPuam 1.0" available
Aug  9 10:33:26 SMEServer afpd[1561]: uam: "DHCAST128" available
Aug  9 10:33:26 SMEServer afpd[1561]: uam: "Cleartxt Passwrd" available
Aug  9 10:33:32 SMEServer papd[1556]: Authentication disabled: officejet on sheila
Aug  9 10:33:32 SMEServer papd[1556]: register officejet on sheila:LaserWriter@*

Any ideas?

Cheers

Brian

[JB]

I was getting the same thing with network printers on a win2k sp3 pc connecting to a 5.5 update 2 server.  

Here is what I did to fix things for me:

I created another network printer with the same IP address as the one that wasn't working.  This printer worked.  I still could not connect to my original printer.  So, I created another network printer with the same IP address as well.  This printer also worked.  Then my original printer connection came back as well.  So now I have 3 network printers defined with the same IP address.  I deleted the 1st one, my original connection still worked, I deleted the 2nd one, and my orginal connection still worked.  I went ahead and deleted my original one and re-created it with the same name, settings, etc. and it still works.  I rebooted the server, and the printer still works.

I am not quite sure what the real issue is, but the above did fix it for me.

YMMV,

JB