Aaron, David, I found that the following IPTABLES rule needs to be added if you are running an IPTABLES firewall on the samba server side and a Novell Client on the Windows XP side:
# The following port needs to be open so that Microsoft XP can timeout quicker. $IPTABLES -A tcp_packets -p tcp -m tcp --dport 524 --syn -j ACCEPT Also, I found that opening TCP/UDP ports 135:139 are good. These Microsoft/Novell services are so "brain-dead" that if the firewall is blocking these ports, the client realizes a timeout of roughly 1 to 1.5 minutes before trying different services elsewhere. Opening these ports (without services running on the ports) gives the brain-dead Microsoft box an immediate "Service Not Available" error, causing it to go elsewhere quicker . . . :-) Also, have you tried disabling the firewall on the XP client side and running that SP2 modified configuration for a little while? One of the main differences with SP2 is that it's the first XP release that came with the firewall ENABLED by default (prior released came with with firewall DISABLED by default). Also, is this XP system part of a "domain" or standalone. If standalone, you should apply the XP registry hacks to stop it from trying to find it's domain server (an active directory) every 8 hours or so . . . (I forgot the URL for these . . . www.google.com). Also, are you running a WINS server anywhere in the area? Let me know what works . . . :-) Steve -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David Kaiser Sent: Wednesday, December 01, 2004 12:12 AM To: [email protected] Subject: Re: [909linux] samba, cups and windows xp sp2 problem Hi Aaron, I haven't yet seen a SP2 setup, so that firewall hasn't gotten in my way (yet!) but I was able to talk to a Samba expert about this. Here's some things to look into. - diagnose with a sniffer, as with all firewall problems. Probably XP is blocking the print notify back channel - (What is print notify back channel?) Depending on how printing is setup, for some operations the server needs to create a SMB connection to the client (tcp ports 139 and/or 445) (this is just a wild guess - really better to use a sniffer to diagnose) ... also, here is a link that seemed related... http://www.archivum.info/[email protected]/2004-11/msg00981.html Hope this helps... On 30Nov2004 09:34AM (-0800), Aaron Lopez wrote: > Hello, > I know some of us have setup linux print servers with SAMBA and CUPS, > as have I. But, I have noticed that workstations with Windows XP SP2 > perform slowly at times when copying from SAMBA or bringing up the > Properties menu on printers. Windows NT 4 and Windows 2000 do not > experience this performance issue. SAMBA's site is vague on the matter > and just mentions that some people have reported it but there's no > official explanation. Has anyone seen this problem? > > > > Aaron Lopez > PerMedics Inc. System Administrator > 909.558.8155 > [email protected] > > _______________________________________________ > 909linux mailing list > [email protected] > http://909linux.org/cgi-bin/mailman/listinfo/909linux -- /* david kaiser (NO SPAM/UCE) pubkey=1C8DCC8D begin e-mail decoder */ main() {int j=-1;char t[]="gndlvhuCfgn1frp\r";while(t[j]!='\r'){putchar(t[++j]-3);}0;} _______________________________________________ 909linux mailing list [email protected] http://909linux.org/cgi-bin/mailman/listinfo/909linux Confidentiality Note: The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.
