Hi Antonio,<br><br>We're seeing the second problem (adding a new service when using unicast causes old ones to restart on a multicast address) here at RIT, running Windows XP. I just submitted a bug report for it (<a href="http://bugzilla.mcs.anl.gov/accessgrid/show_bug.cgi?id=1678">
http://bugzilla.mcs.anl.gov/accessgrid/show_bug.cgi?id=1678</a>).<br><br>--Andrew Ford<br><br><div><span class="gmail_quote">On 7/12/07, <b class="gmail_sendername">Antonio Bandeira</b> <<a href="mailto:bandeira@fe.up.pt">
bandeira@fe.up.pt</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I've found a few "problems" with the new
AG3.1 beta. Don't know if it is<br>just me, but...<br>I am currently running FC7, but I think some of this problems can also be<br>found in WinXP.<br><br>- Bridge sorting is not persistent. After restart agtk the order is no
<br>longer the one set under "preferences".<br>- Working in unicast mode, adding a new service under "node management" will<br>cause all previously added services to restart using a multicast address.<br>- Autoplace from VIC will not show up for the second time I try to set it.
<br>The first time I hit 'autoplace' in vic, it works fine. I can set it ok and<br>when done I hit 'quit'. When I try to set it again, hitting 'autoplace'<br>button in vic, it does nothing.<br><br>
I also had problems connecting to a 3.0.2 Venue Server with encryption set<br>up. Vic was not able to connect. I am not very sure about this, but at that<br>time, the only way to solve it was removing encryption from the venue
<br>configuration.<br><br>Best regards,<br><br>António Bandeira<br>FEUP :: SICC ~ uTICM<br>+351 225 574 199 (ext.3535)<br><a href="mailto:bandeira@fe.up.pt">bandeira@fe.up.pt</a><br><br><br><br></blockquote></div><br>