Samba error Address Family not supported by protocol
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba error Address Family not supported by protocol
Can you please help with the following.
I have managed to setup my cups HP Officejet printer on a Fedora core 6 print server. I can print successfully locally and on my other linux boxes - the story of connecting with my windows boxes is less favorable.
I have a "successful" connection from printserver (fedora 6) using samba to windowsbox1. my samba server is visible and i can log on with my samba user account and see my printer. I have previously install the cups windows drivers and it appears when I connect to printer on windows the drivers gets installed. However on printing test pages nothing happens. on checking both the smbd.log and windowsbox1.log there are entries regarding "address family not supported by protocol".
Below is an extract from windowsbox1.log
Quote:
2007/04/19 20:09:30, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.1.111. Error Connection reset by peer
[2007/04/19 20:09:30, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/04/19 20:41:34, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/04/19 20:41:34, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/04/19 21:01:33, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 192.168.1.111. Error = Connection reset by peer
[2007/04/19 21:01:39, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.1.111. Error Connection reset by peer
[2007/04/19 21:01:39, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/04/19 21:02:24, 1] smbd/service.c:make_connection_snum(950)
winmj (192.168.1.111) connect to service root initially as user root (uid=0, gid=0) (pid 7163)
[2007/04/19 21:02:35, 1] smbd/service.c:close_cnum(1150)
winmj (192.168.1.111) closed connection to service root
[2007/04/19 21:02:45, 0] printing/print_cups.c:cups_job_submit(571)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:15:14, 0] printing/print_cups.c:cups_cache_reload(85)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:15:14, 0] printing/print_cups.c:cups_cache_reload(85)
Unable to connect to CUPS server localhost - Address family not supported by protocol
Also smbd.log:
Quote:
[2007/04/19 20:58:04, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:01:32, 0] printing/print_cups.c:cups_cache_reload(85)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:01:32, 0] printing/print_cups.c:cups_cache_reload(85)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:02:06, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:02:36, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:04:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:05:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:06:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:07:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:08:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:09:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
[2007/04/19 21:10:29, 0] printing/print_cups.c:cups_queue_get(737)
Unable to connect to CUPS server localhost - Address family not supported by protocol
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.