The following table describes various problems you might experience with Network Services software and suggests possible corrective actions.
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
The Windows Network Connections manager reports
“Network cable unplugged”
status for a EVLAN.
The “network cable unplugged” status now indicates that the connection group on the MCP server is closed.
All Platforms
Connecting to the MCP from the Windows server fails or uses the public LAN rather than EVLAN on servers with more than 4 NICs defined.
See Microsoft knowledge base article 253811,
“How to Disable NetBT Per Adapter Cache Behavior” for information about a registry setting that must be made on Windows servers that have more than four network adapters being used for NetBIOS over TCP/IP communications.
Libra Series servers
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
The response to the NW NP
<NP #> command for an NNS device indicates that the device is NASCENT.
Check for a popup window on the Windows server for the Service Control Manager indicating that "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details". In this case, the event log would be the Windows system event log.
Look for log entries for the Service Control Manager of the appropriate date and time and examine them. If the description indicates that any of the NNS services or drivers listed in Appendix B failed to start or load then a reboot of the Windows server is necessary to restart NNS.
Also, check for a popup window indicating that an application error has occurred and an application error log is being generated. If this window indicates that any of the NNS services listed in Appendix B is at fault then a reboot of the Windows server is necessary to restart NNS. In some rare cases, an NxNet uninstall and reinstall may be necessary to resolve the problem of one of the services or drivers (in Appendix B) not starting properly.
Note that a state of NASCENT is normal in some cases while the MCP Server is waiting for the Windows server to complete its boot cycle and initialize the NNS device. The Windows server boot cycle may take several minutes to complete.
See Section 6 for a description of the materials to collect when reporting these types of problems.
All Platforms
The status <OUT OF SERVICE>
is reported when you issue the OL PORT <port #> command.
This occurs after Network Services has been running successfully.
Network Services was stopped for more than 10 minutes for any reason. These reasons could include manually stopping the service, rebooting the Windows server, or a software or hardware failure that caused the Windows server to halt.
To correct the problem, issue the UR – PORT command after Network Services is active.
All Platforms
The following message displays when you issue the UR – PORT command:
PORT <port #> is available, but it is unusable as a path to all controls it services.
1. From the desktop, right click on "My Computer"
and choose "Manage".
2. Select "System Information" and then
"Software Environment".
3. Select "Drivers" and verify that the Unisys NNSDRLOG Driver (nnsdrlog) is running.
4. Select "Services" and verify that the Unisys Network Services service (CNP) is running.
MCPvm
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
The following message displays when you issue the UR – CTL command:
CTL <control #> not made available. It is not in partition.
The control number was not acquired. Use the ACQUIRE CTL command as follows:
ACQUIRE CTL <control # of NP>
where <control #> is 7000 for a PCI bridge, increments by 2 up to 7018 for the 10th PCI bridge, and is 210 for emulated systems.
MCPvm
The following messages display when you issue the UR – PORT command:
PORT <port #> HAS BEEN REPORTED BROKEN BY THE IOP.
PORT <port #> NOT MADE AVAILABLE. IT FAILED TO
PORT <PORT #> WILL NOT BE USED; ABC PROTOCOL FAILED TO INITIALIZE.
These messages indicate that Network Services has not been installed correctly on the Windows server.
See “Installing Network Services” in Section 2 for instructions for installing Network Services on the Windows server.
Also see “Bringing Network Services Into Service for the First Time” and “Reinitializing Network Services” in Section 6.
See “Gathering Values for Installation” in Section 2 for information.
Also see “Examining or Updating Network Services Values” in Section 3 or 4.
All platforms
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
You see a Windows “blue screen” with an error message that describes the problem and the module where the problem occurred.
A serious problem has occurred. Report the problem to your Unisys representative, and submit the following:
• NP dump file from the MCP server
• Event Log backup from the Windows server
• Problem description as reported on the first three lines of a Windows “blue screen”
• Crash dump file MEMORY.DMP. (If the Windows server is configured to do so, it puts this crash dump file into the directory that is specified in the Recovery section of the System applet on the Control Panel.) See these topics in Section 6 for related information:
“Recovering the Windows Event Log”
“Recovering the Windows Event Log Manually”
“Submitting Trouble Reports”
Also see this topic in Section 2:
“Managing the NetBIOS Name Cache
After encountering a Windows “blue screen”, use the following procedure to recover from the Windows stop:
1. Issue the UR PORT <port#> command for the port associated with the Windows server.
2. Wait for the Windows server to finish copying its memory to a dump file. The memory image copy is complete when the message beginning
“Restart and set the recovery options in the system control panel…” is displayed at the bottom of the screen.
3. Issue the UR- PORT <port#> command to bring the port online.”
4. Power off and power on the Windows server.
Wait for the Windows server to complete its initialization.
All platforms
A message indicating that the Event Log is full displays.
Examine the contents of the Windows Event Log. If you don’t notice anything unusual, you may need to change the parameters of the Event Log as
described in “Completing Installation of Network Services (Virtual Machines with Multiple NPs).
All platforms
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
You cannot establish
connections to network drives in the MCP environment over a non-EVLAN path.
Check the Services applet on the Control Panel to verify that Network Services is running.
Network Services may be attempting to use the EVLAN path when it is not available. To restore the non-EVLAN path
• See “Directing Data through the Fast Ethernet Switch Data Path” in Section 3, “Directing Data through the Ethernet Switch Data Path” in Section 4, or “Directing Data through the Externally Configured LAN” in Section 5.
• Also see “Managing the NetBIOS Name Cache”
in Section 2 for information about how
Network Services manages the NetBIOS Name Cache.
All platforms
You are able to successfully PING a remote host by specifying its name, but when you try to connect a network drive to a share on the remote host, you get the following message:
SEMAPHORE TIMEOUT PERIOD HAS EXPIRED
The NetBIOS remote name cache probably contains an entry for the remote host that cannot be used.
This usually occurs when the LMHosts file contains an entry for the MCP server using the EVLAN path, but the Network Services service is not running.
To restore the non-EVLAN path, see “Directing Data through the Fast Ethernet Switch Data Path” in Section 3, or “Directing Data through the Externally Configured LAN” in Section 5. Also see “Managing the NetBIOS Name Cache” in Section 2 for
information about how Network Services manages the NetBIOS Name Cache.
All platforms
An OL NP inquiry on the EVLAN adapter (700n or 210) shows that the NP is active - communicating, but the response to an NW NP <device number> inquiry is
GREETING SENT.
It is likely that the NP Unit Number for Network Services defined in the Windows environment does not match the NP Number defined in the MCP environment.
To update NP Unit Number in the Windows
environment so that it matches the number defined in the MCP environment, see “Examining or Updating Network Services Values” in Section 3 or 4. Step 4 of the procedure describes how to change the value.
MCPvm
You are not sure if data is taking the EVLAN data path
Refer to “Verifying Network Services Installation”
in Section 2 for two test procedures to use.
All platforms
During CNS initialization file processing on the MCP server, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services shared adapter:
Hardware Not Present
Verify that the LINEID specified in the initialization file matches the CNS Line ID specified during Network Services Setup.
All platforms
Table 7–1. Troubleshooting Network Services
Problem Possible Corrective Action Applies To
During CNS initialization file processing on the MCP server, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services shared adapter:
Invalid Attribute Value
Verify that the value specified as the local address (in the initialization file ADD CONNECTIONGROUP command) matches the MAC address of the adapter NIC in the Windows server. For additional information, see “Determining Fast Ethernet or Gigabit Ethernet Information” in Section 3 or 4.
Verify that the speed setting is appropriate for the adapter type you are using.
All platforms
ClearPath Network Appliance
Problems Refer to the appropriate ClearPath Network Appliance Implementation Guide for
troubleshooting procedures for the CNA on Libra Series native MCP servers.
Libra Series native MCP servers, FS1800 servers
The IP address for Network Services EVLAN is not correct (as shown in the configuration summary of the Adapters.txt file generated by Network Services Setup)
Examine the IP address for Network Services EVLAN via the Windows Control Panel for the correct value. For details, see “Examining or Updating Network Services Values” in this guide.
Note that changes to Network Services parameters via the Windows Control Panel are not reflected in the Adapters.txt file. To keep this file up to date, use Network Services Setup to make configuration changes.
All platforms
MCP Cryptographic Services does not work when the Windows Firewall is active on a Windows 7 system.
Firewall Products, such as Windows Firewall may not work with the EVLAN drivers. To maintain all EVLAN functions, you should deactivate the Windows Firewall on the EVLAN adapter.
MCPvm
This appendix provides guidelines for building CNS, TCP/IP, and BNA network
initialization files and also includes a preconfigured SNMP initialization file. You can find sample CNS and TCP/IP initialization files for the following servers on the Network System Software NETSYSTEM release media.
• VMMCP servers (LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760)
• Libra 4000, and FS1800 servers
• Libra Model 680 and 690 servers
In addition, a preconfigured SNMP agent initialization file is included on the NETSYSTEM release media.
If you want to create your own CNS or TCP/IP initialization files, refer to the sample files on the NETSYSTEM release media and to the “Guidelines for Building CNS
Initialization Files” or “Guidelines for Building TCP/IP Initialization Files” sections later in this appendix. If you want to create BNA (also known as Heritage Network Services) initialization files, refer to “Guidelines for Building BNA Initialization Files” later in this appendix.