[Samba] Re: Odd problem with samba v.3.0.20b

2007-04-25 Thread Jason Gray

 Andreas Oster wrote:

 |   novaws20 (10.2.1.71) couldn't find service aoste
 |
 | The last five messages are the relavant ones. The share mentioned
 | (aoster) is the home share of user aoster. This not only happens with
 | the home share but with all other configured shares. The last letter
 | seems to truncated.
 |
 | Does anybody have a similar/same problem ?
 
 This is a Windows 2000 client bug.  The client then
 tryies again with the corrcet name.
 

Would this also affect XP clients?  It seems more like a cosmetic issue (the log
file gets clogged up).  I have the same problem on my servers.

Cheers,

Jason  




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Re: Odd problem with samba v.3.0.20b

2005-10-24 Thread Andreas Oster

Andrew Bartlett schrieb:

On Mon, 2005-10-24 at 13:22 +0200, Thomas Bork wrote:

Andreas Oster wrote:


[2005/10/24 12:29:33, 0] smbd/service.c:make_connection(798)
  novaws20 (10.2.1.71) couldn't find service aoste
The last five messages are the relavant ones. The share mentioned
(aoster) is the home share of user aoster. This not only happens with
the home share but with all other configured shares. The last letter
seems to truncated.
Does anybody have a similar/same problem ?
This is a *long* standing bug in samba 3.0.x (in all versions I tried up 
to 3.0.21pre1). Sometimes the last character  of the services is 
truncate here too, but the server is nevertheless working properly:


[2005/10/24 03:09:32, 0] smbd/server.c:main(805)
   smbd version 3.0.21pre1-01-for-eisfair started.
[...]
[2005/10/24 03:19:40.521307, 0, pid=11532] 
smbd/service.c:make_connection(802)

   tb3 (192.168.0.15) couldn't find service publi

The service is named 'public' and not 'publi'.


The trouble is that we don't know where the string is being trucated.
It is not as simple as 'in the tree connect', as ethereal shows the
string to be already truncated.  It must be somewhere else, but it also
appears non-fatal:  I've never heard of it actually breaking setups,
just making noise.

Andrew Bartlett



Dear Andrew, dear Thomas,

thank you for your reply to my posting. Actually, the
server works without any problems, but because I did
not recognize this truncation error in the logs before
the update, I was afraid, that this could brake
something :)
So I am trying to not bother any more :)


best regards

Andreas

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba