Compaq PATHWORKS for OpenVMS (Advanced Server)
Server Administrator's Guide

6.2.2.3.1 Monitoring Data Cache Use by the File Server

Advanced Server uses its data cache for caching the security databases, in addition to client file data. To ensure a balance of cache usage, the file server periodically monitors its use of the data cache, as follows:

Total security databases utilization
The file server monitors the total utilization of the data cache by the security databases. If the file server detects that the utilization of the data cache for these files exceeds thirty-five percent (35%), a warning message is posted to the file server log file indicating that the current cache configuration may not be adequate for the current load imposed on the file server.
For example:
BlobCache Warning: Sum of Blob file control areas is 950272 bytes (45% of data cache).
The condition reported by this warning message will not prevent the file server from being able to properly process requests associated with the security databases. The message (shown below) indicates that you should increase the size of the data cache.

Individual security database utilization
The file server monitors utilization of the data cache by individual security database files. When the database expands in size, more cache resources are required to continue operating. If the file server detects that an operation will cause a database file expansion, and that expanding the database file will cause it to utilize more than fifty percent (50%) of the data cache, error messages are recorded in the file server log, as in the following example:

BlobCache Error: The largest single Blob file control area is 1187840 bytes (57% of data cache). BlobCache Error: The largest single Blob file control area is PWRK$LMROOT:[LANMAN.DOMAINS]DOMAIN1.

In addition to recording the problem in the file server log, the software generates an operator message and raises a server alert.
These messages indicate that the operation will prevent the file server from completing the current and future operations. In this case, you should use the Configuration Manager (ADMIN/CONFIG), as described in Section 7.2, Using the Configuration Manager, to increase the size of the data cache so that utilization of the data cache by a single database file remains under 50%. The change to the data cache size takes effect the next time you start the server.

You can use the ADMIN/ANALYZE command to monitor these warning messages and error messages, as described in Section 6.1.4.2, The Advanced Server Common Event Log.

6.2.2.4 Problems with Services

Advanced Server software includes several optional services. For example, Auditing is a service useful for analyzing server problems. However, the services must be enabled.

Table 6-10, Procedure for Solving Service Problems, describes how to determine the cause of a network service problem and what do to about it.

Table 6-10 Procedure for Solving Service Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 Check whether the services are running. Use the SHOW SERVICES command to display the services that are running. Use the following commands to control the operation of the services:

START SERVICE

STOP SERVICE

PAUSE SERVICE

CONTINUE SERVICE

(See Section 2.3.4, Managing Services, for more information.)

6.2.2.5 Client Connection Problems

Clients may be individually or collectively reporting a failure to connect to the server or reporting slow response time in connecting to the server or the share.

Table 6-11, Procedure for Solving Client Connection Problems, describes how to determine the causes behind many typical client connection problems and what to do about them. For information about problems connecting to shares or specific files, see Section 6.2.2.6, Share Access Problems.

Table 6-11 Procedure for Solving Client Connection Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 If a client cannot end a session or there are too many sessions, you can control the user sessions. Use the SHOW SESSIONS command to display current Advanced Server client sessions. Use the CLOSE SESSION command to close unneeded sessions.

2 If more than one client reports a problem when connection to the server is lost or with slow response time, the problem may be caused by too many connections to the same server. Use the SHOW
CONNECTIONS command to display the connections that clients have established to Advanced Server shares. Use the CLOSE CONNECTION command to end one or more connections.

3 When a client tries to log on over a WAN, the following message is received: "You were logged on, but have not been validated by a server." Clients may use NetBIOS broadcasts to send logon requests, and these requests do not go over the router. To locate domain controllers capable of authenticating logons, use a WINS Server or LMHOSTS entries that include the #DOM directive.

**Table 6-11 Procedure for Solving Client Connection Problems**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	If a client cannot end a session or there are too many sessions, you can control the user sessions.	Use the SHOW SESSIONS command to display current Advanced Server client sessions.	Use the CLOSE SESSION command to close unneeded sessions.
2	If more than one client reports a problem when connection to the server is lost or with slow response time, the problem may be caused by too many connections to the same server.	Use the SHOW CONNECTIONS command to display the connections that clients have established to Advanced Server shares.	Use the CLOSE CONNECTION command to end one or more connections.
3	When a client tries to log on over a WAN, the following message is received: "You were logged on, but have not been validated by a server."	Clients may use NetBIOS broadcasts to send logon requests, and these requests do not go over the router.	To locate domain controllers capable of authenticating logons, use a WINS Server or LMHOSTS entries that include the #DOM directive.

6.2.2.6 Share Access Problems

Clients may fail to connect to shares or lose existing connections. The shares must be set to permit client access. Share setup includes:

Allowing access to users who are members of user groups that have access to the share
Setting permissions to allow access to the share such as read access
Setting OpenVMS file and directory protections, if the Advanced Server and OpenVMS security model is in use
Setting the maximum connection limit to allow the required connects

Table 6-12, Procedure for Solving Share Access Problems, describes how to determine the causes behind some typical share access problems and what to do about them.

Table 6-12 Procedure for Solving Share Access Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 Determine whether the client is connected but failing to access resources in the shares. For example, the client computer displays the connection to the server but is unable to list all the files and directories to which the client requires access. Use the SHOW USER command to display the groups to which the user belongs.
Use the SHOW SHARE command to display the groups allowed to access the share.
To add the user to a group, use the MODIFY GROUP command to add the user name. To let the user's group access a share, use the MODIFY SHARE/PERMISSIONS command, as described in Section 4.3.4, Changing Share Properties.

Use the SHOW FILE command to display access permissions on the resources. If the OpenVMS and Advanced Server security model is enabled, use the OpenVMS command DIRECTORY/SECURITY to display the OpenVMS owner and protection information. Use the server SET FILE/PERMISSIONS command, as described in Section 4.3.5.2, Setting Permissions on a File or Directory, to modify the permissions on the file to give the user or group access to the specific resource. Use the OpenVMS SET FILE/PROTECTION command to modify the RMS protections on a directory or file.

Use the Advanced Server SHOW HOSTMAP command to display host mapped user accounts. Use the ADD HOSTMAP command, as described in Section 3.1.16.2, Establishing User Account Host Mapping, to associate a network user account with an OpenVMS user account.

2 If some clients report problems connecting to a share, the problem may be caused by too many connections. Use the SHOW SHARES command to display information about the connection limit on the share. Use the MODIFY SHARE command to change the connection limit on the share, as described in Section 4.3.4, Changing Share Properties.

3 If clients report failure to access a specific file, the problem may be caused by incorrect permission settings on the file. Use the SHOW FILE command to display files that are open, clients who have the files open, and the permissions granted to the clients. Use the SET FILE
/PERMISSIONS command, as described in Section 4.3.6, Specifying File and Directory Access Permissions, to set the file permissions correctly.

**Table 6-12 Procedure for Solving Share Access Problems**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	Determine whether the client is connected but failing to access resources in the shares. For example, the client computer displays the connection to the server but is unable to list all the files and directories to which the client requires access.	Use the SHOW USER command to display the groups to which the user belongs. Use the SHOW SHARE command to display the groups allowed to access the share.	To add the user to a group, use the MODIFY GROUP command to add the user name. To let the user's group access a share, use the MODIFY SHARE/PERMISSIONS command, as described in Section 4.3.4, Changing Share Properties.
		Use the SHOW FILE command to display access permissions on the resources. If the OpenVMS and Advanced Server security model is enabled, use the OpenVMS command DIRECTORY/SECURITY to display the OpenVMS owner and protection information.	Use the server SET FILE/PERMISSIONS command, as described in Section 4.3.5.2, Setting Permissions on a File or Directory, to modify the permissions on the file to give the user or group access to the specific resource. Use the OpenVMS SET FILE/PROTECTION command to modify the RMS protections on a directory or file.
		Use the Advanced Server SHOW HOSTMAP command to display host mapped user accounts.	Use the ADD HOSTMAP command, as described in Section 3.1.16.2, Establishing User Account Host Mapping, to associate a network user account with an OpenVMS user account.
2	If some clients report problems connecting to a share, the problem may be caused by too many connections.	Use the SHOW SHARES command to display information about the connection limit on the share.	Use the MODIFY SHARE command to change the connection limit on the share, as described in Section 4.3.4, Changing Share Properties.
3	If clients report failure to access a specific file, the problem may be caused by incorrect permission settings on the file.	Use the SHOW FILE command to display files that are open, clients who have the files open, and the permissions granted to the clients.	Use the SET FILE /PERMISSIONS command, as described in Section 4.3.6, Specifying File and Directory Access Permissions, to set the file permissions correctly.

6.2.2.7 Printer Problems

Problems with the print software can occur after changes in hardware configuration or print queues. The Advanced Server provides commands to modify and remove print jobs and print queues.

Table 6-13, Procedure for Solving Printing Problems, describes how to determine the causes behind some typical printing problems and what to do about them.

Table 6-13 Procedure for Solving Printing Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 Obtain the physical printer name, the print queue name, the print share name, and the specific print command used to submit the print job. Use the SHOW PRINT JOBS command to display information about print jobs.
Set the audit policy to record printer-related events by using the following command: ADMINISTER SET AUDIT POLICY/SUCCESS=ACCESS.
Use the SET PRINT JOB command to change the status of a print job or delete a print job, as described in Section 5.3.2.12, Managing Print Jobs.

2 During printer maintenance and when printers are off line, you may need to prevent users from submitting print jobs. Use the SHOW PRINT QUEUE command to display information about the print queue, the print jobs in the print queue, and the status of the print queue. Use the following commands to control the print queue while you correct the problem:

PAUSE PRINT QUEUE
CONTINUE PRINT QUEUE
REMOVE PRINT QUEUE

See Section 5.3.2, Managing Printers Using the Advanced Server ADMINISTER Command-Line Interface, for more information.

2 Windows NT, Windows 95, Windows 98, or Windows 2000 client cannot print to a shared print queue. Use the ADMINISTER SHOW SHARES/TYPE=PRINT command to view the shared print queues. The share name and the queue name must differ for printing from these Windows clients.

**Table 6-13 Procedure for Solving Printing Problems**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	Obtain the physical printer name, the print queue name, the print share name, and the specific print command used to submit the print job.	Use the SHOW PRINT JOBS command to display information about print jobs. Set the audit policy to record printer-related events by using the following command: ADMINISTER SET AUDIT POLICY/SUCCESS=ACCESS.	Use the SET PRINT JOB command to change the status of a print job or delete a print job, as described in Section 5.3.2.12, Managing Print Jobs.
2	During printer maintenance and when printers are off line, you may need to prevent users from submitting print jobs.	Use the SHOW PRINT QUEUE command to display information about the print queue, the print jobs in the print queue, and the status of the print queue.	Use the following commands to control the print queue while you correct the problem: PAUSE PRINT QUEUE CONTINUE PRINT QUEUE REMOVE PRINT QUEUE See Section 5.3.2, Managing Printers Using the Advanced Server ADMINISTER Command-Line Interface, for more information.
2	Windows NT, Windows 95, Windows 98, or Windows 2000 client cannot print to a shared print queue.	Use the ADMINISTER SHOW SHARES/TYPE=PRINT command to view the shared print queues.	The share name and the queue name must differ for printing from these Windows clients.

6.2.2.8 User Account Problems

When one user reports a problem connecting to the server or a share, establish whether the problem is caused by the Advanced Server user account definition. You can help users with password problems immediately, by changing their passwords.

Table 6-14, Procedure for Solving User Account Problems, describes how to determine the causes of typical problems in user account definition and what do to about them.

If a client reports a failure to log on to the network, use the procedure described in this table.

Table 6-14 Procedure for Solving User Account Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 Determine whether the user account is set up properly. Use the SHOW USER command to display user account information. Look for logon restrictions, such as logon hours, which might give the client access only during specific hours of the day and days of the week. Check also whether the account has expired or is locked out. Use the MODIFY USER command to change user account information like restricted hours, or to unlock the user account, as described in Section 3.1.3, User Account Attributes.

2 Determine whether the user is entering the correct password. Use the SET PASSWORD command to change a user account password, as described in Section 3.1.5, Specifying Passwords.

**Table 6-14 Procedure for Solving User Account Problems**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	Determine whether the user account is set up properly.	Use the SHOW USER command to display user account information. Look for logon restrictions, such as logon hours, which might give the client access only during specific hours of the day and days of the week. Check also whether the account has expired or is locked out.	Use the MODIFY USER command to change user account information like restricted hours, or to unlock the user account, as described in Section 3.1.3, User Account Attributes.
2	Determine whether the user is entering the correct password.		Use the SET PASSWORD command to change a user account password, as described in Section 3.1.5, Specifying Passwords.

6.2.2.9 Privileged User Problems

Users with responsibility for privileged operations, such as administrators, printer operators, and server operators, may receive error messages when attempting to use privileged commands and procedures. Make sure the user is a member of the appropriate group.

If users are unable to perform privileged operations, use the procedure described in Table 6-15, Procedure for Solving Problems of Privileged Users, to determine the cause of the problem and what to do about it.

Table 6-15 Procedure for Solving Problems of Privileged Users
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 Determine whether users are unable to perform administrative operations on a file, such as deleting the file, modifying file protections, and displaying directory information about the file. Check the user accounts and predefined groups for operators and administrators. If an Advanced Server user does not have the required user rights, use the MODIFY USER/ADD_TO_GROUP command to add the user to the appropriate groups, as described in Section 3.1.14, Modifying User Accounts.

2 Determine whether users are unable to perform administrative operations on a file, such as deleting the file, modifying file protections, and displaying directory information about the file. Use the SHOW FILES command to display the permissions set on the file. Use this information to notify users of changes you plan to make to the file. Use the TAKE FILE
OWNERSHIP or SET FILE
/PERMISSIONS command to obtain the desired control over a file and set permissions appropriately, as described in Section 4.3.10, Taking Ownership of Files or Directories, and Section 4.3.6, Specifying File and Directory Access Permissions.

**Table 6-15 Procedure for Solving Problems of Privileged Users**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	Determine whether users are unable to perform administrative operations on a file, such as deleting the file, modifying file protections, and displaying directory information about the file.	Check the user accounts and predefined groups for operators and administrators.	If an Advanced Server user does not have the required user rights, use the MODIFY USER/ADD_TO_GROUP command to add the user to the appropriate groups, as described in Section 3.1.14, Modifying User Accounts.
2	Determine whether users are unable to perform administrative operations on a file, such as deleting the file, modifying file protections, and displaying directory information about the file.	Use the SHOW FILES command to display the permissions set on the file. Use this information to notify users of changes you plan to make to the file.	Use the TAKE FILE OWNERSHIP or SET FILE /PERMISSIONS command to obtain the desired control over a file and set permissions appropriately, as described in Section 4.3.10, Taking Ownership of Files or Directories, and Section 4.3.6, Specifying File and Directory Access Permissions.

6.2.2.10 Problems Connecting to the Advanced Server

Clients and servers in the network that communicate with the Advanced Server to perform various tasks might receive error messages when attempting to locate the Advanced Server. Table 6-16, Procedure for Solving Problems Connecting to the Advanced Server, describes how to determine the cause of host-to-host communication problems and what do about it.

Table 6-16 Procedure for Solving Problems Connecting to the Advanced Server
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 The client computer receives the following error when attempting to map a network drive:
"Network path not found"
Can the client communicate with any other system on the network? Use PING or NCP LOOP commands against other systems on the same physical segment. Check the physical cabling and network adapter of the client for loose connections.

Can the client communicate with the target server at the transport level? For example, can the client PING or TELNET to the server using the server's IP address? If a Wide Area Network path is used, verify communication along each segment of the network using a utility such as Tracert. Check the transport configuration such as IP address, subnet mask, broadcast address, and default gateway/routes of systems involved.

Can the source system resolve the NetBIOS name(s) of the target system, and can the target server resolve the NetBIOS name(s) of the source system? You can use tools such as NBTSTAT.EXE on Windows systems and NBSHOW ¹ KNBSTATUS on Advanced Server and PATHWORKS systems to perform limited NetBIOS name resolution testing. In addition, you can use Windows NT Resource Kit utilities such as DOMMON, NLTEST, and BROWSTAT to test connectivity. Ensure NetBIOS name registration is occurring on the correct WINS Server or that appropriate NetBIOS names are represented in LMHOSTS files.

Is the problem license related? See Section 6.2.2.11, License Acquisition and Validation Problems.

Is the Advanced Server file server process running? Use the PWSHOW command and verify that the PWRK$LMSRV process is present. If the PWRK$LMSRV process is not running, restart the Advanced Server with the command PWRESTART.

2 The client computer receives the error "Network name not found." This error usually indicates that the share name cannot be found or the share path is not available. Use the ADMINISTER SHOW SHARE/PATH command to verify that the share exists and the share path is correct. Verify that the share path is available (that is, that the device reference is valid). Use the ADMINISTER/ANALYZE command to check for device and autoshare related errors. If the share path is incorrect, the share must be removed and added again using the correct path.
If the device is not mounted, mount it.
For autoshare errors, change the volume label to 11 characters or less or establish a different autoshare name for the device as described in Section 4.2.3.2, Defining Autoshares.
If the device was mounted after the Advanced Server started, use the following ADMINISTER command to make it accessible to the Advanced Server:
SET COMPUTER/
AUTOSHARE_SYNCHRONIZE.

**Table 6-16 Procedure for Solving Problems Connecting to the Advanced Server**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	The client computer receives the following error when attempting to map a network drive: "Network path not found"	Can the client communicate with any other system on the network? Use PING or NCP LOOP commands against other systems on the same physical segment.	Check the physical cabling and network adapter of the client for loose connections.
		Can the client communicate with the target server at the transport level? For example, can the client PING or TELNET to the server using the server's IP address? If a Wide Area Network path is used, verify communication along each segment of the network using a utility such as Tracert.	Check the transport configuration such as IP address, subnet mask, broadcast address, and default gateway/routes of systems involved.
		Can the source system resolve the NetBIOS name(s) of the target system, and can the target server resolve the NetBIOS name(s) of the source system? You can use tools such as NBTSTAT.EXE on Windows systems and NBSHOW ¹ KNBSTATUS on Advanced Server and PATHWORKS systems to perform limited NetBIOS name resolution testing. In addition, you can use Windows NT Resource Kit utilities such as DOMMON, NLTEST, and BROWSTAT to test connectivity.	Ensure NetBIOS name registration is occurring on the correct WINS Server or that appropriate NetBIOS names are represented in LMHOSTS files.
		Is the problem license related?	See Section 6.2.2.11, License Acquisition and Validation Problems.
		Is the Advanced Server file server process running? Use the PWSHOW command and verify that the PWRK$LMSRV process is present.	If the PWRK$LMSRV process is not running, restart the Advanced Server with the command PWRESTART.
2	The client computer receives the error "Network name not found."	This error usually indicates that the share name cannot be found or the share path is not available. Use the ADMINISTER SHOW SHARE/PATH command to verify that the share exists and the share path is correct. Verify that the share path is available (that is, that the device reference is valid). Use the ADMINISTER/ANALYZE command to check for device and autoshare related errors.	If the share path is incorrect, the share must be removed and added again using the correct path. If the device is not mounted, mount it. For autoshare errors, change the volume label to 11 characters or less or establish a different autoshare name for the device as described in Section 4.2.3.2, Defining Autoshares. If the device was mounted after the Advanced Server started, use the following ADMINISTER command to make it accessible to the Advanced Server: SET COMPUTER/ AUTOSHARE_SYNCHRONIZE.

¹The NBSHOW command and other Advanced Server management commands are defined in the SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM command file; for more information, refer to the Compaq PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide.

6.2.2.11 License Acquisition and Validation Problems

For a client to use the services of a PATHWORKS V6.1 for OpenVMS (Advanced Server) server, the minimum license required is the Client Access license PWLMXXXCA07.03, or an equivalent client virtual license. A client can acquire either one of the following:

Client-based license from a License Server
Server-based license from the Advanced Server system to which the client connects

A client-based license is acquired once, and thereafter it is verified during client startup. The License Server is responsible for assigning and verifying client-based licenses. Once acquired, the client-based license is presented for validation when establishing a session to any PATHWORKS server. The License Registrar on each PATHWORKS server is responsible for validating client-based licenses or assigning a server-based license, if available, when clients establish a session.

A server-based license is assigned to a client only for the duration of the client's session with the server.

Note that client-based licensing involves two distinct operations:

Obtaining (or verifying, once initially acquired) the appropriate license from a License Server during startup
Validating the appropriate license when establishing a session to an Advanced Server.

Clients using client-based licensing may report license acquisition (or verification) problems during startup. These problems typically result in a "LICnnnn error" being displayed on the client. Refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses for more information about these messages.

All clients, whether using client-based licensing or not, may also report problems connecting to a server that could be the result of a license validation issue. Table 6-17, Procedure for Solving License Validation Problems describes how to determine the cause of license validation problems and what to do about it.

Table 6-17 Procedure for Solving License Validation Problems
Step Stage 1: Collect Information Stage 2: Analyze the Problem Stage 3: Solve the Problem

1 When mapping a network drive, the Windows NT or Windows 2000 client sees:

The error message: "A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached."
If the Alerter service is running on the server, a Messenger pop-up window indicating that the connection attempt was denied because the server failed to authenticate a license for the client.
If a license problem is preventing a client from connecting to a server, a warning message is written to the Advanced Server common event log ($ ADMIN/ANALYZE) indicating "No server license for client - access denied," along with the name of the client. Add server-based licenses to the server, or check the License Server to ensure adequate client-based licenses are available to clients. For more information, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.

Also check for applicable messages in the License Registrar log file on the server (PWRK$LICENSE_REGISTRAR_ nodename.LOG). Extend the logging performed by the License Registrar process, and then recheck the PWRK$LICENSE_REGISTRAR_ nodneame.LOG file for errors. For details on logging capabilities, see the comments in the License Registrar process startup file, SYS$STARTUP:PWRK$
LICENSE_R_START.COM.

2 When mapping a network drive, the Windows 95 or Windows 98 client sees the following error message: "The local device type and the network resource type are not the same." See analysis instructions above. See problem-solving instructions above.

**Table 6-17 Procedure for Solving License Validation Problems**
Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	When mapping a network drive, the Windows NT or Windows 2000 client sees: The error message: "A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached." If the Alerter service is running on the server, a Messenger pop-up window indicating that the connection attempt was denied because the server failed to authenticate a license for the client.	If a license problem is preventing a client from connecting to a server, a warning message is written to the Advanced Server common event log ($ ADMIN/ANALYZE) indicating "No server license for client - access denied," along with the name of the client.	Add server-based licenses to the server, or check the License Server to ensure adequate client-based licenses are available to clients. For more information, refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.
		Also check for applicable messages in the License Registrar log file on the server (PWRK$LICENSE_REGISTRAR_ nodename.LOG).	Extend the logging performed by the License Registrar process, and then recheck the PWRK$LICENSE_REGISTRAR_ nodneame.LOG file for errors. For details on logging capabilities, see the comments in the License Registrar process startup file, SYS$STARTUP:PWRK$ LICENSE_R_START.COM.
2	When mapping a network drive, the Windows 95 or Windows 98 client sees the following error message: "The local device type and the network resource type are not the same."	See analysis instructions above.	See problem-solving instructions above.

Contents

Index

Step	Stage 1: Collect Information	Stage 2: Analyze the Problem	Stage 3: Solve the Problem
1	Check whether the services are running.	Use the SHOW SERVICES command to display the services that are running.	Use the following commands to control the operation of the services:
			START SERVICE
			STOP SERVICE
			PAUSE SERVICE
			CONTINUE SERVICE
			(See Section 2.3.4, Managing Services, for more information.)

Compaq PATHWORKS for OpenVMS (Advanced Server)Server Administrator's Guide

6.2.2.3.1 Monitoring Data Cache Use by the File Server

Compaq PATHWORKS for OpenVMS (Advanced Server)
Server Administrator's Guide