So here is the current hardware set up:<br><br>We have an ethernet cable from the main school access point that is connected to each individual computer in the lab as well as the XS. However, we are currently not using the second ethernet port on the XS. The wiki page suggests connecting a wireless access point to the second ethernet port on the XS. However the school will not allow us to bring in our own router/access point of some kind as it will disrupt their current set up. Hardwiring the computers to the XS is also not very practical. <br> <br><div class="gmail_quote">On Tue, Jul 7, 2009 at 10:27 PM, Caroline Meeks <span dir="ltr"><<a href="mailto:solutiongrove@gmail.com">solutiongrove@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br><br><div class="gmail_quote"><div class="im">On Tue, Jul 7, 2009 at 10:20 PM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com" target="_blank">martin.langhoff@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Wed, Jul 8, 2009 at 9:46 AM, Anurag Goel<<a href="mailto:agoel23@gmail.com" target="_blank">agoel23@gmail.com</a>> wrote:<br> > We booted several computers with SoaS and changed the<br> > network settings from the default (<a href="http://jabber.sugarlabs.org" target="_blank">jabber.sugarlabs.org</a>) to the IP address<br> > on the XS. After doing this, the computers in the computer lab still would<br> <br> </div>That is a workaround to the missing "register" button in SoaS, right?</blockquote></div><div><br>no, we are still just trying to get the machines in the lab to see the Jabber Server in the lab via the server setting in the control panel.<br> <br>I think some of your comments below may still be relevant but I don't entirely understand.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im"> <br> <br> I suspect that part of the problem is that you are using the IP<br> address. Sugar will see whatever DNS or IP addr you provide there and<br> will try to connect to jabber and create an account as follows:<br> <br> - <machine-id>@<jabberservername><br> <br> On XO hardware, machine-id is the serialnumber. On other hw, it<br> creates a random string on first boot.<br> <br> The problem with the scheme is that jabber on the XS expects a very<br> specific jabber servername for the account: its own name (as given to<br> domain_config) prefixed with 'schoolserver.'<br> <br> If the name doesn't match that format, then it breaks.<br> <br> The workaround is to use "schoolserver.<mydomain>" in the SoaS control<br> panel. A more proper solution is probably to bring back 'registration'<br> :-)<br> <br> hth,<br> <br> <br> <br> m<br> <font color="#888888">--<br> <a href="mailto:martin.langhoff@gmail.com" target="_blank">martin.langhoff@gmail.com</a><br> <a href="mailto:martin@laptop.org" target="_blank">martin@laptop.org</a> -- School Server Architect<br> - ask interesting questions<br> - don't get distracted with shiny stuff - working code first<br> - <a href="http://wiki.laptop.org/go/User:Martinlanghoff" target="_blank">http://wiki.laptop.org/go/User:Martinlanghoff</a><br> </font></div><div class="im"><div><div></div><div>_______________________________________________<br> Sugar-devel mailing list<br> <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> </div></div></div></blockquote></div><div><div></div><div class="h5"><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br> </div></div></blockquote></div><br><br clear="all"><br>-- <br>Anurag Goel<br>