Hi! No, all PC's are in domain, and domain controller is that time source.

Aha, then that might be where the problem comes from. Is the lanshare also in the domain?

I have never put my editing systems in a domain. The rights issues avid and Unity have, and the lack of documentation, have stopped me from ever trying. The forum user that might be able to help you is DocAvid.

Maybe if you send him a private mail he will join this thread.

But lanshare can be in a domain (there is a description in avid documentation how to setup lanshare in domain).

There is a tool, named Server Log Viewer. And this info from that program:

Local transport enabled
Target mode transport enabled
GetSystemInfo returned 4 logical processors
GetProcessAffinityMask returned f for system and 1 for process
Binding thread to processor(s) 1 (mask)
MediaNetwork 4.2.1 Server 4.2.1 has successfully started.
Avid Unity Server (Version 4.2.1) is running.
[Press ? for interactive help.]

Physical Mem 2046 MB, Auto Mount Size 500 MB, Disk Limit 32, File Limit 250000, Dir Limit 10000
Allocated 1042 MB
Reserved 54400 bytes for requests
Reserved 5120 bytes for internal requests
Reserved 40960 bytes for internal responses
Reserved 27648 bytes for net buffers
Reserved 640000 bytes for 10000 channels
Reserved 2097248 bytes for heap validation
Reserved 32768480 bytes for disk validation
Reserved 2164800 bytes for transaction journal
Reserved 880000 bytes for open segments
Total 5910176 bytes reserved

Max Users allowed by dongle is 4
Mirroring is not allowed by dongle

Virtual server name: AVID-99C7B8294AFC

Initializing IBOD target mode communication area
Enabling the fc target mode communication transport
Enabling the local communication transport
Is a LANshare, so the LUN masking feature is not used...
Found a partition -- need 15 disks and have 15
Logical Unit 0, named Drive 000 is \Device\Harddisk16
Logical Unit 1, named Drive 001 is \Device\Harddisk2
Logical Unit 2, named Drive 002 is \Device\Harddisk3
Logical Unit 3, named Drive 003 is \Device\Harddisk4
Logical Unit 4, named Drive 004 is \Device\Harddisk5
Logical Unit 5, named Drive 005 is \Device\Harddisk8
Logical Unit 6, named Drive 006 is \Device\Harddisk6
Logical Unit 7, named Drive 007 is \Device\Harddisk7
Logical Unit 8, named Drive 008 is \Device\Harddisk9
Logical Unit 9, named Drive 009 is \Device\Harddisk13
Logical Unit 10, named Drive 010 is \Device\Harddisk10
Logical Unit 11, named Drive 011 is \Device\Harddisk11
Logical Unit 12, named Drive 012 is \Device\Harddisk12
Logical Unit 13, named Drive 013 is \Device\Harddisk15
Logical Unit 14, named Drive 014 is \Device\Harddisk14

Spare disk \Device\Harddisk1
Found data disks.

Meta Set 1
Disk 0 \Device\Harddisk16
Disk 3 \Device\Harddisk4

Meta Set 2
Disk 1 \Device\Harddisk2
Disk 4 \Device\Harddisk5

Meta Set 3
Disk 2 \Device\Harddisk3
Disk 5 \Device\Harddisk8

Did not lock section: addr 42edd000, len 8192, retry 0, status 87
Failed to lock 1 sections
Memory lock down complete. Took 7 seconds

Locked 1119768576 bytes into working set in 285 of 286 sections with 1 errors
Working set is now 1124831232 min and 1126039552 max
Looking for active file managers
Allowing server operation
Set Created Fri Apr 04 10:32:52 2008

Meta Set 1 Sequence Number is 5557492 using 2 disks
Meta Set 2 Sequence Number is 5557493 using 2 disks
Meta Set 3 Sequence Number is 5557494 using 2 disks
Local Disk Sequence Number is 5557491
Loading metadata from Meta Set 3


Partition0 Mounted from Meta Set 3
Removing Auto.Import
Server created a new recovery file.

Area 0, total 500 MB, unlocked 344 MB, locked 155 MB
Area 1, total 500 MB, unlocked 344 MB, locked 155 MB
Partition mount completed
Server startup complete. Took 50 seconds

Watchdog - enabling watching of metadata saving

"Locked 1119768576 bytes into working set in 285 of 286 sections with 1 errors"  - what does this "1 errors" mean I don't understand.

The problem solved!

1) We disabled unnecessary resources (services)

2) We played with antivirus software

Files become visible. It looks like something ate part of system memory.

Thank you all for advice!

Update to 4.2.3 at your earliest convenience,  or 4.2.4 if you plan on ever attaching Windows 2003 server clients.  4.2.1 was not a fun build.

The question about metadata,  files are either there or not with a metadata problem-  that would be a global issue,  and you would prolly have obnoxiously high file and folder counts.

What AV solution are you using?

JDS