|
>> Anybody has any ideas how to solve this ? This happened all the time to me and to about 50% of my clients. From my experience it is almost certainly either then firewall and/or a NAT that is causing the problem. For years the debugger has used what I will politely refer to as a "flawed" design that effectively has the host component arbitrarily selecting ports to use for the communication back to the workstation. Since no request was made on that port by the workstation, most firewalls/NATs will block/throw away the response. The only easy fix that I know of is to upgrade to V6 where IBM finally fixed the %$@# thing so that all port usage is initiated from the workstation. This has worked for all customers that I have worked with to-date. Jon Paris Partner400 www.Partner400.com www.RPGWorld.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
