Job Management Partner 1/Software Distribution Administrator's Guide Volume 2

[Contents][Glossary][Index][Back][Next]

6.4.2 Actions to be taken when JP1/Software Distribution does not operate normally

Problems, such as failure to operate normally, and errors can occur during the operation of JP1/Software Distribution Client (client). This section explains possible problems that can occur and how to resolve them, according to each operating system.

Organization of this subsection
(1) Locating services and hosts files to be edited
(2) Client cannot communicate with the higher system
(3) Installation and packaging fail
(4) JP1/Software Distribution Client (client) hangs when a network hardware error, such as incorrect LAN cable connection, occurs
(5) AMT Linkage does not operate correctly

(1) Locating services and hosts files to be edited

(a) Windows NT

If the default installation directory for Windows is \WINNT, the hosts and services files are located in the following directory:

\WINNT\system32\drivers\etc

Specifying a host name
Windows Server 2003 or Windows XP
  1. In Control Panel, choose System.
  2. On the Computer Name page, click the Change button.
  3. In the Computer Name Changes dialog box, enter the computer name.
Windows 2000
  1. In Control Panel, choose System.
  2. On the Network ID page, click the Properties button.
  3. In the Identification Changes dialog box, enter the computer name.
Windows NT 4.0
  1. In Control Panel, choose Network.
  2. Choose TCP/IP protocol from Network Protocol on the Protocol page, and then click the Properties button.
  3. On the DNS page of the TCP/IP Protocol dialog box, specify the host name.
(b) Windows Me or Windows 98

The hosts and services files are located in the Windows installation directory, which is C:\WINDOWS.

The following procedures describe how to set an IP address normally, and how to set it using DNS

Normal setting method
  1. In Control Panel, choose Network.
  2. Specify your settings in the User identification page.

Using DNS
  1. In Control Panel, choose Network.
  2. In the Configuration page, choose TCP/IP, and then click Properties.
  3. In the DNS configuration page, specify DNS settings.

(2) Client cannot communicate with the higher system

If a job error occurs, it may be because the client cannot communicate normally with the higher system. Use the method below to determine whether the communications environment has been set up properly.

(a) Windows NT
(b) Windows Me or Windows 98

To check the current TCP/IP communications environment, execute the WINIPCFG command from the command prompt.

(3) Installation and packaging fail

If the installation or packaging of a package fails, check to see if there is enough disk space. For required disk space, see 5.3.3(4) Disk space required for package installation and 5.3.3(6) Disk space required for packaging in the manual Description and Planning Guide.

(4) JP1/Software Distribution Client (client) hangs when a network hardware error, such as incorrect LAN cable connection, occurs

(a) Windows NT

Check the keep alive settings for the TCP/IP environment. The following settings in the register values should be checked:

This value specifies the length of time until an error is detected. The following setting range and default value apply:

Setting range:
1 to 0xFFFFFFFF

Default:
7,200,000 milliseconds (2 hours)

To reduce the length of time until an error is detected, reduce the value. This value affects all TCP/IP applications. A value that is excessively small can generate excessive communications errors. For further details, see books on the Windows NT resource kit.

In addition, you should check to see whether the keep alive settings in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\adapter-name\Parameters\Tcpip key are enabled.

(b) Windows Me or Windows 98

Check the keep alive settings for the TCP/IP environment. The following registry settings should be checked:

This setting indicates the amount of time allowed until an error is detected. The following allowable range and default apply:

Setting range:
1 to 0xFFFFFFFF

Default:
7,200,000 milliseconds (2 hours)

To reduce the length of time until an error is detected, reduce the value. This value affects all TCP/IP applications. A value that is excessively small can generate excessive communications errors. For further details, see books on the resource kit for this operating system.

(5) AMT Linkage does not operate correctly

If use of AMT Linkage does not restore the host identifier when you are re-installing the client, consider the possible causes explained below.

(a) AMT does not exist on the PC

Check that the client PC supports AMT. If not, N/A is displayed in the system information's AMT firmware version item.

(b) The Provision model setting is incorrect

Check that Small Business is set for the Provision model of AMT. If the model setting is incorrect, N/A is displayed in the system information's AMT firmware version item.

(c) The user name or password set for AMT is incorrect

Check that the user name and password set for AMT are correct. If not, N/A is displayed in the system information's AMT firmware version item.

(d) The nonvolatile memory of AMT is not initialized

The host identifier cannot be restored from the nonvolatile memory of AMT when you reinstall the client. This is because the host identifier is not stored if the nonvolatile memory of AMT is not initialized before initial installation of the client.

If the nonvolatile memory of AMT has not been initialized, the version is displayed in the system information's AMT firmware version item.

(e) Restoration of the host identifier failed

When restoration of the host identifier fails, the host identifier stored in the nonvolatile memory of AMT is rewritten by the host identifier that was created during installation. The host identifier that was created is reported to higher systems.

In this case, you should use the managing server to search for a duplicate host. If a duplicate host is found, delete it.