The Question is:
We are currently writting a new Windows based GUI for our core system, which
runs on VMS7.2-1. The comms are via TCP (V5.0a-1 install on Alpha box). The
server sets up its sockets and sits listenning for connections using QIOW
calls. This works fine and i
t accepts connections from a WindowsNT client. However, it will not respond to
connection requests from a Windows98 client (of any type).
The socket is being created and is listenning on the server side - UCX SH DEV
says so. The Windows98 client is configured correctly and can ping the server.
The Answer is :
As the IP and application connection is working between OpenVMS
and Windows NT, an assumption that OpenVMS would be at fault when
an application on Windows 98 is not cooperating appears somewhat
odd -- on OpenVMS, the same stack is used. Thus this would initially
appear to be a network configuration error, a problem with the Windows
98 client or IP stack, or some sort of an application error. Though
without a whole lot more detail on the problem, a problem in OpenVMS,
TCP/IP Services V5.0A, the application code, or most any other component
involved here cannot be ruled out.
Use of the OpenVMS COM support would be an alternative here.
Please contact the Compaq Customer Support Center, as a short reproducer
will be required.