ACC: Disk or Network Error with Windows 95 Client on NT Server (165351)


The information in this article applies to:

  • Microsoft Access 2.0
  • Microsoft Access for Windows 95 7.0
  • Microsoft Access 97
This article was previously published under Q165351
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.

Advanced: Requires expert coding, interoperability, and multiuser skills.

SYMPTOMS

When you run Microsoft Access on a Microsoft Windows 95 client computer, and you link a Microsoft Access database on a Microsoft Windows NT network server, you receive random occurrences of "Disk or Network Error."

CAUSE

This error can occur as a result of many different situations, such as faulty network cabling, noise or traffic in network lines, and problems with network interface cards. However, in many situations Microsoft has confirmed that using the IPX/SPX protocol as the primary network protocol to communicate with a Windows NT 3.51 server may cause the problem. This situation occurs when a Windows 95 client computer, using direct hosting with IPX/SPX protocol, writes to a file on a Windows NT Server.

RESOLUTION

In addition to troubleshooting your network connections and network hardware, you may be able to resolve the problem by disabling direct hosting, upgrading to Microsoft Windows NT version 3.51 Service Pack 5, or by implementing TCP/IP as the primary protocol.

Disabling Direct Hosting

The first method involves disabling the direct hosting feature for the IPX/SPX protocol on both the client and server computers. The following steps outline how to do this.

Disable Direct Hosting on the Windows 95 Client Computer:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

NOTE: For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.

To disable direct hosting in Windows 95, add a new string value named DirectHost to the following registry key: 
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Vxd\VNETSUP

Set the value for the DirectHost string value to 0.

Disable Direct Hosting on the Windows NT 3.51 server:
  1. Open Control Panel and double-click the Network icon.
  2. Click Bindings.
  3. Select Server->Nwlink Ipx/Spx Compatible, and click Disable.
  4. Click OK.

Upgrading to NT 3.51 Service Pack 5

The upgrade to Microsoft Windows NT version 3.51 Service Pack 5 contains a fix that may resolve the networking problem with a Windows 95 client computer.

For information about obtaining Service Pack 5, please see the following article in the Microsoft Knowledge Base:

128465 How to Obtain Windows NT Version 3.51 U.S. Service Pack 5

Implementing TCP/IP Protocol

Another possible solution is to disable IPX/SPX on both the client and server computers and implement TCP/IP as the primary protocol.

REFERENCES

For more information about using direct hosting in Microsoft Windows NT 3.51, please see the following articles in the Microsoft Knowledge Base:

151744 Network Client 3.0 with IPX Needs Direct Hosting on Server

147246 Using Direct hosting over IPX Causes STOP Ox0000000A

Modification Type:MajorLast Reviewed:5/9/2003
Keywords:kbprb KB165351
©2002 Microsoft Corporation. All rights reserved.