I have BusinessEntitites for both of these OIDs in my uddiConnectionInfo.xml (I also tried internalConnectionInfo.xml for kicks).
What I'm seeing the gateway actually do, though, is send a query to the first entry (.1003 in my example) and ignore the second entry entirely. I verified this by swapping the order of the OIDs in the NhinTargetCommunities.
I can't tell based on that link if this was maybe a roadmapped feature that was never implemented?
Re: Querying Multiple Communities With One "Trigger" (NhinTargetCommunities)
John, are you set up in passthrough mode? Our fanout logic sends to only the first target in passthrough. Also, sorry if it's already been asked, but if you can give us some more background on the context in which you use CONNECT, it could help us in supporting you further.