Re: Stability of Program Linking via IP.
Re: Stability of Program Linking via IP.
- Subject: Re: Stability of Program Linking via IP.
- From: Steven Angier <email@hidden>
- Date: Thu, 01 Aug 2002 10:15:35 +1000
On 1/8/02 4:19 AM, "Robert Eppich" <email@hidden> wrote:
>
The following appleScript:
>
>
tell application "Finder" of machine
>
"eppc://h24-207-32-75.dlt.dccnet.com"
>
name
>
end tell
>
>
often works without any problems for days and weeks, however, we have
>
run across instances where the same code will work unreliably and may
>
cause a freeze on the Mac running it and even freezes on the target Mac.
>
When this code does not work properly, we are still able to use file
>
sharing to the target Mac and reliably mount volumes, but we most likely
>
are not able to see any programs if we use the 'choose application'
>
command. However, if we check port 3031 on both Macs, we find that it is
>
open and pinging the target Mac will also work successfully.
>
>
This problem has been present since Program Linking via IP was
>
introduced. We believe the problem is with either the Keychain, the
>
Cable/DSL modems, or that port 3031 is not clear. In these cases, no
>
error is returned when we add the 'Try' block. The only way to fix this
>
problem temporarily, is to restart the computer and/or the Cable/DSL
>
modems and sometimes a clean install is the only thing that works.
I (and others on this list) have tried in vain to get any response from
Apple about this. In our situation, we were able to rule out both the
keychain (by not using it) and any intermediate network hardware (by
connecting the machines together directly with a crossover cable). The
machine sending the event would simply freeze (though never on the first
remote event -- it would always work). Manually breaking into MacsBug would
reveal the current procedure as "ipcKillListPorts". We were beginning to
suspect CarbonLib, though we were able to use AppleTalk to solve our problem
(which has worked flawlessly ever since).
All we ever got after days of troubleshooting and isolating the problem for
Apple, rudely, was silence.
>
How can we find the cause and/or prevent it from happening? Any insights
>
would be greatly appreciated.
I think you might have to join the ADC as a paid member, file a bug, and, if
necessary, use up one of your technical support incidents.
But, if you do, please let us know what you find out.
Steven Angier
Macscript.com
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.