said:
>You need to resolve the winsock error before the trace can have any
>meaning. You must still have the wrong winsock installed somewhere such
>that it can be found by your eCS WinOS2 setup. Check your autoexec.bat
>PATH and check the various INIs in the WINOS2 directory.
That problem resolved. When I turned off "show pictures" and "play sounds"
in IE, the eCS machine connected just fine without winsock errors.
Now -- warp 4 connects to Quicken.com without problem (see warp.txt).
eCS does not connect to quicken -- it says it can't find the server (see
ecs.txt).
I don't see anything obvious to me on the iptraces. One shows the
connection to quicken and the other does not. I can't figure out if it
says why. If you get a chance to look at these, let me know if anything
stands out for you. AFAIK, both systems (Warp and eCS are configured the
same).
Thanks,
Sandy
Content Type: application/zip
File attachment:
868iptrace.zip
<< Previous Message <<
Return to [ 15 |
March |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.