RE: [Samba] Bizarre problem - happens only under XP and not 2000
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 13 Mar 2003, Kier Darby wrote: Just an update on this - I removed Samba 2.2.7 from the RH8 system and reinstalled it using the Samba 2.2.1a-4 version from my Redhat 7.2 CDs, and the problem has miraculously disappeared... So what got broken between 2.2.1a-4 and 2.2.7-2? Could you possibly retest with a stock Samba 2.2.8 build? Or even test the SAMBA_3_0 cvs branch? Thanks. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+ibFBIR7qMdg1EfYRAojIAKCR3Rv7LAmCr2yt35mDxiEgDm9MlwCgpUE/ SYCgkzJ2oTmmstny9ur+o04= =XuT3 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Bizarre problem - happens only under XP and not 2000
I have a very strange problem, which no one has been able to fathom to
this point so I'm hoping that someone here may have encountered
something similar. I'd better note down some background details first.
Relevant machines involved:
Win2K Adv. Server SP3 (acting as Active Directory primary)
Win2K Pro SP3 (authenticates against Win2K server above)
WinXP Pro SP1 (authenticates against Win2K server above)
Redhat 7.2 running Samba 2.2.1a in 'domain' mode (password
server is Win2K server)
Redhat 8.0 running Samba 2.2.7 in 'domain' mode (password server
is Win2K server)
Here is the background of what I am trying to do. There is a CVS module
for a project I develop checked out on both of the Redhat machines,
which I manage using TortoiseCVS on the WinXP machine. Until this week I
was running only the RH7.2 machine and had no problems at all, but this
machine has got a little long in the tooth and so I built a new machine
to run RH8.
All the Windows machines are logged in using the same Active Directory
user, and I can access the shares on both Samba servers via Win2K and XP
with no problems, and have full read/write/delete permissions.
However, when I run a CVS update or checkout using the WinXP machine on
the RH8 box, I get lots of errors reporting that some directories that
were removed from the CVS module a long time ago could not be deleted as
they are not empty. Running the same update on the RH8 machine using
either of the Win2K boxes goes through with no errors. Running the same
CVS update on the RH7.2 machine with any of the Windows machines does
not produce the error.
This is what the CVS update ~should~ look like:
In \\plasma\home\kier\vb2: cvs -q update -d -P
CVSROOT=:pserver:{username}:{repository}
? language
? admin/spellcheck
? images/afp
? images/avatars
? images/styles/new/images
Success, CVS operation completed
And this is what it looks like when I run the same thing on the XP box
with the Samba 2.2.7 machine:
In \\plasma\home\kier\vb2: cvs -q update -d -P
CVSROOT=:pserver:{username}:{repository}
? language
? admin/spellcheck
? images/afp
? images/avatars
? images/styles/new/images
cvs update: cannot remove language: Directory not empty
cvs update: cannot remove images/styles/new/images: Directory not empty
cvs update: cannot remove images/avatars: Directory not empty
cvs update: cannot remove images/afp: Directory not empty
cvs update: cannot remove admin/spellcheck: Directory not empty
Success, CVS operation completed
Here is a summary of the results from running the update from different
machines:
Win2K with RH 7.2 / Samba 2.2.1aNO ERRORS
WinXP with RH 7.2 / Samba 2.2.1aNO ERRORS
Win2K with RH 8.0 / Samba 2.2.7 NO ERRORS
WinXP with RH 8.0 / Samba 2.2.7 ERRORS
From this I can only assume that there is something weird going on with
XP + Samba 2.2.7, as all other factors seem to be the same.
Has anyone got any clue whatsover as to what might be happening here?
Thanks for your help,
Kier Darby
Product Manager, vBulletin
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Bizarre problem - happens only under XP and not 2000
Just an update on this - I removed Samba 2.2.7 from the RH8 system and
reinstalled it using the Samba 2.2.1a-4 version from my Redhat 7.2 CDs,
and the problem has miraculously disappeared...
So what got broken between 2.2.1a-4 and 2.2.7-2?
Kier
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Kier Darby
Sent: 13 March 2003 16:47
To: [EMAIL PROTECTED]
Subject: [Samba] Bizarre problem - happens only under XP and not 2000
I have a very strange problem, which no one has been able to fathom to
this point so I'm hoping that someone here may have encountered
something similar. I'd better note down some background details first.
Relevant machines involved:
Win2K Adv. Server SP3 (acting as Active Directory primary)
Win2K Pro SP3 (authenticates against Win2K server above)
WinXP Pro SP1 (authenticates against Win2K server above)
Redhat 7.2 running Samba 2.2.1a in 'domain' mode (password
server is Win2K server)
Redhat 8.0 running Samba 2.2.7 in 'domain' mode (password server
is Win2K server)
Here is the background of what I am trying to do. There is a
CVS module
for a project I develop checked out on both of the Redhat machines,
which I manage using TortoiseCVS on the WinXP machine. Until
this week I
was running only the RH7.2 machine and had no problems at
all, but this
machine has got a little long in the tooth and so I built a
new machine
to run RH8.
All the Windows machines are logged in using the same Active Directory
user, and I can access the shares on both Samba servers via
Win2K and XP
with no problems, and have full read/write/delete permissions.
However, when I run a CVS update or checkout using the WinXP
machine on
the RH8 box, I get lots of errors reporting that some directories that
were removed from the CVS module a long time ago could not be
deleted as
they are not empty. Running the same update on the RH8 machine using
either of the Win2K boxes goes through with no errors.
Running the same
CVS update on the RH7.2 machine with any of the Windows machines does
not produce the error.
This is what the CVS update ~should~ look like:
In \\plasma\home\kier\vb2: cvs -q update -d -P
CVSROOT=:pserver:{username}:{repository}
? language
? admin/spellcheck
? images/afp
? images/avatars
? images/styles/new/images
Success, CVS operation completed
And this is what it looks like when I run the same thing on the XP box
with the Samba 2.2.7 machine:
In \\plasma\home\kier\vb2: cvs -q update -d -P
CVSROOT=:pserver:{username}:{repository}
? language
? admin/spellcheck
? images/afp
? images/avatars
? images/styles/new/images
cvs update: cannot remove language: Directory not empty
cvs update: cannot remove images/styles/new/images: Directory
not empty
cvs update: cannot remove images/avatars: Directory not empty
cvs update: cannot remove images/afp: Directory not empty
cvs update: cannot remove admin/spellcheck: Directory not empty
Success, CVS operation completed
Here is a summary of the results from running the update from
different
machines:
Win2K with RH 7.2 / Samba 2.2.1a NO ERRORS
WinXP with RH 7.2 / Samba 2.2.1a NO ERRORS
Win2K with RH 8.0 / Samba 2.2.7 NO ERRORS
WinXP with RH 8.0 / Samba 2.2.7 ERRORS
From this I can only assume that there is something weird
going on with
XP + Samba 2.2.7, as all other factors seem to be the same.
Has anyone got any clue whatsover as to what might be happening here?
Thanks for your help,
Kier Darby
Product Manager, vBulletin
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
