Comment below.<br><br><div class="gmail_quote">On Fri, Oct 7, 2011 at 10:16 PM, Robert McNamara <span dir="ltr"><<a href="mailto:robert.mcnamara@gmail.com">robert.mcnamara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Oct 7, 2011 at 9:01 PM, linux guy <<a href="mailto:linuxguy123@gmail.com">linuxguy123@gmail.com</a>> wrote:<br>
<br>
> <snip>2011-10-07 21:46:34.180 New DB connection, total: 2<br>
> 2011-10-07 21:46:34.182 Connected to database 'mythconverg' at host: server<br>
<br>
<br>
</div><div class="im">> 2011-10-07 21:46:36.120 Found mainmenu.xml for theme 'MythCenter-wide'<br>
> 2011-10-07 21:46:36.151 MythCoreContext: Connecting to backend server:<br>
> <a href="http://127.0.0.1:6543" target="_blank">127.0.0.1:6543</a> (try 1 of 1) <----------------- WHAT ? Why isn't this<br>
> server ?<br>
<br>
</div>Mythtv frontends connect to the database, and from there get the IP<br>
address for the master backend. Your frontend diligently connected to<br>
the DB you told it to, and pulled out the IP you configured on your<br>
backend for the Myth backend server... which is currently set to<br>
127.0.0.1.<br>
<br>
Go back into mythtv-setup on your backend and set the IP addresses to<br>
something externally accessible (NOT HOSTNAMES, and not 127.0.0.1 as<br>
you currently configured) in step one.<br>
<br>
So, not a bug. A misconfiguration.<br></blockquote><div><br>Excellent reply. And timely. Thanks. <br></div></div>