Home | Doel |_Meetings_|_Tips/Tricks_|_Editor Database _|_Links_|_Contact_|_RSS Avid
Stuur deze site door
 

 

Slow navigation in Windows Explorer on Unity ISIS

Description: Browsing in Windows explorer (or double-clicking My Computer) is sluggish when there are ISIS workspaces mounted.
Browsing in Windows explorer (or double-clicking My Computer) is sluggish when there are ISIS workspaces mounted.
Other Products: Avid Unity ISIS
The following is a workaround for this problem. This should be applied to Unity ISIS clients only.

1. Go to the System Director.
2. Launch System Director Control Panel and click the configuration tab.
3. Click the general configuration button and make a note of the virtual system director name. Close this window.
4. Go to each client and do the following.
5. Right click on My Network places and get properties
6. Right click on the adaptor attached to ISIS (Intel PRO Server) and get properties
7. Highlight "Internet Protocol (TCP/IP)" and click properties
8. Click the Advanced button
9. Click the WINS tab
10. Verify that Enable LMHOSTS lookup is checked and the Radio button for "Enable NetBIOS over TCP/IP" is selected.
11. Click OK and close all windows
12. Launch notepad and create a new file.
13. Add the following entries to the file. Please take care not to change any other entries or add any extra characters. There should be a tab between the IP and the name.
127.0.0.1 <virtual system director name> #PRE
The virtual name should match exactly to what is entered into the System Director Control Panel.
14. Save out this file with the name LMHOSTS (with no extension) to the following location c:\windows\system32\drivers\etc

Note: If you already have a LMHOSTS file, simply add this above entry to your existing LMHOSTS file.
To verify above
1. Launch Windows Explorer and navigate to a workspace. It should be quick.
2. Open a command window and type the following command. nbtstat -c
3. This will output the netbios cache. You should see the virtual system director name with IP of 127.0.0.1 listed in there.
4. Verify that you can ping both by that name and IP.