Help and Support
 

powered byLive Search

Macintosh Clients May Hang Temporarily with Multiple Mac Volumes

View products that this article applies to.
Article ID:162189
Last Review:November 1, 2006
Revision:1.1
This article was previously published under Q162189

SYMPTOMS

On a Windows NT MacFile server with multiple Macintosh volumes, Macintosh clients may experience wait times showing network busy (-><-) for varied lengths of time while Afp calls requiring an exclusive lock retry. This issue can be verified in a network trace where Macintosh clients are seen to be issuing retry calls AfpGetFileDirParms and AfpCloseFork until an exclusive volume lock on the MacFile server is released.

Back to the top

CAUSE

Where multiple volumes exist, as file status changes were being processed across various Macintosh volumes, an exclusive and volume-specific lock was being applied during volume change notify processing. In a particular instance, a volume-specific lock was not being released. This lock was released as more volume changes were processed; however, wait times varied.

Back to the top

RESOLUTION

The issue was addressed in a code change that manages the change notify processing more efficiently and resolves the held lock condition.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.51 and 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K

Back to the top

MORE INFORMATION

In addition, performing the following actions can have a positive impact on Macintosh performance:
1.Disabling the Catsearch Function - this requires the hotfix for Windows NT version 3.51 or Service Pack 3 or later for Windows NT version 4.0 and a registry change.
2.Disabling EnableOplocks on the NT Server (registry change only).
3.Reducing AppleTalk Traffic by using a 3rd party application called Less Talk on the Mac client.
4.If Microsoft Mail is being used -- reset the PC Polling interval on the MS Mail client to reduce the frequency of polling for new mail.
5.Apply a hotfix that resolved a record locking issue -- "Record Unlock After PC Release" (this fix should be included in the hotfix under item number one.
For more information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: 158796 (http://support.microsoft.com/kb/158796/EN-US/)
TITLE : Macintosh Clients Connected to WinNT Server Appear to Hang

ARTICLE-ID: 129202 (http://support.microsoft.com/kb/129202/EN-US/)
TITLE : PC Ext: Explanation of Opportunistic Locking on Windows NT

ARTICLE-ID: 150879 (http://support.microsoft.com/kb/150879/EN-US/)
TITLE : SFM: Macintosh Computers Create a Lot of Network Traffic

ARTICLE-ID: 150978 (http://support.microsoft.com/kb/150978/EN-US/)
TITLE : SFM: Optimizing Polling Rate for Macintosh Clients for PCMail

ARTICLE-ID: 159994 (http://support.microsoft.com/kb/159994/EN-US/)
TITLE : SFM Does Not Unlock Record After PC Releases Lock

Back to the top

APPLIES TO
•Microsoft Windows NT Server 3.51
•Microsoft Windows NT Server 4.0 Standard Edition

Back to the top

Keywords: 
kbbug kbnetwork KB162189

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by E-mail, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.