On Sun, 2006-02-12 at 23:33 +1030, Tim wrote: > > One gotcha to look out for is making sure that the users that you want > to be able to print have to be entered into Samba as users with > passwords. Is that users from the Windows side or from the Linux side? I added a Samba user (identical to my Linux user), but I can't seem to log in, by typing the address directly in the add Printer dialog. Clearly something is amiss, especially since the browsing part doesn't seem to be working. I even tried a samba login to my Linux machine from my Linux machine and that failed with: session setup failed: NT_STATUS_LOGON_FAILURE I've turned off SELinux and my firewall, so that's not it. I'm still getting weird messages when trying to access the printer from my Windows machine: Feb 12 20:32:30 friday smbd[27966]: getpeername failed. Error was Transport endpoint is not connected Feb 12 20:32:30 friday smbd[27966]: [2006/02/12 20:32:30, 0] lib/util_sock.c:write_socket_data(430) Feb 12 20:32:30 friday smbd[27966]: write_socket_data: write failure. Error = Connection reset by peer Feb 12 20:32:30 friday smbd[27966]: [2006/02/12 20:32:30, 0] lib/util_sock.c:write_socket(455) Feb 12 20:32:30 friday smbd[27966]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Feb 12 20:32:30 friday smbd[27966]: [2006/02/12 20:32:30, 0] lib/util_sock.c:send_smb(647) Feb 12 20:32:30 friday smbd[27966]: Error writing 4 bytes to client. -1. (Connection reset by peer) -- Oliver Sampson Support Indie Music! olsam@xxxxxxxxxxxxxx http://cdbaby.com/group/MrSampson http://www.oliversampson.com
