Sorry if this has been covered before. I setup a new Samba server using RedHat EL 3, and samba 3.0.2-6.3E (the version that comes with Redhat). We were seeing an intermittant 20 seconcd delay when grabbing a directory listing, but only from XP, win 2k was fine. I couldn't completely nail down when the delay occured but it seemed to be when the directory or share hadn't been accessed in a while, ~15mins ??. There was never a problem or delay seeing the samba server on the browse list. I turned off iptables and the delay has been drastically reduced, now down to 2 secs, which is acceptable. Obviously I'd like to turn iptables back on. I'm wondering if there are any special port openings or other iptables settings that need adjustments with XP; or if there are adjustments I need to make to the XP clients. I've already tried the RemoteComputer\NameSpace\ regkey fix to no avail. It's a very basic iptables setup. I opened up the standard samba ports. I've listed the output of 'iptables --list' below. Any ideas? TTIA /randoms/ 'iptables --list' output : Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:netbios-ns ACCEPT udp -- anywhere anywhere state NEW udp dpt:netbios-ns ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:netbios-dgm ACCEPT udp -- anywhere anywhere state NEW udp dpt:netbios-dgm ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:netbios-ssn ACCEPT udp -- anywhere anywhere state NEW udp dpt:netbios-ssn ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:microsoft-ds ACCEPT udp -- anywhere anywhere state NEW udp dpt:microsoft-ds ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:497 ACCEPT udp -- anywhere anywhere state NEW udp dpt:497 ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
hi friend. that is what i m wondering about for a while. and listen i got another problem that if i redirect port 80 (http) to transparent proxy in PREROUTING then this delay approaches to a delay of 4 minutes. but if there is no rule for transparent redirection then it takes a delay as u specified. please let me know if u find the solution and i will aslo let u know if i find any problem Regards Azeem>From: Randy S <randoms@yahoo.com> >To: samba@lists.samba.org >Subject: [Samba] Directory listing delay with WinXP and IPtables >Date: Mon, 31 May 2004 15:50:47 -0700 > >Sorry if this has been covered before. > >I setup a new Samba server using RedHat EL 3, and samba 3.0.2-6.3E (the >version that comes with Redhat). > >We were seeing an intermittant 20 seconcd delay when grabbing a directory >listing, but only from XP, win 2k was fine. > >I couldn't completely nail down when the delay occured but it seemed to be >when the directory or share hadn't been accessed in a while, ~15mins ??. >There was never a problem or delay seeing the samba server on the browse >list. > >I turned off iptables and the delay has been drastically reduced, now down >to 2 secs, which is acceptable. > >Obviously I'd like to turn iptables back on. > >I'm wondering if there are any special port openings or other iptables >settings that need adjustments with XP; or if there are adjustments I need >to make to the XP clients. I've already tried the RemoteComputer\NameSpace\ >regkey fix to no avail. > >It's a very basic iptables setup. I opened up the standard samba ports. >I've listed the output of 'iptables --list' below. > >Any ideas? > >TTIA > >/randoms/ > >'iptables --list' output : > >Chain INPUT (policy ACCEPT) >target prot opt source destination >RH-Firewall-1-INPUT all -- anywhere anywhere > >Chain FORWARD (policy ACCEPT) >target prot opt source destination >RH-Firewall-1-INPUT all -- anywhere anywhere > >Chain OUTPUT (policy ACCEPT) >target prot opt source destination > >Chain RH-Firewall-1-INPUT (2 references) >target prot opt source destination >ACCEPT all -- anywhere anywhere >ACCEPT icmp -- anywhere anywhere icmp any >ACCEPT ipv6-crypt-- anywhere anywhere >ACCEPT ipv6-auth-- anywhere anywhere >ACCEPT all -- anywhere anywhere state >RELATED,ESTABLISHED >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:netbios-ns >ACCEPT udp -- anywhere anywhere state NEW udp >dpt:netbios-ns >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:netbios-dgm >ACCEPT udp -- anywhere anywhere state NEW udp >dpt:netbios-dgm >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:netbios-ssn >ACCEPT udp -- anywhere anywhere state NEW udp >dpt:netbios-ssn >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:microsoft-ds >ACCEPT udp -- anywhere anywhere state NEW udp >dpt:microsoft-ds >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:497 >ACCEPT udp -- anywhere anywhere state NEW udp >dpt:497 >ACCEPT tcp -- anywhere anywhere state NEW tcp >dpt:ssh >REJECT all -- anywhere anywhere reject-with >icmp-host-prohibited > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba_________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
mrojava4@eastgranby.k12.ct.us
2004-Jun-01 02:17 UTC
[Samba] Directory listing delay with WinXP and IPtables
I'd be curious to know whether the behaviour for XP Pro changes if you put the following parameter into smb.conf smb ports = 139 This tells samba not to respond to port 445 traffic. I'm assumming that samba is not participating in an active directory. Mark> Sorry if this has been covered before. > > I setup a new Samba server using RedHat EL 3, and samba 3.0.2-6.3E (the > version that comes with Redhat). > > We were seeing an intermittant 20 seconcd delay when grabbing a > directory listing, but only from XP, win 2k was fine. > > I couldn't completely nail down when the delay occured but it seemed to > be when the directory or share hadn't been accessed in a while, ~15mins > ??. There was never a problem or delay seeing the samba server on the > browse list. > > I turned off iptables and the delay has been drastically reduced, now > down to 2 secs, which is acceptable. > > Obviously I'd like to turn iptables back on. > > I'm wondering if there are any special port openings or other iptables > settings that need adjustments with XP; or if there are adjustments I > need to make to the XP clients. I've already tried the > RemoteComputer\NameSpace\ regkey fix to no avail. > > It's a very basic iptables setup. I opened up the standard samba ports. > I've listed the output of 'iptables --list' below. > > Any ideas? > > TTIA > > /randoms/ > > 'iptables --list' output : > > Chain INPUT (policy ACCEPT) > target prot opt source destination > RH-Firewall-1-INPUT all -- anywhere anywhere > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > RH-Firewall-1-INPUT all -- anywhere anywhere > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > Chain RH-Firewall-1-INPUT (2 references) > target prot opt source destination > ACCEPT all -- anywhere anywhere > ACCEPT icmp -- anywhere anywhere icmp any > ACCEPT ipv6-crypt-- anywhere anywhere > ACCEPT ipv6-auth-- anywhere anywhere > ACCEPT all -- anywhere anywhere state > RELATED,ESTABLISHED > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-ns > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-ns > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-dgm > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-dgm > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-ssn > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-ssn > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:microsoft-ds > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:microsoft-ds > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:497 > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:497 > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:ssh > REJECT all -- anywhere anywhere reject-with > icmp-host-prohibited > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
mrojava4@eastgranby.k12.ct.us
2004-Jun-01 02:18 UTC
[Samba] Directory listing delay with WinXP and IPtables
I'd be curious to know whether the behaviour for XP Pro changes if you put the following parameter into smb.conf smb ports = 139 This tells samba not to respond to port 445 traffic. I'm assumming that samba is not participating in an active directory. Mark> Sorry if this has been covered before. > > I setup a new Samba server using RedHat EL 3, and samba 3.0.2-6.3E (the > version that comes with Redhat). > > We were seeing an intermittant 20 seconcd delay when grabbing a > directory listing, but only from XP, win 2k was fine. > > I couldn't completely nail down when the delay occured but it seemed to > be when the directory or share hadn't been accessed in a while, ~15mins > ??. There was never a problem or delay seeing the samba server on the > browse list. > > I turned off iptables and the delay has been drastically reduced, now > down to 2 secs, which is acceptable. > > Obviously I'd like to turn iptables back on. > > I'm wondering if there are any special port openings or other iptables > settings that need adjustments with XP; or if there are adjustments I > need to make to the XP clients. I've already tried the > RemoteComputer\NameSpace\ regkey fix to no avail. > > It's a very basic iptables setup. I opened up the standard samba ports. > I've listed the output of 'iptables --list' below. > > Any ideas? > > TTIA > > /randoms/ > > 'iptables --list' output : > > Chain INPUT (policy ACCEPT) > target prot opt source destination > RH-Firewall-1-INPUT all -- anywhere anywhere > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > RH-Firewall-1-INPUT all -- anywhere anywhere > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > Chain RH-Firewall-1-INPUT (2 references) > target prot opt source destination > ACCEPT all -- anywhere anywhere > ACCEPT icmp -- anywhere anywhere icmp any > ACCEPT ipv6-crypt-- anywhere anywhere > ACCEPT ipv6-auth-- anywhere anywhere > ACCEPT all -- anywhere anywhere state > RELATED,ESTABLISHED > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-ns > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-ns > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-dgm > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-dgm > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:netbios-ssn > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:netbios-ssn > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:microsoft-ds > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:microsoft-ds > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:497 > ACCEPT udp -- anywhere anywhere state NEW > udp dpt:497 > ACCEPT tcp -- anywhere anywhere state NEW > tcp dpt:ssh > REJECT all -- anywhere anywhere reject-with > icmp-host-prohibited > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
hi Take a look at this document. It should help you solve your problem: http://www.linuxhomenetworking.com/linux-hn/samba-trouble.htm inseart the rules for firewall as decribed there and i expect u will have ur problem solved. i have solved it and listen i dont know wot is the concept wot was the problem that these rules solved so if u find any concept plz let me know Regards Azeem _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus