Hi All-

Having some odd difficulties with samba and Windows XP SP2 clients. File
share browsing works just fine, but printing is taking forever. It takes
several seconds to get a print dialog on a WinXP box, then several seconds
more if you want to change printers, then several seconds more to actually
print the job after hitting the "Print" button. Not experiencing any of
this when printing to printers shared from non-Samba boxes.

I did some poking around in the logs first. I see the following
interesting things:

In /var/log/messages:
> getpeername failed. Error was Transport endpoint is not connected
This only occurs periodically, not every time a print attempt is made=

In /var/log/samba:
There are four log files made each time an XP machine connects:
log.0.0.0.0
log.[the-xp-machine's-ip]
log.[the-xp-machine's-netbios-name]
log.[the-xp-machine's-netbios-name].old

In /var/log/samba/log.0.0.0.0:
smbd/connection.c:yield_connection(76)
  yield_connection: tdb_delete for name  failed with error Record does not
exist.

/var/log/samba/[the-xp-machine's-netbios-name] is HUGE... Looks almost
like every packet is getting logged here. My debuglevel in
/etc/samba/smb.conf is set to 3.

After poking around on google, I'm thinking it might be a reverse DNS
issue. Some prior posts on this list pseudo-confirmed that, but I'm still
not sure what I need to do to resolve it. If I try to ping one of the
windows boxes by its netbios name, I get a host not found, as I would
expect. But I've so far been unsuccessful in getting netbios name lookups
working.

I've tried adding a "wins server = [ip-address-of-wins-server]" in the
/etc/samba/smb.conf file - no help. I've tried adding "wins" to the
"hosts:" line of /etc/nsswitch.conf - no help. Meanwhile, I can type "ping
[somemachine]" in a command window on my XP box, and it happily finds the
other box.

Anyone have any suggestions? I need to get this printing slowness problem
resolved.

Thanks,
Dave

--
[email protected] mailing list

Reply via email to