Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Robert Field on February 03, 2002, 11:38:28 PM

Title: Can not print using Win2K and SME5.12
Post by: Robert Field on February 03, 2002, 11:38:28 PM

Have updated to SME5.1.2 and I can now not print from any Win2K clients.

Printers hanging off the Server no longer work. error is access denied.

If I log on using Administrator to a Win2K client it works, but using any other name fails even if I apply admin privilages to the user.

I'm assuming its a Samba issue.

Any ideas?


Rob

Title: Re: Can not print using Win2K and SME5.12
Post by: Alexander Ziemann on February 04, 2002, 03:16:57 AM

It is a samba issue. Something went wrong during printer installation.

Delete the printer, reboot and install again. Make shure you are logged in as root/admin all the time during printer and printer-driver installation.

Be sure you upgrade to version 5.1.2 first. It has most average samba support. Even my ugly access-apps work on e-smith now.

hth
alex

Title: Re: Can not print using Win2K and SME5.12
Post by: Robert Field on February 04, 2002, 12:15:24 PM

Thanks for you thoughts Alex.

I've reinstalled the printers at the Win2K end As Administrator and SME5.1.2 as Admin, but I still get the same problem.

I have now tried it on three different systems two running SME5.1.2 and one running SME5 with the SAMBA upgrade.  I get the same result.

Any printer hanging of the server (Access denied, unable to connect).

One of the SME5.1.2 was an upgrade from SME5 and the printer work before upgrade.

Full network printers are OK its only those hanging off the servers.


Rob

Title: Re: Can not print using Win2K and SME5.12
Post by: Alexander Ziemann on February 04, 2002, 01:06:54 PM

Hi, reinstall is not enough. You have to delete the existing printer via admin-panel at least. Sometimes we have to switch off/on the Network Printer, to restart the printqueue. This seems to happen, when printjobs arrive at night with printer off-line.

What do the logs say?

We are heavily printing here in exactly your configuration. So it should be no problem.

alex

Title: Re: Can not print using Win2K and SME5.12
Post by: Robert Field on February 04, 2002, 01:50:31 PM

Alex, thanks for your input.


Have tried the following on two servers.

Delete printer via SME admin-panel

Delete printer via Win2K

Power off/on printer

Restart Win2K machine

Add printer via SME admin-panel

Add printer via Win2K

Same Error  on both servers

Log file below

Feb  4 10:47:08 server1 papd[19593]: Authentication disabled: epson
Feb  4 10:47:08 server1 papd[19593]: register epson:LaserWriter@*

Rob

Title: Re: Can not print using Win2K and SME5.12
Post by: Filippo Carletti on February 04, 2002, 01:57:15 PM

Robert Field wrote:
> Delete printer via Win2K
> Feb  4 10:47:08 server1 papd[19593]: Authentication disabled:
> epson
> Feb  4 10:47:08 server1 papd[19593]: register
> epson:LaserWriter@*

papd is an Appletalk daemon, used by macintosh.
I assume you're printing through smb with win2k.

Title: Re: Can not print using Win2K and SME5.12
Post by: Robert Field on February 04, 2002, 02:45:59 PM

Filippo

I'm printing through both Apple and Win2K, but its the Win2k that is the problem.

I was not sure what part of the log to include and just grabbed the latest section assuming it would relate to what I hade just done. My mistake.


Rob

Title: Re: Can not print using Win2K and SME5.12
Post by: Filippo Carletti on February 04, 2002, 02:53:11 PM

Look at samba logs (/var/log/samba/log.your-windows-pc-name)
Output of "lpc status all"

Title: Re: Can not print using Win2K and SME5.12
Post by: Ian Lowe on February 05, 2002, 08:49:17 PM

Getting same issue, SME 5.1.2, Windows 2K (also XP)

[2002/02/05 12:24:36, 0] lib/util_sock.c:matchname(955)
  host name/name mismatch: pc-00129 != pc-00129.homeoffice.wintermute-ltd.com
[2002/02/05 12:24:36, 0] lib/util_sock.c:get_socket_name(1008)
  Matchname failed on pc-00129 192.168.1.129
[2002/02/05 12:26:27, 0] smbd/service.c:make_connection(238)
  babbage (192.168.1.129) couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d}
[2002/02/05 12:28:52, 0] smbd/server.c:sig_hup(384)
  Got SIGHUP

We are evaluating SME as an W2K replacement, so elements of both environments exist. the machine in question is called "babbage", however, we have now disabled the W2K DHCP Server and are using SME5 instead.

Thing is, the user at this workstation can happily use i-bays.

Title: Re: Can not print using Win2K and SME5.12
Post by: Tom Veitch on February 05, 2002, 10:15:34 PM

Out of the Box Installation i have been able to print with SME 5.1.2 from a Win2000 workstation.

Have you joined the Domain with your workstation. ?

Is the Printer a Network Printer or direct off the Server. ?

If you are useing a print server what type ?

Let us Know

Title: Re: Can not print using Win2K and SME5.12
Post by: Robert Field on February 06, 2002, 03:30:06 PM

Same problem if I have joined a Domain or not, have tried both.




Directly off the server,  Have tried three different printers.




No printer server being used.


Will post log files later if I get a spare moment.

thanks for your input


Rob

Title: Re: Can not print using Win2K and SME5.12
Post by: Andrew Hunt on February 26, 2002, 05:07:32 PM

Hello,

I am having a similar problem. Here's my case:

- everything working on SME 5.0
- desktop Win XP printing fine on printer attached to SME
- laptop Win XP printing fine on printer attached to SME
- upgraded to SME 5.1.2
- desktop Win XP printing fine on printer attached to SME
- laptop Win XP gives access denied error

Any ideas?

...Andrew