Kofax Communication Server 9.1 - Manual (Page 22)

Environment Guide Version 3.00.04
22 © Copyright Kofax, Inc. All information is subject to change without notice.
4.4.8 Known Issues on Outdated Third-Party Hardware
If running up-to-date KCS applications under modern operating systems like Windows 2008 on outdated
hardware which is not listed on Microsoft HCL, it must be taken into account that there is a higher risk that
any issues may occur during KCS installation and operation.
This chapter summarizes problems and hardware related issues which have already been observed on
particular outdated hardware.
Tyan Mainboard Thunder HESL-T S2688 Running Windows 2008
TCP connection problems were observed, documented in the SPR00054023: KCS FoIP Configuration
Utility cannot open local port under Win 2008 OS and huge communication problems between TCOSS
instances in the ASP Tandem Server were observed, too.
The main problem is that around 15-20 minutes after machine reboot, each attempt to make a synchronous
(blocking) TCP Connect to any existing IP address (remote or even localhost) but to a non-existing port
number (no listener on it) remains hanging instead of returning corresponding error saying that the port is
not reachable.
During first around 15 minutes after machine reboot this problem does not occur.
Finally, the problem has been isolated on new Windows 2008 installation on this main board, without any
KCS software, without any LAN card in the following way:
Open command line and try to open a Telnet session to localhost and not-existing port number 50000.
During the first 15 minutes after machine reboot it returns properly with an error:
Later on, it remains hanging in the “Connecting to localhost ….” status:
Note that this problem does not occur on this hardware in the case Windows 2003 is being used.