On Fri, 2006-02-10 at 12:44 -0600, Mikkel L. Ellertson wrote: > Oliver Sampson wrote: > > Howdy, > > I'm having trouble getting my printer to share to my other Windows > > computers on my network via Samba. The funny thing is that I had this > > set up a coupla years ago on FC2, and it was a piece of cake. Now, > > there's nothing but problems. > > > > I turned on Samba and browsing for printers in Samba. My Windows > > machines can now see my Linux machine via the Network Neighborhood, but > > not the printer. > > > > I turned on printer sharing in the system-config-printer utility, but > > that doesn't seem to make a difference. > > > > Here's the printer part of my smb.conf > > [printers] > > comment = All Printers > > path = /var/spool/samba > > browseable = yes > > # Set public = yes to allow user 'guest account' to print > > guest ok = yes > > ; writeable = no > > printable = yes > > public = yes > > > > Any tips? > > > Do you have something like this in the Global section? > > # 2. Printing Options: > # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK > # (as cups is now used in linux-mandrake 7.2 by default) > # if you want to automatically load your printer list rather > # than setting them up individually then you'll need this > printcap name = cups > load printers = yes > > # It should not be necessary to spell out the print system type unless > # yours is non-standard. Currently supported print systems include: > # bsd, sysv, plp, lprng, aix, hpux, qnx, cups > printing = cups > > Mikkel > -- > > Do not meddle in the affairs of dragons, > for thou art crunchy and taste good with Ketchup! > I forgot one thing: I did a tail on /var/log/messages and this pops out when I try to connect to my linux box: Feb 11 13:46:33 friday smbd[8673]: [2006/02/11 13:46:33, 0] lib/util_sock.c:get_peer_addr(1150) Feb 11 13:46:33 friday smbd[8673]: getpeername failed. Error was Transport endpoint is not connected Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:get_peer_addr(1150) Feb 11 13:46:34 friday smbd[8673]: getpeername failed. Error was Transport endpoint is not connected Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/access.c:check_access(328) Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:get_peer_addr(1150) Feb 11 13:46:34 friday smbd[8673]: getpeername failed. Error was Transport endpoint is not connected Feb 11 13:46:34 friday smbd[8673]: Denied connection from (0.0.0.0) Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:get_peer_addr(1150) Feb 11 13:46:34 friday smbd[8673]: getpeername failed. Error was Transport endpoint is not connected Feb 11 13:46:34 friday smbd[8673]: Connection denied from 0.0.0.0 Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:write_socket_data(430) Feb 11 13:46:34 friday smbd[8673]: write_socket_data: write failure. Error = Connection reset by peer Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:write_socket(455) Feb 11 13:46:34 friday smbd[8673]: write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by peer Feb 11 13:46:34 friday smbd[8673]: [2006/02/11 13:46:34, 0] lib/util_sock.c:send_smb(647) Feb 11 13:46:34 friday smbd[8673]: Error writing 5 bytes to client. -1. (Connection reset by peer) So, I thought there was something funny with the IP address from the Windows machine. So, I turned off the IP address checking in Samba (I had it limited to 192.168.0. and 127.) but I still can't see the printer. Why the IP address is showing up as 0.0.0.0 is a puzzle. My linux machine is also the dhcp server giving the windows machine its IP address. -- Oliver Sampson Support Indie Music! olsam@xxxxxxxxxxxxxx http://cdbaby.com/group/MrSampson http://www.oliversampson.com
