Visual Studio 6 + Samba 2.2.5 misbehaves.

Mathew McKernan mathewmckernan at
Thu Aug 1 05:41:02 GMT 2002

Hi Fredrik,

This problem has been found with any server. Whether it be Samba or 2k or
NT. I have had this problem with a NT server, as we didn't have a NTP server
at the time, I used "net time \\server /set /yes" in the logon script. Made
life a lot easier. I use the "net time \\server" method at home as I run a
mixture of XP/98 workstations and a Samba server. I can't be bothered
finding a NTP sync program for 98 workstations *grin*.

Remember that with general NT/2k/XP permissions won't allow users to change
clock time, so in your Domain Policies/Local Security Policies/User Manager
(depending on OS) you need to set the advanced options to allow "Users can
change system time". By default Administrators and Power users only can.


Mathew McKernan
IT Services Department
After Hours Technician and Unix Server Administrator
m.mckernan at

----- Original Message -----
From: "Fredrik Ohrn" <ohrn at>
To: "Mike Gerdts" <Michael.Gerdts at>
Cc: "Samba Technical Mailing List" <samba-technical at>
Sent: Thursday, August 01, 2002 10:22 PM
Subject: Re: Visual Studio 6 + Samba 2.2.5 misbehaves.

> On 1 Aug 2002, Mike Gerdts wrote:
> > This sounds like you have clocks out of sync.  Be sure that the time on
> > your workstation, the Samba server, and any NFS servers that Samba may
> > get shares from all have clocks that are in sync.  I highly suggest
> > using NTP between all servers.  Once you have NTP running on a unix
> > server, you can convince win2k clients to sync with that server using:
> >
> > net time /setsntp:unixservername
> >
> That was a good start, the client and server was 20 seconds out of sync.
> Now the "file changed outside editor" message is gone. I just tried the
> same procedure on two XP boxes sharing files with their clocks out of
> sync. The problem never surfaced.
> Is this a bug in samba that it cant handle out of sync clocks or is it
> just not possible to do a better implementation?
> Also the "delayed write failed" doesn't happen right away as it did
> before. Now I have to wait untill samba disconnects the drive due to
> inactivity (as specified by deadtime). Stopping and restarting Visual
> Studio cures it (untill the nex timeout).
> Regards,
> Fredrik
> --
>    "It is easy to be blinded to the essential uselessness of computers by
>    the sense of accomplishment you get from getting them to work at all."
>                                                    - Douglas Adams
> Fredrik Öhrn                               Chalmers University of
> ohrn at

More information about the samba-technical mailing list