Live CD Front end can't connect to backend

[sbrattonuk]

Hi

I've a Mythbuntu 10.04, mythtv 0.23 setup running nicely as a master BE & FE on the same box. (My wife can even use it and wants me to expand the system).

Now has come the time to get MythTV running with remote Frontends. Trying the Live CD I can't get the live FE to connect to the backend.

BE : is fully setup with manual IP address 192.168.1.91 in both sections on the BE setup config.
Pin is set to 0000

FE testing connection to BE enter the PIN as 0000 then click "test" this fails, I get no further than the first step

Questions :

1. How does the FE find the back end, I'm guessing uPnP ?
2. How do I check if the BE has uPnP running?
3. Do the machines need to be on the same workgroup?
4. Is there anything else I need to check if it is running on the BE, eg mysql?

Other information:
The BE is on workgroup .mshome as appears on my network as BTV1.mshome The rest of my network is on workgroup .home (as assigned by my router). However pining btv1.mshome fails but pinging btv1.home succeeds.

Could this be where my issue resides ? or am I barking up the wrong tree.

Thanks in advance
Steven

[nickrout]

Hi

I've a Mythbuntu 10.04, mythtv 0.23 setup running nicely as a master BE & FE on the same box. (My wife can even use it and wants me to expand the system).

Now has come the time to get MythTV running with remote Frontends. Trying the Live CD I can't get the live FE to connect to the backend.

BE : is fully setup with manual IP address 192.168.1.91 in both sections on the BE setup config.
Pin is set to 0000

FE testing connection to BE enter the PIN as 0000 then click "test" this fails, I get no further than the first step

Questions :

1. How does the FE find the back end, I'm guessing uPnP ?
2. How do I check if the BE has uPnP running?
3. Do the machines need to be on the same workgroup?
4. Is there anything else I need to check if it is running on the BE, eg mysql?

Other information:
The BE is on workgroup .mshome as appears on my network as BTV1.mshome The rest of my network is on workgroup .home (as assigned by my router). However pining btv1.mshome fails but pinging btv1.home succeeds.

Could this be where my issue resides ? or am I barking up the wrong tree.

Thanks in advance
Steven

Workgroups are an MS concept to do with smb/cifs networking, so have nothing to do with it.

[nhtrader]

FE testing connection to BE enter the PIN as 0000 then click "test" this fails, I get no further than the first step

Can I ask what was the error message when you pressed "Test Connection" and it failed?

[sbrattonuk]

Sorry for the delay, work sent me to Sunny South Africa for a week, beats the UK cold.
____________
Connection Results:
Could not find database login
credentials
____________
Thanks
Steven

[sbrattonuk]

Just had a thought, what user name does the live CD use to login to the database on a backend.


I've got the remote backend set up as user = <mythuser>
Could the live CD be trying to login with user = <mythtv>
I assume my backend still has the mythtv user name as a valid login.


If not is there any way to force the live CD to use <mythuser>


Thanks
Steven

[AlecJ]

On the BE/FE machine,

in Mythbuntu Control Centre, under the MySQL tab, enable Master Backend Role
in MYTHTV Backend Setup/ General, ensure both IP's are the same and the port is 6543 and the status port is 6544, also note the pin number
The IP address must be the same as the Machine, so use a static IP.

I was unable to make Network Manager do this, so it is done manually,
edit /etc/network/interfaces to look something like this

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.92
gateway 192.168.1.??? (whatever your routers address)
netmask 255.255.255.0

and /etc/resolv.conf

# Generated by NetworkManager
nameserver 192.168.1.??? (whatever your routers address)

if you leave resolv.conf there will be no internet and no updates.

In the FE on the BE in settings/General make a note of the data base name, username and the password


On the new remote Frontend

On startup it will go looking for the uPnP and when found, May? ask for the username and password of your BE

I also use a static IP here, just to stop things moving about, very bad calmer when trying to VNC to a remote frontend.

Any Music or Video Folders will have to shared and mounted outside of Myth, either SMB or NFS, your choice. Then point the remote frontend to said Folders in mythmusic and or Videos.
HD does not Stream well over even on a 1Gb network. But LiveTV, music, videos and recorded TV works well.

For a LiveCD, the versions of MythTV must be the same, there is another Thread on this subject on here.

[sbrattonuk]

BE/FE machine - Mysql section of control center has database enabled.

Backend setup - general page has fixed ip address 192.168.1.91 in both sections and the ports as 6543 & 6544 as described, Pin is 0000.

My router assigns a static address to the BE/FE machine so I guess I shouldn't need to mess with the network settings on this machine.

On the BE/FE machine test connection succeeds and gives me the green tick.


I'm still stuck, I'm now thinking the problem is along the lines of network device discovery issue with uPnP. Are there any network tools I can run from a remote machine to search for uPnP devices on my network to see if I can detect the myth BE/FE.

Thanks for your advice so far.
Steven

[sbrattonuk]

I ran a heavy weight security scan (Nessus default scan)to the BE/FE machine.

port 6543 was present (lds-distrib)
but no mention of port 6544
Mysql was open on port 3306
No mention of uPnP

Steven

[AlecJ]

On the BE/FE machine test connection succeeds and gives me the green tick.

You mean on the remote front end machine?
can you ping the backend across the network?

I have to mess with the network setting, the router setting was not enough

[sbrattonuk]

Yes the machine can be pinged
I can even login to mythweb and watch/setup recordings

A bit of searching, gave another idea but I don't know how to check it out. Could the mysql database be only running on loopback and not the ethernet adapter?

I'll try fiddling with network settings if I get time tonight.
also tried 10.04 live cd instead of 10.10, no joy there either.

Steven