Error: “Error Reading File”.
Introduction
Error “1104 Error Reading File” happens when the network or file system takes too long to respond to BarScan. This is not a BarScan application error, but is a network, server or security (such as your anti-virus) level problem. It is also an umbrella error frequently caused by one of the following two Microsoft Windows errors:
Here is an image of the error message that you may receive from BarScan:
Below you will find information on many of the causes. However, most of the time this error is caused either by one of the following:
1. Server level processes such as those performing firewall, file indexing, and anti-virus functions. (e.g., an anti-virus program interactively scanning BarScan data files while BarScan is being used) or
2. A user leaving a BarScan session idle too long – especially during a remote session where the user is connected remotely to the server or
3. Sleep Mode disrupts the connection. If you use BarScan on a regular basis for long period of time, we recommend that you disable sleep mode. If your computer enters Sleep Mode (low-power suspend mode) this can also cause this error. When Windows enters Sleep Mode, files are disconnected from your server or
4. A VPN (virtual private network) client restarting the VPN tunnel.
Antiviral scanning operations delay file reads just enough to trigger this error. Leaving BarScan idle too long may cause the server to drop open file connections thinking that the workstation has disconnected due to inactivity. A VPN tunnel may be reset for a variety of reasons, but can generally be triggered by an new update and a change in configuration. This kind of problem can be checked by examining its log.
Note that BarScan has the capability of logging users out of BarScan if they leave a session idle for too long. This is not the default of BarScan, but rather something that can be setup. The Knowledge Base Article discussing this is here: Scripting Feature In BarScan
Any network might create this error infrequently, but if this error begins to repeat itself then we recommend that you involve your IT department to find a resolution. BarScan, Inc. provides limited technical support on this issue since this is a customer’s internal network issue.
What the BarScan Administrator can do:
As mentioned in the introduction, most causes of this problem may need the involvement of your IT department. However, there are things that the BarScan administrator can and should do. See below for details about how to do each listed item.
1. Run a BarScan Table Integrity operation.
2. Verify that your version of BarScan is 3.2.1 or higher. Inform IT that it needs to be upgraded or reach out to us.
3. Verify with the IT department that BarScan data files are not being scanned by an anti-virus package. The Knowledge Base discussing this is here: Our Anti-Virus Is Causing BarScan To Run Slowly
4. Enforce a policy of NOT allowing BarScan to sit idle too long. Have all users log out of BarScan when they are not using the program or use the BarScan Scripting Language to log users out.
5. Coordinate with IT to update workstation SMB2 caching.
6. Ask IT to check the VPN client logs to see if a disconnect/restart at the time of the problem.
What the IT Department can do:
As mentioned in the introduction, many causes of this problem may need the involvement of the IT department. These are listed here in the order they should be checked. Some of these will be easier if you get information from the BarScan application itself. Coordinating with the BarScan Administer (Master User) will make this easier. See below for detail about how to do each listed item.
1. Check the VPN workstation/client logs to determine whether or not a disconnect occurred.
2. Verify that your security software is NOT scanning BarScan data folders (i.e. any subfolder of the BarScan root folder). If it is, disable this.
3. Verify that the version of BarScan is 3.2.1 or higher. Update BarScan if it is not.
4. Check to see if BarScan users are accessing BarScan using a mapped drive. If so, verify that the mapped drive connection timeout is not too short.
5. Coordinate with the BarScan Administrator to update workstation SMB2 caching.
6. Verify SMB1/SMB2 settings.
7. Adjust workstation SMB2 cache settings.
8. Check through some of the other causes listed below.
Account Details
Below is the list of recommended actions. Some can be done by the BarScan administrator, some by the IT department, and some by both in coordination. Please note that this is not an exhaustive list of actions nor is it a solution to all possible causes of this error.
1. Run a BarScan Table Integrity operation.
Whenever this error occurs a BarScan Table Integrity should be performed immediately because this error leaves the state of table indexes in a possible corrupted state. A Table Integrity must be done to correct this. The BarScan Administrator should immediately perform a BarScan Table Integrity upon detection of this error to minimize or avoid data corruption, while observing that the process completes successfully without any warnings. If possible, performing the Table Integrity from the server console rather than from a network workstation is recommended. This should be done to avoid further errors over the network. We recommend that the user continue performing the Table Integrity on a regular basis, for example every 4 weeks.
2. Verify that your version of BarScan is 3.2.1 or higher.
Version 3.2.1 and higher resolves BarScan runtime issues that may contribute to this error. You may also get a BarScan fatal c0000006 error rather than the “Error Reading File” message. If so, Microsoft has a web page to specifically address the error. It contains the basic cause and some suggested resolutions. Here is the link: C0000006 Error And Troubleshooting Suggestions If you have a version of BarScan older than 3.2.1 you must upgrade to the latest version. The latest version fixes a number of issues related to DLL placement.
3. Verify that BarScan data files are not being scanned by anti-virus software.
BarScan opens and closes many data files during its normal operation. Anti-virus packages may scan those files at the time they are opened. Application files are scanned when activated to make sure that they are not harmful to your network. By its nature, this can severely reduce access speed and sometimes cause the “Error reading File”. In addition, there have been instances of specific versions or updates to anti-virus packages causing these errors. Of all issues causing this error, anti-viral scanning is the most likely. There are also other applications and services performing similar functions, such as Disk Optimizers which can also be the cause.
One tipoff that a scanning package is likely at fault is that the BarScan error message will list a file with an “.fxp” extension. For example:
Error reading file c:usersbarscanappdatalocaltempmain.fxp
The file mentioned in this message is actually embedded within the BarScan executable. The scanning (anti-virus) package is interfering with BarScan internal memory management.
A second tipoff that it is your anti-virus package that is the cause is that the error occurs somewhat regularly just after an upgrade to BarScan or the anti-virus software, but was not occurring before one of these events.
When updating anti-virus software scanning:
a. Update Server based anti-virus software, AND
b. Update Workstation based (the local PC) anti-virus software
Background scanning problems can be resolved by updating the antivirus (or background) process on the server (and the workstation if it scanning there as well) so that BarScan data files and/or the BarScan folders and subfolders are listed as exceptions that are NOT to be scanned.
See the BarScan Knowledge Base article for more details:
This does not mean excluding BarScan entirely from scanning, but scanning should be reduced to scheduled rather than dynamic scanning. If the cause is a faulty version of the scanning application or a faulty update, then falling back to the previous version or installing a more recent version may resolve the issue.
4. Enforce a policy of NOT allowing BarScan to sit idle.
BarScan internally makes efforts to keep network connections active, but there are a variety of ways that an idle BarScan application can have its file connections dropped outside of BarScan control. An idle BarScan is more likely to be impacted by one of these issues.
Solutions:
a. Log out of BarScan rather than leaving it open for long periods of time. This is self-explanatory. All users must always log out of BarScan before engaging in other activities.
b. Implement a .bini style startup command to implement an inactivity timeout. BarScan has a startup scripting feature that allows various initialization values and actions to be done as a user starts BarScan. One of these is to set an inactivity timer (in minutes) that will automatically close BarScan if there is no mouse activity on the workstation. See Knowledge Base article:
5. Correct mapped drive connection timeouts.
If your IT department has set up a mapped drive for you to access BarScan, one of the mapped drive settings is how long it keeps the connection live when the connection is idle. Note: The default is normally 10-15 minutes. After the timeout period it will disconnect the network session automatically. BarScan won’t be able to access its own data if the connection has been disconnected. See this Microsoft article for more information on network Mapped Drives using Group Policy.
The following Microsoft article describes two methods to resolve the problem.
The article below describes four approaches to resolve the problem. This is summarized as the Group Policy Method, the Registry Method, the Command Line Method and the Failsafe method.
https://eddiejackson.net/wp/?p=16319
The Eddie Jackson approach is detailed at the end of this Article.
6. Verify SMB1/SMB2 settings.
PROBLEM #1: Some networks may have problems with SMB policy settings that work fine on other networks but cause problems on their own network. One known problem that can cause the “Error reading file” message is digitally signing SMB blocks. This does not happen over all networks, but under some load situations can add overhead to network traffic which may cause the problem. Since signing packets is a security policy, adjusting the digital signing of network packets requires careful IT consideration.
Here is a link that can be helpful in learning more about this issue: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/microsoft-network-client-digitally-sign-communications-always
Note that at one-point Microsoft says “Misuse of these policy settings is a common error that can cause data access failure”.
Here is an image of a typical Windows 10 Local Security Policy screen with the two “Digitally sign communications” entries involved in this issue.
Here is an actual example of someone who had this problem and how they resolved it:
Solution
Disable digitally signing communications. Add the following to your Group Policy:
Client
Windows Settings->Security Settings->Local Policies/Security Options->Microsoft Network Client->Policy:
Microsoft network client: Digitally sign communications (always) – Disabled Microsoft network client: Digitally sign communications (if server agrees) – Disabled
Server
Windows Settings->Security Settings->Local Policies/Security Options->Microsoft Network Server->Policy:
Microsoft network server: Digitally sign communications (always) – Disabled Microsoft network server: Digitally sign communications (if server agrees) – Disabled
PROBLEM #2: A second known cause is incompatible settings, mismatches between various SMB settings between server and workstation, e.g. workstation set for SMB1 and server for SMB2. This latter issue is usually only a problem with older networks and workstations so a solution is not detailed here, other than to make sure you are up to date.
7. Update BarScan workstation level SMB2 cache settings
In addition to all of the other methods of fixing this error, network caching can be adjusted on each workstation by BarScan. Each workstation must be individually adjusted. There were three Client caches introduced with SMB2.
a. Directory caching
b. File Not Found caching
c. FileInfo caching
While BarScan has the built-in ability to turn these caches on and off, this should only be done in coordination with your IT department as it changes the behavior of your workstation on your network. Resetting any of the cache settings will require that you reboot your computer. Changing these three settings turns off Opportunistic Locking from the workstation side of the network. Most literature suggests that turning OpLocks must be done in concert with turning off SMB2 entirely, but essentially the same effect can be achieved with these three settings. For an article about Opportunistic Locking reproduced from outside sources, see the note below.
Special Note: If you suspect a metadata caching problem, disable the three (3) caches only in the order listed above. Analyze the results after each adjustment before proceeding to the next. This will help you to determine which of these caches is affecting the application while minimizing the impact on network communications for you workstation.
To adjust one or more of these settings, do the following:
a. Start BarScan “As an Administrator” (Right click on the application and select “Run as administrator”).
b. Log into BarScan as a BarScan administrator (Master User).
c. Open the Synchronization screen (File-> Open-> Handheld-> Synchronize).
d. Select the “More>>” button.
e. Put a check mark in the “Debug” box.
f. Select the “Windows 10 tests and fixes” button.
A number of tests will be run and their results will be displayed. For more information about this screen in general see the following Knowledgebase article.
Is there a connection test that can be done if handheld not synchronizing
Below is the relevant area in the test:
To turn the specified caching on or off, highlight the desired item and select the “Fix or Run Current Item” button. Before doing this, carefully read all of the Detail information after you have highlighted the item to make sure you will not adversely affect your workstation.
Repeated here are the general explanations of each setting and cautions that should be taken.
Registry setting ‘DirectoryCacheLifetime’. This controls how long your local workstation waits for directory information before it signals a timeout. When throughput to a device (such as a server UNC or mapped drive) is low, the workstation may believe that access to a directory entry has been lost if the device does not respond quickly enough. This can cause the error “Error reading file”. Disabling caching by setting this value to zero (0) may help prevent this error. The default value is 10 seconds.
Registry setting ‘FileNotFoundCacheLifetime’. This is one of the three Client Redirectory caches introduced with SMB2. It controls how long your local workstation waits before it retries opening a file that was not found. When not found, the file is put into this cached list and any attempt to retry opening the file will be refused for the designated timeout period before an actual retry is performed. When throughput to a device (such as a server UNC or mapped drive) is low the workstation may believe that access to a file has been lost if the device does not respond quickly enough. This can cause the error “Error reading file”. Disabling caching by setting this value to zero (0) may help prevent this error. The default value is 5 seconds.
Registry setting ‘FileInfoCacheLifetime’. Turning off this cache is not recommended except under some very specific scenarios as it could nearly double the number of network transactions required. It controls how long your local workstation keeps common file metadata in a cache, information that is commonly repeatedly requested. The down side is that if the information currently existing is not correct (perhaps due to slow network response) it can cause an error. When throughput to a device (such as a server UNC or mapped drive) is low the workstation may believe that access to a file has been lost if the device does not respond quickly enough and untimely information “sticks around” due to the cache. This can cause the error “Error reading file”. Disabling caching by setting this value to zero (0) may help prevent this error. The default value is 10 seconds.
BarScan has the ability to directly turn on and off one or all of these three cache settings. To do so it must be granted “Run as Administrator” privileges and the user must be a BarScan administrator.
Other Causes:
Slow network throughput. This is caused by the simple fact that your network has low throughput by its extent, its nature, or the fact that it is fully shared and densely used. For example, a network that extends between cities or countries with built-in limits on throughput. If you suspect that this may be the cause, use the BarScan throughput test. See the following BarScan Knowledge Base article:
Is there a comprehensive speed test for throughput on my network?
Faulty hardware. Network cards and routers are highly reliable. However, they can eventually fail or degrade. Sometimes a reset will resolve an issue, sometimes replacement is required.
Data throttling. Data throttling is a feature used by many network administrators to make sure that loads are balanced properly and that no one user or group of users or an application gets more than its fair share of the network. However, if this is set too low for a BarScan user or the BarScan application, then it can cause the above errors. This setting can generally be adjusted upwards for greater reliability.
8. Disable DEP (Data Execution Prevention)
DEP (Data Execution Prevention) is a Windows setting that helps protect from security threats. However, like some
settings, it can cause problems under some conditions. There are two available options with Windows:
a. Turn on DEP for essential Windows programs and services only
b. Turn on DEP for all programs and services except those I select
BarScan’ s preferred setting is (a), or (b) with BarScan listed as an exception.
To make a change to this setting, select Control Panel> System> Advanced System Settings. This shows the “System Properties” panel.
Select the “Advanced” tab> Performance button> Data Execution Prevention tab.
The screen will look similar to the image displayed at the right.
Final Thoughts:
There may be other causes and solutions to this error. If you wish to learn more about this particular problem you can perform searches on the specific windows errors mentioned above. Here is a link documenting various causes:
https://social.msdn.microsoft.com/Forums/en-US/a964c493-a407-480f-9e60-877a9dfdec79/1104-error-reading-file-errors-in-network-environment-random?forum=visualfoxprogeneral
SUPPLEMENTAL SECTION # 1 – The eddiejackson.net approaches are repeated here:
Group Policy Method:
a. Open the group policy management console.
b. Select the appropriate existing Group Policy Object (GPO). Right-click and select Edit to open the Group Policy Management Editor.
c. Select Configuration-> Preferences-> Windows Settings-> Drive Maps
d. Change Drive Map Action property for the selected drive from “Create” to “Update”.
Registry Method:
You cannot use this method to turn off the autodisconnect feature of the Server service. You can only use this method to change the default time-out period for the autodisconnect feature.
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanserverparameters
3. In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnectvalue does not exist, follow these steps:
a. On the Edit menu, point to New, and then click REG_DWORD.
b. Type autodisconnect, and then press ENTER.
4. On the Edit menu, click Modify.
5. Click Hexadecimal.
6. In the Value data box, type ffffffff, and then click OK.
The client-side session is automatically disconnected when the idling time lasts more than the duration that is set in KeepConn. Therefore, the session is disconnected according to the shorter set duration value between AutoDisConnect and KeepConn. To change the time-out duration in the client-side during a UNC connection, specify the arbitrary time in KeepConn.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanworkstationparameters
Value: KeepConn
Data type : REG_DWORD
Range : 1 to 65535 (sec)
Default value: 600 sec = 10 mins
Command Line Method:
If you use this method, you may turn off the auto-tuning feature for the Server service. To change the default time-out period for the autodisconnect feature of the Server service, open a command prompt, type the following line, and then press ENTER:
net config server /autodisconnect:number
…where number is the number of minutes that you want the server to wait before it disconnects a mapped network drive. The maximum value for this command is 65,535.
If you set the autodisconnect value to 0 (zero), the autodisconnect feature is not turned off, and the Server service disconnects mapped network drives after only a few seconds of idle time.
To turn off the autodisconnect feature, open a command prompt, type the following line, and then press ENTER:
net config server /autodisconnect:-1
Failsafe Method:
If all else fails, and the drives are still disconnecting, create a Scheduled Task, pointing to a batch script that checks and reconnects the drive. Add the following code into a netmap.cmd file (copy it to system32), create a Schedule Task, and point to the netmap.cmd file.
@echo off
dir X:SomeFile.txt
IF %ERRORLEVEL%==1 GOTO MapDrive
exit /b 0
:MapDrive
net use X: /Delete
net use X: \ShareNameShareFolder /persistent:yes
:: command line testing
:: dir C:testss.cmd && echo do not map || echo map drive
SUPPLEMENTAL SECTION #2 – Opportunistic Locking
ENERCALC_Network_File_Performance_Issues.pdf
In order to preserve this information in case of loss of the data link, the following file is shortened and copied below:
Resolving network file speed & lockup problems
Network / file problems can take many forms but most often it’s a network configuration problem
issue. The biggest potential problem area is Opportunistic Locking (oplocks)
Opportunistic locking (oplocks) and performance
Improperly configured Windows networks can lead to data corruption in any file system database, including the database file system that ENERCALC uses. Two Windows networking behaviors, opportunistic locking (on Windows servers) and read caching (on Windows clients) are sources for speed and corruption issues. Here we discuss these behaviors, their effects and what can be done to minimize the chances of data corruption on Windows networks when running ENERCALC.
What is Opportunistic Locking?
Opportunistic locking (oplocks) is a Windows-specific mechanism for client/server databases to allow multiple processes to lock the same file while allowing for local (client) data caching to improve performance over Windows networks. It is supposed to provide performance benefits when sharing small document files. Unfortunately, the default setting of the oplocks mechanism that enhances the performance of one type of database (client/server) also introduces data integrity issues for other database types (file system/ISAM) which ENERCLAC uses.
Microsoft’s documentation states “An opportunistic lock (also called an oplock) is a lock placed by a client on a file residing on a server. In most cases, a client requests an oplock so it can cache data locally, thus reducing network traffic and improving apparent response time. Oplocks are used by network redirectors on clients with remote servers, as well as by client applications on local servers” and “Oplocks are requests from the client to the server. From the point of view of the client, they are opportunistic. In other words, the server grants such locks whenever other factors make the locks possible”.
What is Read Caching?
Read caching, sometimes referred to as read-ahead caching, is a feature of oplocks. It is a technique used to speed network access to data files. It involves caching data on clients rather than on servers when possible.
The effect of local caching is that it allows multiple write operations on the same region of a file to be combined into one write operation across the network. Local caching reduces network traffic because the data is written once. Such caching improves the apparent response time of applications because the applications do not wait for the data to be sent across the network to the server.
Problems with read caching usually occur if something unforeseen happens, such as a workstation crash, where data is not properly flushed from the workstation, which can lead to data corruption.
Microsoft’s documentation states that ‘Under extreme conditions, some multiuser database applications that use a common data store over a network connection on a file server may experience transactional integrity issues or corruption of the database files and/or indexes stored on the server. This typically applies to some so-called “ISAM style” and “A hazard of local caching is that written data only has as much integrity as the client itself for as long as the data is cached on the client. In general, locally cached data should be flushed to the server as soon as possible.”
What Is SMB2
SMB2 is the second generation of server message block (SMB) communication on Windows networks. SMB2 was introduced in Windows Vista and Windows Server 2008 to enable faster communication between computers that are running Windows Vista and Windows Server 2008. Previous Windows versions used SMB1, also called “traditional” SMB. SMB1 is still supported in current Windows versions (Vista, Server 2008) for backward compatibility.
Recommendations
The ENERCALC project file database is an ISAM database and thus susceptible to the effects of the default Windows oplocks settings. Using the embedded database on Windows networks without disabling oplocks is not recommended or supported and has a high likelihood of data corruption.
Disabling oplocks may have a performance impact on Windows networks.
What Operating Systems are affected?
All computers running Windows operating systems that host or access embedded database tables accessed by other Windows PCs need to have oplocks disabled in order to minimize the chances of database corruption.
Oplocks can be disabled on either (or both) of these:
• the client side (a Windows PC that accesses an embedded database table hosted on another PC)
• the server side (a Windows PC that hosts an embedded database table accessed from another PC)
What Environments Are Not Affected?
There are some environments and scenarios that we support that may not be affected by oplocks, even if using the embedded database:
• Local database access : In general, whenever a project file is accessed on the same PC where that table is located, oplocks do not apply.
• Windows Terminal Services and Citrix : Under normal use for these environments, users log onto a Windows server and run applications locally on that server. If, however, your project file is located on another server than the one running WTS/Citrix, oplocks between the WTS/Citrix server and the database server must be disabled.
Making Windows Registry Changes
The topics below discuss changing editing the Windows Registry.
Caution: The following warning appears in every Microsoft article that discusses editing the Windows
Registry:
WARNING : You can edit the registry by using Registry Editor (Regedit.exe or Regedt32.exe). If you use Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. Microsoft does not guarantee that problems that you cause by using Registry Editor incorrectly can be resolved. Use Registry Editor at your own risk.
If you change any of the Registry values discussed below, you will have to reboot the PC on which the value was changed to ensure that the new setting goes into effect.
The Registry changes are listed in the format MainRegistryKeySubKeySubKey RegistryValue =
RequiredValue
where:
• MainRegistryKey is one of the main Windows Registry keys (e.g. HKey_Local_Machine)
• SubKey is any subkey of a main Registry key
• RegistryValue is a Registry value to change or add in the specified Registry key
• RequiredValue is the value RegistryValue must be set to cause the effect described
If any subkeys or values described do not exist in your Registry, you will have to add them. Please check carefully before doing so.
Disabling Oplocks on Windows Client PCs
To disable oplocks on a Windows client PC (a Windows PC that accesses an embedded database table hosted on another PC), change or add (dword) the following Registry values:
• HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMRXSmbParameters OplocksDisabled = 1
Disabling Oplocks on Windows Servers
To disable oplocks on a Windows server (a Windows PC that hosts an embedded database table accessed from another PC), change or add (dword) the following Registry values:
• HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters EnableOplocks = 0
Disabling Oplocks on SMB2
Oplocks cannot be turned off for SMB2. You can apparently disable SMB2 itself, but how to do so is not documented by Microsoft and was only mentioned in a Microsoft support forum post as a workaround for a bug.
According to that post, SMB2 can be disabled on Windows operating systems that support it.
To disable SMB2 on a Windows Server 2008 or Windows Vista PC hosting embedded database tables, change or add (dword) the following Registry value:
• HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters SMB2 = 0
Once SMB2 is disabled, SMB1 will be used again and the methods described above applied to disable oplocks for SMB1.
Persistent Data Corruption
If you have applied all of the settings discussed in this paper but data corruption problems and other symptoms persist, here is some additional information:
• We have credible reports from developers that faulty network hardware, such as a single faulty network card, can cause symptoms similar to data corruption.
• If you see persistent data corruption even after repeated reindexing, you may have to rebuild the files in question. Send them to ENERCALC for this process.
Resources
• Opportunistic Locks, Microsoft Developer Network (MSDN)
• Microsoft Knowledge Base Article Q296264 Configuring Opportunistic Locking in Windows
• Microsoft Knowledge Base Article Q224992 Maintaining Transactional Integrity with OPLOCKS
• Microsoft Knowledge Base Article Q129202 PC Ext: Explanation of Opportunistic Locking on Windows NT
• Microsoft Knowledge Base Article Windows registry information for advanced users.
Other sources of Network problems
Drivers up to date? Windows networking is subject to a number of problems, MANY of which can be solved simply by installing updated driver software from the manufacturer or (more often) Microsoft.
Is your network slow when using a mapped drive letter?
The reason is this: The computer has both TCP/IP and NetBEUI (network protocols, similar to different spoken languages). TCP/IP for the Internet and NetBEUI for the local network. TCP/IP is the default protocol. When connecting to a mapped drive after some idle time, the computer tries to connect first over TCP/IP and times out. Then and only then it tries the NetBEUI connection. Go to the Control Panel-> Networks-> Bindings. Make NetBEUI as the default protocol.
Is your network slow when using a mapped drive letter? (part 2)
Is the drive mapped to the main computer’s drive or to a folder? If it is mapped to a folder, you will likely see a decrease in performance, often a quite noticeable decrease. We are not sure why this happens, but mapping directly to the drive has been proven time and time again to be faster. We have not discovered the reason for this, despite extended searches of Microsoft’s tech database ( http://msdn.microsoft.com ).
Is your network slow?
Recently, we have noticed that the “Windows Indexing Service” has a seriously negative effect on network performance. Turn it off. The indexing service scans your hard disk and indexes the files so that the next time you do a file search, Windows can find the files more quickly. Turn it off. Think about how often you do searches vs. how much time you waste waiting on your network. Do a search and do other work while waiting for it. It’s just not worth waiting 99% of the time to speed up 1% of your work.
Do some or all computers on your network randomly “die”, “go to sleep” or “hang”?
Usually, this is caused by power management being active on the workstation and possibly the server. Power management is a computer geek word for “Windows has settings that turns stuff off when it hasn’t been used in a while”. Power management is a bad thing on a network. Bottom line issue: You don’t want network cards turning off because you haven’t moved your mouse for 20 minutes. You don’t want your server’s hard drive turning off because no one has touched the server keyboard in the last 30 minutes (this might make your workstations just a little bit cranky when they are trying to read stuff on that server’s drive). This is exactly what Power Management is supposed to do, but you don’t want this to happen when using a networked database. To investigate, go to Start, settings, control panel or Start, Control Panel and double click the Network Connections icon (if that doesn’t exist on your computer, you need to find the place where you can change settings on your network cards). Find your network
adapter on this screen. Usually it will say something like “Local Area Connection” or “Wireless Connection 1” (if you are ignoring our advice and using wireless). Right click that icon, click properties. When the screen opens, you’ll see the name of the network card up near the top, just below the tabs. To the right of that, there is a Configure button. Click it. When the next screen opens, there will almost certainly be a Power Management tab. On that tab, chances
are you will see a checkbox that says something like “Allow the computer to turn off this device to save power”. Uncheck the box and click OK until you don’t have to look at all these network settings anymore. Reboot your PC, hope for the best.
Performance issues are often caused by network protocol “bindings”
Check the following Network protocols basics:
• Make sure that your default network protocol has no bindings to a virtual device (dialup…..).
• If you are using TCP/IP and you have dialup on this workstation, try NetBEUI.
• Try to avoid using IPX and NetBEUI together. IPX gets confused when you have a “chatty” NetBEUI. Removing IPX (if you can) is strongly advised.
END OF THIS KNOWLEDGE BASE