"K. M. Peterson" <KMP AT LOGOS.CV DOT COM> writes:

>>> Does anyone have any ideas on getting the Windows client to work with Sun
>>> PC/NFS?  We got the product loaded, and found that supplying the server
>>> IP address in the opt file caused an "invalid host name" error; supplying
>>> the host name of the server eliminated the error, but the client process
>>> hangs. NETSTAT on CMS shows the session "established" with one byte sent
>>> and one byte received...

I have not tested this particular stack. Do you know if it is WinSock 1.1
compliant ? Do you have other WinSock applications running ? It's been my
experience that many tcp/ip protocol stacks require special configuration to
run WinSock applications correctly. You might check your TCP/IP documentation
to see if this is the case. If so please post the results to this forum.

Also you might try specifying your TCPSERVER in dotted notation. If you are
still having problems  I'll give you some trace flags to turn on and you
can either send the trace file to me directly or post it here and I'll take a
look. The traceflags can either be specified in dsm.opt or on a command line
used to launch the dsm.exe Windows application.

Specify these options as follows in dsm.opt:

           TRACEFLAGS COMM,COMMDETAIL
           TRACEFILE  TCPIP.TRC

or on a command line as

           DSM.EXE -TRACEFLAGS="COMM,COMMDETAIL" -TRACEFILE=TCPIP.TRC


The trace file you specify will be written to the ADSM working directory
(usually the directory in which the ADSM executables reside).


Hope this helps some ....


>>> Pete Tanenhaus, ADSM Client Development