Re: [Samba] smb log error-Transport end point/getpeername
Den 11-02-2005 kl 12:09 skrev David Rankin: From: Josh Kelley [EMAIL PROTECTED] david rankin wrote: Well, no, I'm not positive, but when whatever hangs, I get a big slowdown in file access, file open, etc.. from XP. When I then go and check the logs the transport end point and getpeername is the only thing that shows up in the log. I admit I haven't had time to put up a console and check in the past few days. It is definately an XP issue. It occurs on both Suse 9.0 and Mandrake 7.2 with 3.0.7. It occurred with all the 2.0 and 2.2 sambas as well. I'll keep an eye on it and report back. This is a bit of a shot in the dark, but do you have port 80 firewalled off on your Samba server? It's my understanding that by default, XP will try to access network drives via WebDAV before trying SMB, and a firewall that drops attempted connections to port 80 or that doesn't respond with a TCP reset can cause noticeable slowdowns in connections from XP. Thanks for the 'shot', but in my case, port 80 is wide open I have followed this thead because I have had the same troubles. On the Primary server I have used socket = IP-addres of server and I have both the lmhost og the hosts files up to date When I now set up a second server on another workgroup but same subnet and disable port 443 in Samba and only uses port 139, it seems that it all works ok. I am still worried though, I have really had a lot of trouble and lost many hours trying to solve this problem. Its was not only slowing the system when the errors occured, I experienced database errors if a program was writing to a database when it happended. And the database has to be repaired. If anyone knows more of this problem do write, I ko not know why these correction to the smb.cfg helps and why they ar necessary. Bjørn Fahnøe -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
david rankin wrote: Well, no, I'm not positive, but when whatever hangs, I get a big slowdown in file access, file open, etc.. from XP. When I then go and check the logs the transport end point and getpeername is the only thing that shows up in the log. I admit I haven't had time to put up a console and check in the past few days. It is definately an XP issue. It occurs on both Suse 9.0 and Mandrake 7.2 with 3.0.7. It occurred with all the 2.0 and 2.2 sambas as well. I'll keep an eye on it and report back. This is a bit of a shot in the dark, but do you have port 80 firewalled off on your Samba server? It's my understanding that by default, XP will try to access network drives via WebDAV before trying SMB, and a firewall that drops attempted connections to port 80 or that doesn't respond with a TCP reset can cause noticeable slowdowns in connections from XP. Josh Kelley -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
From: Josh Kelley [EMAIL PROTECTED] david rankin wrote: Well, no, I'm not positive, but when whatever hangs, I get a big slowdown in file access, file open, etc.. from XP. When I then go and check the logs the transport end point and getpeername is the only thing that shows up in the log. I admit I haven't had time to put up a console and check in the past few days. It is definately an XP issue. It occurs on both Suse 9.0 and Mandrake 7.2 with 3.0.7. It occurred with all the 2.0 and 2.2 sambas as well. I'll keep an eye on it and report back. This is a bit of a shot in the dark, but do you have port 80 firewalled off on your Samba server? It's my understanding that by default, XP will try to access network drives via WebDAV before trying SMB, and a firewall that drops attempted connections to port 80 or that doesn't respond with a TCP reset can cause noticeable slowdowns in connections from XP. Thanks for the 'shot', but in my case, port 80 is wide open -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankin-bertin.com -- -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2/10/2005 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 david rankin wrote: | |I'm trying to solve some log errors I getting. I | have samba 3.0.7 installed on Suse 9.0. It has been | happening intermittently for several months. I don't know | if this is XP client related or what. Any thoughts: | The errors are: | | Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] | lib/util_sock.c:get_peer_addr(1000) | Feb 9 20:00:33 skyline smbd[14408]: getpeername failed. Error was | Transport endpoint is not connected I know that Windows XP clients try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. This is probably what you are seeing. cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCC2ZmIR7qMdg1EfYRApRrAKCueTKNLmp2eIpxsDBwXxeTPCPnFwCdFJha cP0Ftaoy1weqJ3J2SJLYTxw= =Rjrf -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
From: Gerald (Jerry) Carter [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 david rankin wrote: | |I'm trying to solve some log errors I getting. I | have samba 3.0.7 installed on Suse 9.0. It has been | happening intermittently for several months. I don't know | if this is XP client related or what. Any thoughts: | The errors are: | | Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] | lib/util_sock.c:get_peer_addr(1000) | Feb 9 20:00:33 skyline smbd[14408]: getpeername failed. Error was | Transport endpoint is not connected I know that Windows XP clients try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. This is probably what you are seeing. Thanks Jerry, That makes sense. No doubt an intentional feature from M$. Is there any way to get around it? When it occurs, there is a real slowdown in the connection. It is intermittent so it doesn't last that long, but it is sure annoying when it does. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
Den 10-02-2005 kl 13:06 skrev david rankin: From: Gerald (Jerry) Carter [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 david rankin wrote: | |I'm trying to solve some log errors I getting. I | have samba 3.0.7 installed on Suse 9.0. It has been | happening intermittently for several months. I don't know | if this is XP client related or what. Any thoughts: | The errors are: | | Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] | lib/util_sock.c:get_peer_addr(1000) | Feb 9 20:00:33 skyline smbd[14408]: getpeername failed. Error was | Transport endpoint is not connected I know that Windows XP clients try to connect to port 139 and 445 in parallel and drop the connection to port 139 if the connect to 445 is successful. This is probably what you are seeing. Thanks Jerry, That makes sense. No doubt an intentional feature from M$. Is there any way to get around it? When it occurs, there is a real slowdown in the connection. It is intermittent so it doesn't last that long, but it is sure annoying when it does. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba *** Citat slut *** -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 david rankin wrote: | | I know that Windows XP clients try to connect to port | 139 and 445 in parallel and drop the connection to port | 139 if the connect to 445 is successful. This is probably | what you are seeing. | | | Thanks Jerry, | |That makes sense. No doubt an intentional feature from | $. Is there any way to get around it? When it occurs, there is | a real slowdown in the connection. It is intermittent so | it doesn't last that long, but it is sure annoying when | it does. You could set 'smb ports = 139' for force netbios connections. Are you sure this is causing a slowdown ? Other than the overhead of forking a new smbd temporarily. cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCC8HNIR7qMdg1EfYRAkKSAJ9pdaw6mytjrdM7L6UI9Llsa6Q5YwCdGcuS HpGoypNKX8ePXLzWp7u+DnY= =6app -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smb log error-Transport end point/getpeername
From: Gerald (Jerry) Carter [EMAIL PROTECTED] david rankin wrote: | | I know that Windows XP clients try to connect to port | 139 and 445 in parallel and drop the connection to port | 139 if the connect to 445 is successful. This is probably | what you are seeing. | | | Thanks Jerry, | |That makes sense. No doubt an intentional feature from | $. Is there any way to get around it? When it occurs, there is | a real slowdown in the connection. It is intermittent so | it doesn't last that long, but it is sure annoying when | it does. You could set 'smb ports = 139' for force netbios connections. Are you sure this is causing a slowdown ? Other than the overhead of forking a new smbd temporarily. Well, no, I'm not positive, but when whatever hangs, I get a big slowdown in file access, file open, etc.. from XP. When I then go and check the logs the transport end point and getpeername is the only thing that shows up in the log. I admit I haven't had time to put up a console and check in the past few days. It is definately an XP issue. It occurs on both Suse 9.0 and Mandrake 7.2 with 3.0.7. It occurred with all the 2.0 and 2.2 sambas as well. I'll keep an eye on it and report back. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
