<br><br><div class="gmail_quote">On Wed, Dec 26, 2012 at 3:46 AM, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</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 25/12/12 15:54, Tim Phipps wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Quoting Gabe Rubin <<a href="mailto:gaberubin@gmail.com" target="_blank">gaberubin@gmail.com</a>>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cannot find (ping) database host 192.168.1.101 on the network<br>
</blockquote>
<br>
That's because 192.168.1.101 is not a host name it's an IPv4 address. Try using<br>
the hostname instead. I had the same problem when I moved a lot of stuff to<br>
IPv6: mythbackend will only ping an IPv4 resolvable hostname and I didn't have<br>
an IPv4 address for my database.<br>
<br>
</blockquote></div>
You're much more likely to be able to ping an IP address than you are pinging a hostname. After all, /someone/ has to resolve that hostname into an IP address for the ping to work at all!<br>
<br>
The resolving can be done either (or both) of two ways: You either have an /etc/hosts file in the machine that needs to do the resolving or someone on your internal network has a DNS resolver. This last is usually your router or firewall. If you are all on the same box (a combined BE/FE) then a hosts file is usually enough.<br>
<br>
192.168.1.101 is either: powered off, disconnected from the network, bad cable, bad network configuration so that it's not listening, not mapped (see above) or firewalled. Pick one.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
</font></span><br></blockquote><div><br>It is on the same machine I am trying to do the ping from. I can regularly ping the machine (and can do that from another machine in the network). I could see a firewall issue, but don't think I have any firewall set up on the machine (aside from the NAT router it is behind). I am also able to do this, so don't understand why myth is having difficulty:<br>
[root@localhost mythtv]# mysqladmin ping -h 192.168.1.101 -u mythtv -p<br>Enter password:<br>mysqld is alive<br></div></div><br>