Hello list,
I have recently updated our companys fileserver from version
3.0.13 to 3.0.20 and shortly afterwards to 3.0.20b. Since then
I have a prolem with my shares, at least the logs state that
there is a problem :(
The server acts as a domain member server. The domain is controlled
by a
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Oster wrote:
| novaws20 (10.2.1.71) couldn't find service aoste
| novaws20 (10.2.1.71) couldn't find service aoste
| novaws20 (10.2.1.71) couldn't find service aoste
| novaws20 (10.2.1.71) couldn't find service aoste
| novaws20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
| 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
Gerald (Jerry) Carter wrote:
It's not our bug Andrew. I've generated traces from
a Win2K - WinXP that show the exact same thing. It's
a Windows 2000 client bug.
tb3 is a XP SP2 client. Thats why it must be a Windows 2000 *and*
Windows XP client bug.
der tom
--
To unsubscribe from this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bork wrote:
| Gerald (Jerry) Carter wrote:
|
| It's not our bug Andrew. I've generated traces from
| a Win2K - WinXP that show the exact same thing. It's
| a Windows 2000 client bug.
|
| tb3 is a XP SP2 client. Thats why it must be a
On Monday 24 October 2005 20:45, Gerald (Jerry) Carter wrote:
Andrew Bartlett wrote:
| 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
