Bug 1794 - Print problem with Windows XP and samba
Print problem with Windows XP and samba
Status: RESOLVED INVALID
Product: Samba 3.0
Classification: Unclassified
Component: Printing
3.0.0
x86 Windows XP
: P3 normal
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-18 21:39 UTC by Jason Chan
Modified: 2004-09-20 04:18 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Chan 2004-09-18 21:39:11 UTC
Dear all,
sorry for my poor english.

Here is my problem
I have a Fedora Core 1 Box, and Samba Server and Client 3.0.0-15 installed. 
Actually this Linux-Windows configuration is used among several sites, and 
they do not this problem, i don't know why.

What the actual problem is, when I add printer in Windows box, the connection 
seems very very slow, and i wait until it finishes. Then when I double click 
and want to see the print queue, it shows: "Opening" printer or some 
how "initializing" forever. I can print (only occasionally), but most likely 
it will hang my printing application. 

Here is my log (/var/log/samba/xxx.log)
[2004/09/18 20:07:13, 1] libsmb/cliconnect.c:cli_connect(1214)
  Error connecting to 192.168.0.199 (Connection time out)
[2004/09/18 20:07:13, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client
(2588)
  spoolss_connect_to_client: unable to connect to SMB server on machine FRED. 
Error was : SUCCESS - 0.
[2004/09/18 20:07:13, 0] lib/util_sock.c:read_socket_data(342)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/09/18 20:11:05, 1] smbd/service.c:make_connection_snum(698)
  fred (192.168.0.199) connect to service jason initially as user jason 
(uid=553, gid=554) (pid 6387)
[2004/09/18 20:12:36, 1] smbd/service.c:make_connection_snum(698)
  fred (192.168.0.199) connect to service jason initially as user jason 
(uid=553, gid=554) (pid 6393)
[2004/09/18 20:15:42, 1] libsmb/cliconnect.c:cli_connect(1214)
  Error connecting to 192.168.0.199 (Connection Time Out)
[2004/09/18 20:15:42, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client
(2588)
  spoolss_connect_to_client: unable to connect to SMB server on machine FRED. 
Error was : SUCCESS - 0.
[2004/09/18 20:16:27, 1] libsmb/cliconnect.c:cli_connect(1214)
  Error connecting to 192.168.0.199 (....)
[2004/09/18 20:16:27, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client
(2588)
  spoolss_connect_to_client: unable to connect to SMB server on machine FRED. 
Error was : SUCCESS - 0.
[2004/09/18 20:16:27, 1] smbd/service.c:close_cnum(880)
  fred (192.168.0.199) closed connection to service jason
[2004/09/18 20:17:34, 1] libsmb/cliconnect.c:cli_connect(1214)
  Error connecting to 192.168.0.199 (Connection time out)
[2004/09/18 20:17:34, 0] rpc_server/srv_spoolss_nt.c:spoolss_connect_to_client
(2588)
  spoolss_connect_to_client: unable to connect to SMB server on machine FRED. 
Error was : SUCCESS - 0.

------------------------
Here is my smb.conf (testparm)
# Global parameters
[global]
        dos charset = big5
        unix charset = big5
        workgroup = SHOWART
        netbios name = SERVER
        server string = Super Showart Samba Server
        interfaces = 192.168.0.0/24
        log file = /var/log/samba/%m.log
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        dns proxy = No
        hosts allow = 192.168.0., 127.

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        use client driver = Yes
        browseable = No

----------------------
I don't why this server have this problem, and should I tell u i have 
customized my kernel? I have my ataraid and pdcraid bulit-in into my kernel 
instead of making modules.

If you need more information just tell me, thx very much!
Comment 1 Jason Chan 2004-09-20 04:18:56 UTC
Sorry,
this issue was completely a "joke"

Just because of bad firewall at the client side.