New issue with a New Vista Client - couldn't find service
in [Samba]
|
Prev: [Samba] openldap error messages after upgrade 3.3.6 -> 3.4.2
Next: [Samba] ln: creating symbolic link `file.txt': Operation not supported, Mounted to Windows 2003 shared
From: John Drescher on 17 Oct 2009 10:10 > Running a samba server version 3.0.7 on a FreeBSD box > You can not expect a version of samba produced over 5 years ago to work with vista. Upgrade to 3.3.9 or 3.4.2. John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Matthew Dickinson on 17 Oct 2009 10:10 Likewise: Situation: I'm seeing lots (~500k per day) of log entries like: smbd[13939]: itlab-pc06 (::ffff:10.51.51.103) couldn't find service it261 In this case, the last character of the request is truncated - it should be it2610 I'm seeing the same/similar issue to http://lists.samba.org/archive/samba/2009-March/147277.html And http://lists.samba.org/archive/samba/2009-October/150998.html I've dismissed this over the last few weeks as a minor inconvenience, but I'm now convinced that it's affecting the performance of the Windows client machines that are connecting to it - a 30 second operation on local disk, takes upwards of 5 mins over a network connection, generating thousands of entries similar to the above. This isn't unique - over the last 16 business hours (it's in a lab in a university dept.), there have been ~900k similar entries. It's also not just for this particular share, it's on all of the "home" shares that have been accessed, and also all of the 4 "defined" shares in smb.conf. Also, it's across many different hosts, and affecting different Windows OS's. My primary testing has been using Windows7 - I have a lab of 33 machines with this OS, but I believe I've also seen this from Windows XP and Vista hosts. Shares on turing - Dell PE2950 connected to Equalogic PS6000 via iSCSI, 1TB volume formatted EXT3 for /content and seperate 1TB EXT3 volume for /students [it2610] comment = "IT2610 AV1" path = /content/it/it2610 writable = yes browseable = yes create mask = 0600 directory mask = 0700 [homes] comment = Home Directories browseable = no writable = yes create mask = 0604 directory mask = 0704 Also, it's not restricted to this particular host: Turing (RHEL5) - tried versions samba-3.0.33-3.14.el5 samba3x-3.3.5-0.40.el5 Babbage (RHEL4) exhibits the same, samba-3.0.33-0.17.el4 Babbage which has higher use (in the last 48 hours), has seen a total of 150 different host/service combinations from the logs, across different networks with different clients and different OS's. Matthew On 10/17/09 8:59 AM, "Brian" <bbayorgeon(a)charter.net> wrote: > Sorry if this a duplicate, previous post was with a disfunctional email > address. > > > > Running a samba server version 3.0.7 on a FreeBSD box > > > > Life has been fine with XP and so forth > > > > I added a new vista workstation to my small network > > > > Vista found my shares and I am able to access them with no jerking around > with authentication types or such as I use appropriate pw and user name to > log into the vista box. > > > > Problem is vista is spamming my server, taking up >50% cpu time and creating > a 500K log file every 2 min > > > > it is filling the log file with > > > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > > > > > the service name is truncated also by on letter > > > > thanks in advance for your help > > > > Brian > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
From: Brian on 25 Oct 2009 01:00
OK, Since we last spoke I built a new server, installed FBSD 7.2 and installed the samba package 3.3.3 and the results were the same. The new server is still being flooded with: Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Oct 24 11:00:14 oldjunk smbd[84681]: [2009/10/24 11:00:14, 0] smbd/service.c:make_connection(1292) Oct 24 11:00:14 oldjunk smbd[84681]: dadsdesktop (10.0.2.123) couldn't find service roo Literally 500K log files in a few seconds. Its modern hardware with a intel Atom processor and so forth and its spending 24% processor time filling out logs. John suggest 3.3.8 and I realized I was at 3.3.3 so I upgraded samba to 3.3.8 and got the same result! So I have had version 3.0.something (older FBSD implementation) through 3.3.8 running (7.2 FBSD implementation) and all of them are being flooded by vista. Ya ya I know...blame Gates, but there must be a fix here some place? thanks for your help in advance. Brian -----Original Message----- From: John H Terpstra - Samba Team [mailto:jht(a)samba.org] Sent: Saturday, October 17, 2009 9:10 AM To: Brian Subject: Re: [Samba] New issue with a New Vista Client - couldn't find service On 10/17/2009 08:59 AM, Brian wrote: > Sorry if this a duplicate, previous post was with a disfunctional email > address. > > > > Running a samba server version 3.0.7 on a FreeBSD box Please update your version of Samba to at 3.3.8 or later (preferably 3.4.2 or later). Samba-3.4.2 is a whole different animal from 3.0.7 - life has moved on. Vista is also a whole different animal than XP and requires the later Samba releases for smooth interoperability. cheers, John T. > Life has been fine with XP and so forth > > > > I added a new vista workstation to my small network > > > > Vista found my shares and I am able to access them with no jerking around > with authentication types or such as I use appropriate pw and user name to > log into the vista box. > > > > Problem is vista is spamming my server, taking up >50% cpu time and creating > a 500K log file every 2 min > > > > it is filling the log file with > > > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > [2009/10/17 08:11:28, 0] smbd/service.c:make_connection(800) > > dads-pc (10.0.2.124) couldn't find service roo > > > > > > the service name is truncated also by on letter > > > > thanks in advance for your help > > > > Brian > > > -- John H Terpstra "If at first you don't succeed, don't go sky-diving!" -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba |