OS/2 Troubleshooting
8 Have you applied appropriate fixpacks, APARs (see Compatibility for required fixpacks)? If not, the proper fixpack must be applied.
TCP/IP for OS/2 | 1 Make sure the OS/2 Spooler Print Priority is at the | |
versions 2.0, 3.0, 3.1, | maximum value of 189 (lowering this value frees up | |
memory resources but can have adverse affects on | ||
4.0 | printing graphics). Try adjusting the value to “tune” your | |
| server/workstation performance. | |
| 2 Changes to TCP/IP Configuration may require system | |
| reboot rather than the OS/2 Command “TCPSTART.” | |
OS/2 | OS/2 Warp V 4.0, OS/2 Warp V 3.0 (all | |
Troubleshooting | versions), Warp Server, LAN Server 4.0, & Warp | |
| Connect using TCP/IP for OS/2 versions 2.0, 3.0, | |
3.1, 4.0 | ||
| ||
| 1 At the OS/2 Command Prompt, issue the command: | |
| ping xxx.xxx.xxx.xxx, | |
| where, xxx.xxx.xxx.xxx is your server IP address (i.e. | |
| 109.108.145.22). If you receive a correct ping reply, go to | |
| step 2; otherwise check your TCP/IP configuration and | |
| your LAPS/MPTS/APS configurations. (See IBM | |
| Documentation for configuring TCP/IP for OS/2 and TCP/ | |
| IP LAPS/MPTS/APS configuration.) | |
| 2 At the OS/2 Command Prompt, issue the command: | |
| ping xxx.xxx.xxx.xxx | |
| where, xxx.xxx.xxx.xxx is your DocuPrint printer | |
| IP address (e.g.109.108.145.22). If you receive a correct | |
| ping reply, go to step 3; otherwise, check to see that the | |
| DocuPrint printer IP address has been correctly entered on | |
| the printer. Print a Configuration Sheet and confirm that | |
| the IP address is entered correctly. If necessary, reenter | |
| your IP addresses (IP address, Gateway Address, Subnet | |
| Address). |
Chapter 7: OS/2 Network Setup ❖
