Errors using HP's OpenView to copy files to the network.
(Last modified: 29Jan2002)
This document (10026135) is provided subject to the disclaimer at the end of this document.
fact
HP OpenView (3rd Party Management Product)
Novell Client 4.6 SP2 for Windows NT
Formerly TID 2951466.
symptom
Errors using HP's OpenView to copy files to the network.
Error occurs randomly. Sometimes for the error to occur, only a file copy to 7 servers is needed, sometimes p to 12 may be needed.
Error occur durring file copy after upgrading 4.6 client from 4.11b client
Occurs when copying files to a large number of servers.
fix
The following is from the Microsoft database. Before using this information, check the Microsoft knowledge base for updated information.
DISCLAIMER
The Origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
CSNW Error 85, Local Device Already in Use
The information in this article applies to:
Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server version 4.0, Terminal Server Edition
SYMPTOMS
In the following configuration, after you log on and log off several consecutive times, the network client receives an access denied error message to one or more network drives located on the NetWare server. Also, the NET USE command fails with the following error message:
Error 85, Local device already in use
This error message is followed by an access denied error message.
The problem can be cleared on the Windows NT Workstation client by restarting Client Services for NetWare (CSNW).
Configuration:
Windows NT primary domain controller (PDC) running Windows NT Server 4.0 with Gateway Services for
NetWare (GSNW)
Novell NetWare 3.12 server
Client running Windows NT Workstation 4.0 with Client Services for NetWare CSNW and:
- Logon script located on the PDC
- Desktop icons stored on the NetWare server (M: drive below)
The Windows NT logon script maps several network drives on the NetWare server. For example:
net use M: /delete > NUL followed by,
net use M: \\NWserver\share > NUL
NOTE: The same behavior is obtained using a NET USE command with the /persistent:no switch.
CAUSE
The problem affects one or more drives and the drive where the desktop icons are located is always affected. The problem is intermittent and is easier to reproduce when using higher speed processors (200 MHz and more).
RESOLUTION
The solution consists of removing a race condition that potentially exists, especially when using high speed processors, between process cleanup and WINLOGON deleting network connections.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:
Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Additional query words: 4.00 error85
Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4
Version : WinNT:4.0
Platform : winnt
Hardware : ALPHA x86
Issue type : kbbug
Solution Type : kbfix
Novell Client 32 Requestor Cannot Connect to FPNW
The information in this article applies to:
Microsoft Windows NT Workstation versions 3.51, 4.0
Microsoft Windows NT Server versions 3.51, 4.0
Microsoft File and Print Services for NetWare version 3.51
Microsoft Services for NetWare version 4.0
Microsoft Windows 95
SYMPTOMS
NOTE: Information in this article applies to Novell's Client 32 Requestor version 2.11.
When you try to connect to a FPNW server volume from a computer running Windows NT version 3.51, Microsoft Windows NT version 4.0, or Microsoft Windows 95 with Novell's Client 32 Requestor for NetWare loaded, you cannot connect or the following message appears:
A device attached to the system is not functioning.
NOTE: This error will also occur with OS/2 Warp clients.
CAUSE
Case 87 (decimal) NetWare Core Protocol (NCP) packets are normally used to communicate with NetWare 3.x servers. Case 22 (decimal) NCPs are normally used to communicate with NetWare 2.x servers. Novell's Client 32 Requestor for Windows 95 makes use of Case 87 NCP packets with NetWare 3.x servers, and Case 22 NCP packets with NetWare 2.x servers. Novell's Client 32 Requestor for Windows NT uses only case 87 NCPs and cannot communicate with NetWare 2.x servers. Either client software version detects FPNW as a NetWare 3.x server and attempts to converse with it using Case 87 NCPs. FPNW 3.51 and 4.0 (without Windows NT 4.0 Service Pack 2) recognize the Case 87 NCPs required to support Novell's VLM, Microsoft's CSNW/GSNW, and Novell's OS/2 Requestor. However, the case 87 support in FPNW 3.51 and 4.0 (without Service Pack 2) is not complete enough to support Novell's Client 32 Requestor, which was released after either version of FPNW shipped. This incomplete support for all case 87 NCPs causes the earlier error.
RESOLUTION
Windows NT Server Version 4.0 Running FPNW
Apply the latest Windows NT 4.0 service pack to resolve this issue. The latest Windows NT 4.0 service pack contains FPNW enhancements to allow FPNW to communicate using Case 87 NCPs.
If LIP and burst mode were disabled before you installed the service pack, it is strongly recommended that you enable them.
Perform the following steps to enable LIP and burst mode:
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at you own risk.
1. Use the Services utility in Control Panel to stop the FPNW service or type the following command at a command prompt:
NET STOP FPNW
2. Start Registry Editor (Regedt32.exe).
3. From the HKEY_LOCAL_MACHINE Window, go to the following key:
System\CurrentControlSet\Services\FPNW\Parameters
4. Set the EnableBurst value to 1. This is the default value.
5. Set the EnableLip value to 1. This is the default value.
6. If present, set the EnableOS2NameSpace value to 1. If the value is not present, it defaults to 1.
7. Quit Registry Editor.
8. Shut down and restart the server.
Windows NT Server Version 3.51 Running FPNW
There is no resolution but there is a workaround to the problem when Windows NT Server version 3.51 and FPNW are involved. This section explains the workaround so that a computer running Novell's Client 32 Requestor on Windows 95 can function when communicating with a Windows NT Server version 3.51 computer running FPNW 3.51.
NOTE: This work around only allows Windows 95 workstation computers with Novell's 32-bit NetWare client installed to communicate properly with a Windows NT Server 3.51 computer running FPNW 3.51. Using Novell's 32-bit NetWare client on Windows NT to communicate with an FPNW 3.51 server is not supported.
Apply the latest Windows NT 3.51 service pack to the Windows NT Server version 3.51 computer with FPNW installed. Applying the service pack installs an updated version of Fpnwsrv.sys that permits the registry changes discussed later.
Configuring File and Print Services for NetWare version 3.51 to respond as a NetWare version 2.2 file server allows Novell's Client 32 Requestor to function correctly. Perform the following steps to configure File and Print Services for NetWare in this manner:
NOTE: Making these changes will disable long filename support (OS/2 name space) from clients, as well as support for burst mode and LIP communication.
WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.
1. Use the Services utility in Control Panel to stop the FPNW service or type the following command at a command prompt:
NET STOP FPNW
2. Start Registry Editor (Regedt32.exe).
3. From the HKEY_LOCAL_MACHINE window, go to the following key:
\System\CurrentControlSet\Services\FPNW\Parameters
4. Click Add Value from the Edit menu.
5. Add the following:
Value Name: EnableOS2NameSpace
Data Type: REG_DWORD
Data: 0
6. Change EnableBurst value from 1 (default) to 0.
7. Change EnableLip value from 1 (default) to 0.
8. Shut down and restart the server.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows NT versions 3.51 and 4.0. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 4.0. 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
Additional query words: client32 ntfaqmax
Keywords : kb3rdparty kbnetwork kbbug4.00 ntprotocol kbbug3.51 NTSrvWkst
Version : WinNT:3.5,4.0;Windows:95
Platform : winnt
Issue type : kbbug kbhowto
Last Reviewed: February 17, 1999.
document
| Document Title: | Errors using HP's OpenView to copy files to the network. |
| Document ID: | 10026135 |
| Solution ID: | 1.0.53768328.2525183 |
| Creation Date: | 03Feb2000 |
| Modified Date: | 29Jan2002 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.