[Samba] Problem printing from Linux to WinXP printer: "getpeername failed"
iancshay at comcast.net
Tue Nov 10 08:46:54 MST 2009
A little more information that might help. I should have
mentioned that the printer works fine when printing from
another WinXP system. Also, it appears that the "getpeername
failed" errors are not necessarily directly related. I was
able to get rid of them with "smb ports = 139" in smb.conf.
Now the only error I get in the log file is
"Nov 10 10:44:22 Officejet: prnt/hpijs/hpcups.cpp 681:
hpcups: returning status 0 from main"
Still, the only time I get the "getpeername failed" errors
is when I try to print to this printer.
iancshay at comcast.net wrote:
> I am unable to print from my Linix (Fedora 11) system, running Samba 3.4.2 , via cups 1.4.1.
> What is confusing is that from the same cups/samba installation I have no trouble at all printing to
> other WinXP printers on the network. All XP systems are running home edition. The system hosting the troubled
> printer is a laptop, this seems to be the only difference. I have ruled out network problems, because
> there is no trouble accessing files between Samba and the WinXP in question, in either direction.
> I get the following error messages in the log:
> Nov 10 00:17:28 Officejet: prnt/hpijs/hpcups.cpp 681: hpcups: returning status 0 from main
> Nov 10 00:18:37 smbd: [2009/11/10 00:18:37, 0] lib/util_sock.c:738(write_data)
> Nov 10 00:18:38 smbd: [2009/11/10 00:18:38, 0] lib/util_sock.c:1491(get_peer_addr_internal)
> Nov 10 00:18:38 smbd: getpeername failed. Error was Transport endpoint is not connected
> Nov 10 00:18:38 smbd: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
> Nov 10 00:18:38 smbd: [2009/11/10 00:18:38, 0] smbd/process.c:62(srv_send_smb)
> Nov 10 00:18:38 smbd: Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
> Also, I know that Samba is able to communicate with the XP system, because during the printer installation, using
> system-install-printer, it finds the print share with no trouble and verifies access to it.
> Any suggestions for what to try next?
More information about the samba