When you say that some can see the bridge and others can't, I assume you mean that the bridge does not appear in the list of bridges at Tools->Bridges. That list contains bridges that are usable by the VenueClient, which is determined as follows:
- can the VenueClient send requests to the bridge? This indicates whether the bridge process is functioning and is reachable for TCP requests. - can the VenueClient receive data over unicast from the bridge? This indicates whether the VenueClient can receive UDP data from the bridge host, which depends on proper operation of the bridge, the network between the bridge and the VenueClient, and firewalls at the client side. If one of these fails, the bridge is marked 'disabled' and will not appear in the list at Tools->Bridges. All bridges will still appear in Tools->Preferences->Bridges, including disabled bridges. I suspect your bridge is being detected by all clients, and you'll find it marked disabled in some of them. If your case is different from this, let us know and we can investigate further. Tom On Sep 29, 2010, at 7:32 PM, HyungJin Kim wrote: > > I excuted Bridge by using command "Bridge -p 20200 -u > http://www.accessgrid.org/registry/peers.txt -n "Gist-AG-Server" -l "kwangju" > and now the bridge is running. > > some computer can see the bridge but anothers can't see the bridge. > if you knows this problem. tell me about it. > thank you. > > HyungJinKim
