Services for Macintosh

I've got a Windows 2003 R2 Server running SFM and am having trouble with a
specific share. It takes the server up to an hour to make the share visible
when I share it from the New Share wizard in computer management. I have 3
other shares that only take a few minutes to appear for Macintosh users.
While this share is visible, the server's system process jumps to 25% system
cpu and stays there indefinitely.

Related to this, I believe, is the fact that this server is repeatedly
running out of system resources and crashing. I'm forced to restart it once
all the nonpaged pool is empty. I do not have any 3rd party applications on
this sytem other than McAfee VirusScan Enterprise 8.0i with Patch 13
installed. The crashes have been occurring within several hours of restart.

Is there an issue with large SFM volumes on Win2k3 servers? Up to this
point, I've had very few users connecting to this server (<10) and will be
having more than 100 connecting in the near future.


--
GCS Tech

Hello,

Thanks for posting.

I didn't hear any information that SFM will cause memory leak. As you said,
3 other shares work well. I noticed that you install McAfee AV in the
system. To isolate the problem, I suggest you temp disable or remove this
software to see results. If the problem persists, please also disable
Network firewall on the Windows Server 2003.

If the problem still occurs, Please use the Process Explorer tool to
collect the process information for me.
================================================== ==========
a) Download and install the Process Explorer.
http://sysinternals.com/ntw2k/freeware/procexp.shtml

b) When the error message occurs, click OK and lunch the Process Explorer
utility.

c) Click View->Lower Pane View and select View DLLs.

d) Select the explorer.exe process, click File and select Save as to save
the information to a TXT file.

Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------
>>From: "GCS Tech" <(E-Mail Removed)>
>>Subject: Services for Macintosh
>>Date: Wed, 13 Sep 2006 10:30:19 -0400
>>Lines: 22
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>>X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <(E-Mail Removed)>
>>Newsgroups: microsoft.public.windows.server.networking
>>NNTP-Posting-Host: 165.139.169.189
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFT NGP05.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.networking:42337
>>X-Tomcat-NG: microsoft.public.windows.server.networking
>>
>>I've got a Windows 2003 R2 Server running SFM and am having trouble with a
>>specific share. It takes the server up to an hour to make the share
visible
>>when I share it from the New Share wizard in computer management. I have
3
>>other shares that only take a few minutes to appear for Macintosh users.
>>While this share is visible, the server's system process jumps to 25%
system
>>cpu and stays there indefinitely.
>>
>>Related to this, I believe, is the fact that this server is repeatedly
>>running out of system resources and crashing. I'm forced to restart it
once
>>all the nonpaged pool is empty. I do not have any 3rd party applications
on
>>this sytem other than McAfee VirusScan Enterprise 8.0i with Patch 13
>>installed. The crashes have been occurring within several hours of
restart.
>>
>>Is there an issue with large SFM volumes on Win2k3 servers? Up to this
>>point, I've had very few users connecting to this server (<10) and will be
>>having more than 100 connecting in the near future.
>>
>>
>>--
>>GCS Tech
>>
>>
>>