Re: Slow opening of files

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Lanwench,
this is my login script:
\\CMCSERVER\Clients\Setup\setup.exe /s CMCSERVER
net use y: \\CMCSERVER\data\CMC
net use z: \\CMCSERVER\data\fileserver\cmc
net use l: \\CMCSERVER\Futurelink

I have only tried the net use command from the server and the above are
showing as disconnected? I haven't access to a workstation at present
(working remotely), will try tomorrow, in the meantime I will amend the
script as per you recommendations.

Many thanks
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23LgLJyhfIHA.2448@xxxxxxxxxxxxxxxxxxxxxxx
TEB <ThickEB@xxxxxxxxx> wrote:
Hi Henrik,

I am not getting any errors anywhere, everything was setup via the
wizards, I am beginning to wonder if it is a mapped drive issue, all
shared data is mapped via login scripts and are used extensively by
the users.

Type

net use

in a command prompt & see if there are any drives in a disconnected state
or any unavailable shares.

What's in your login script? I begin mine with

net use * /del

and then map all drives using the

/persistent:no

switch.




"Henrik" <hear01@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eGhKhJhfIHA.5620@xxxxxxxxxxxxxxxxxxxxxxx
Ted, Lanwench, anyone :-)

Can this be a DNS/name resolution issue?
IMO It can be.

--
Henrik Arenblad, MCP SBS,







"TEB" <ThickEB@xxxxxxxxx> wrote in message
news:eeWEQDhfIHA.4536@xxxxxxxxxxxxxxxxxxxxxxx
I have disabled the AMON module on the server, on the member server
we had removed NOD completely, have done your suggestions, no joy I
am afraid. Many thanks
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:u1V5vlgfIHA.1900@xxxxxxxxxxxxxxxxxxxxxxx
TEB <ThickEB@xxxxxxxxx> wrote:
Hi Lanwench,
Yes NOD32 is on the servers, and is setup according to NOD32
support staff, the options on file monitoring with the NOD "AMON"
module is: Scan ON:
Open = checked

That's bad. Untick that.

Execute = checked

Same as above.


Create = checked

Media Options:
Diskette = checked
Local disks and Media = checked
Network = unchecked (as per support staff)
I have disabled the "AMON" module and this has no effect.
The core kernel driver for NOD cannot be stopped (greyed in
services.msc)

That sounds like a problem to me!

Have tested from clients with and without Anti Virus - same
issues as described.

You've tried it without your *client* antivirus enabled, but that
isn't the issue. The issue is likely on the *server*.

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:ubC84ZgfIHA.748@xxxxxxxxxxxxxxxxxxxxxxx
TEB <ThickEB@xxxxxxxxx> wrote:
Hello,
SBS 2003 Standard
Anti Virus: NOD32
2 NICS, All DNS points to the internal NIC, the CEIW was run,
DHCP installed and servicing clients without issue.
Clients are experiencing slow opening of office files when
opened by Windows Explorer and if they look in Task Manager
they see the folder and the file listed twice in the
Applications Tab and not responding is the Status and the file
could take anything up to a couple of minutes to open, once the
document is opened Task Manager shows just the one file open,
if they open the file via the Office App itself the file opens
immediately. The cabling has recently been rewired and a gigabyte
switch
installed but this hasn't helped, I have spoken to NOD32 and
they say I have configured the File monitoring correctly,
Veritas Backup Exec is on latest software and Open File locks
isn't used anyway. The client has a member server and the same
thing happens when they try and open a document from there as
well, the client is now wanting to flatten the SBS box but I am
dead against this at present. Clients are on Win XP Pro fully
updated with a mix of Office 2003
and 2007, also opening an email document attachment directly
from the email causes the same delay but in Task Manager is
shows upto to 4 files and folders until the document opens which
then drops
down to just the one instance.
Client also has a branch office with a PWAN between the two and
the same things happens there as well, this was happening
before the PWAN was installed though.

There are no errors in any event logs with relation to this
issue (that I could see). Lastly we tried this with a client
without any NOD32 or anti virus installed and received the same
delays. Any help/pointers would be greatly appreciated

You've got NOD32 on your server as well, one presumes. Disable
it and test.

Make sure your realtime antivirus everywhere is set to scan on
writes only, not reads....





.

Relevant Pages

  • Re: Slow opening of files
    ... You shouldn't be mapping drives on the server at all - no login script ... Also, the ipconfig /all from the server & a client, just in case. ... shows upto to 4 files and folders until the document opens ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow opening of files
    ... Yes NOD32 is on the servers, and is setup according to NOD32 support ... You've tried it without your *client* antivirus enabled, ... App itself the file opens immediately. ... You've got NOD32 on your server as well, ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow opening of files
    ... and then map all drives using the ... Yes NOD32 is on the servers, and is setup according to NOD32 ... if they open the file via the Office App itself the file opens ... The client has a member server and the same ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow opening of files
    ... I am not getting any errors anywhere, everything was setup via the wizards, ... Yes NOD32 is on the servers, and is setup according to NOD32 support ... You've tried it without your *client* antivirus enabled, ... App itself the file opens immediately. ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow opening of files
    ... I have disabled the AMON module on the server, on the member server we had ... Yes NOD32 is on the servers, and is setup according to NOD32 support ... You've tried it without your *client* antivirus enabled, ... App itself the file opens immediately. ...
    (microsoft.public.windows.server.sbs)