Re: [mythtv-users] access denied for remote frontend

2006-01-07 Thread Michael T. Dean

Eric Sharkey wrote:

And was shown in the original e-mail (albeit, slightly obscured).  ;)  
Just make sure the Myth box isn't connected directly to the 'net.
   


Yeah, I know.  If they get through the firewall, I'd be worried
about more than just the mythtv box...

Thanks for the replies.  I eventually got it working last night.

I'm ashamed to say it was as simple as a mistyped password.

It was set up with one of those auto-generated uncrackable but
also unmemorable passwords.  When I connected via the mysql command
line client, I cut and paste the password directly from
an image of /etc/mythtv/msql.conf from an ssh session into the
mythtv backend.  That worked.  When I configured the frontend,
it ran fullscreen and I typed the password into the gui from my
(flawed) memory.
 

But, on the bright side, it's a better password than just "mythtv"--it 
was even keeping you out for a while.  :)


Glad you got it working.

Mike
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-07 Thread Eric Sharkey
> And was shown in the original e-mail (albeit, slightly obscured).  ;)  
> Just make sure the Myth box isn't connected directly to the 'net.

Yeah, I know.  If they get through the firewall, I'd be worried
about more than just the mythtv box...

Thanks for the replies.  I eventually got it working last night.

I'm ashamed to say it was as simple as a mistyped password.

It was set up with one of those auto-generated uncrackable but
also unmemorable passwords.  When I connected via the mysql command
line client, I cut and paste the password directly from
an image of /etc/mythtv/msql.conf from an ssh session into the
mythtv backend.  That worked.  When I configured the frontend,
it ran fullscreen and I typed the password into the gui from my
(flawed) memory.

Oh well.

Eric
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-07 Thread Michael T. Dean

Eric Sharkey wrote:


I'm trying to connect a remote frontend to a working mythtv box and I
keep getting Access Denied errors when the frontend tries to connect
to the mysql server.
 

How about the exact (full text of the) error message.  Also, what's in 
the logs?  When you said you read the docs, you mean you tried all of 
these http://dev.mysql.com/doc/refman/4.1/en/access-denied.html ?


Mike
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-07 Thread Michael T. Dean

Eric Sharkey wrote:

I've had problems with invalid characters in passwords before. Not  
specifically with myth, but if I have an FTP account with a slash in  
the password, I can connect with some clients, but not others. Maybe  
something along the same lines is happening here? Try changing your  
password to alphanumeric (if not already) and try again. If it  
already is, sorry for the noise. :)
   


Thanks, but the password already is alphanumeric...
 

And was shown in the original e-mail (albeit, slightly obscured).  ;)  
Just make sure the Myth box isn't connected directly to the 'net.


Mike
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-05 Thread Stephen Kitchener
On Thursday 05 Jan 2006 16:54, Eric Sharkey wrote:
> Thanks for the reply, Steve.
>
> > On Thursday 05 Jan 2006 16:16, Eric Sharkey wrote:
> > You need to change mysql's startup file...
> >
> > /etc/sysconfig/mysqld
>
> I assume you mean /etc/mysql/my.cnf.

Nope, that's where the RPM put the file.

>
> > eg...
> >
> > # (oe) Remove --skip-networking to enable network access from
> > # non local clients. Access from localhost will still work.
> > # MYSQLD_OPTIONS="--skip-networking"
> > MYSQLD_OPTIONS=""
> >
> > # (oe) set TMPDIR and TMP environment variables
> > TMPDIR="${datadir}/.tmp"
> > TMP="${TMPDIR}"
>
> How does this help?

It dosn't...sorry I misread your email - 
>
> As I said, I have no problems connecting to the mysql server
> from the remote frontend using the mysql command line client.
> The mysql server is configured for remote network access and it
> works.  The problem is not a skip-networking setting or anything
> like that.  If it was, I couldn't connect at all.
>
> I have tmpdir set to /tmp.  I've not read anything that suggests
> that this setting would be important, provided that /tmp has
> sufficent space.
>
> The problem seems to be that the mythfrontend client is not sending
> the right password or not sending it in the right way.  I can't
> figure out why.
>
> Eric
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-05 Thread Eric Sharkey
> I've had problems with invalid characters in passwords before. Not  
> specifically with myth, but if I have an FTP account with a slash in  
> the password, I can connect with some clients, but not others. Maybe  
> something along the same lines is happening here? Try changing your  
> password to alphanumeric (if not already) and try again. If it  
> already is, sorry for the noise. :)

Thanks, but the password already is alphanumeric...

Eric
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-05 Thread Brad DerManouelian

On Jan 5, 2006, at 11:54 AM, Eric Sharkey wrote:



Thanks for the reply, Steve.


On Thursday 05 Jan 2006 16:16, Eric Sharkey wrote:
You need to change mysql's startup file...

/etc/sysconfig/mysqld


I assume you mean /etc/mysql/my.cnf.


eg...

# (oe) Remove --skip-networking to enable network access from
# non local clients. Access from localhost will still work.
# MYSQLD_OPTIONS="--skip-networking"
MYSQLD_OPTIONS=""

# (oe) set TMPDIR and TMP environment variables
TMPDIR="${datadir}/.tmp"
TMP="${TMPDIR}"


How does this help?

As I said, I have no problems connecting to the mysql server
from the remote frontend using the mysql command line client.
The mysql server is configured for remote network access and it
works.  The problem is not a skip-networking setting or anything
like that.  If it was, I couldn't connect at all.

I have tmpdir set to /tmp.  I've not read anything that suggests
that this setting would be important, provided that /tmp has
sufficent space.

The problem seems to be that the mythfrontend client is not sending
the right password or not sending it in the right way.  I can't
figure out why.

Eric


I've had problems with invalid characters in passwords before. Not  
specifically with myth, but if I have an FTP account with a slash in  
the password, I can connect with some clients, but not others. Maybe  
something along the same lines is happening here? Try changing your  
password to alphanumeric (if not already) and try again. If it  
already is, sorry for the noise. :)


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-05 Thread Eric Sharkey

Thanks for the reply, Steve.

> On Thursday 05 Jan 2006 16:16, Eric Sharkey wrote:
> You need to change mysql's startup file...
> 
> /etc/sysconfig/mysqld

I assume you mean /etc/mysql/my.cnf.

> eg...
> 
> # (oe) Remove --skip-networking to enable network access from
> # non local clients. Access from localhost will still work.
> # MYSQLD_OPTIONS="--skip-networking"
> MYSQLD_OPTIONS=""
> 
> # (oe) set TMPDIR and TMP environment variables
> TMPDIR="${datadir}/.tmp"
> TMP="${TMPDIR}"

How does this help?

As I said, I have no problems connecting to the mysql server
from the remote frontend using the mysql command line client.
The mysql server is configured for remote network access and it
works.  The problem is not a skip-networking setting or anything
like that.  If it was, I couldn't connect at all.

I have tmpdir set to /tmp.  I've not read anything that suggests
that this setting would be important, provided that /tmp has
sufficent space.

The problem seems to be that the mythfrontend client is not sending
the right password or not sending it in the right way.  I can't
figure out why.

Eric
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] access denied for remote frontend

2006-01-05 Thread Stephen Kitchener
On Thursday 05 Jan 2006 16:16, Eric Sharkey wrote:
You need to change mysql's startup file...

/etc/sysconfig/mysqld

eg...

# (oe) Remove --skip-networking to enable network access from
# non local clients. Access from localhost will still work.
# MYSQLD_OPTIONS="--skip-networking"
MYSQLD_OPTIONS=""

# (oe) set TMPDIR and TMP environment variables
TMPDIR="${datadir}/.tmp"
TMP="${TMPDIR}"

Steve

> I'm trying to connect a remote frontend to a working mythtv box and I
> keep getting Access Denied errors when the frontend tries to connect
> to the mysql server.
>
> I've read the docs and googled this to find all of the common problems
> and none of them seem to fit my situation.
>
> The mysql server is up and correctly configured for remote access.
> If on the remote frontend box I run:
>
>   mysql -h mythtered -u mythtv -p mythconverg
>
> Then I get connected correctly and can see all of the tables, yet when
> mythfrontend tries to connect to the same host using the same dbname,
> username, and password it gets access denied.
>
> I snarfed the mysql network traffic and looked at the difference
> between the mysql command line client and the mythfrontend traffic and
> noticed that mysql sends a packet that looks like:
>
> 0x:  4508 0080 7379 4000 4006 019a c0a8 2201  [EMAIL 
> PROTECTED]@.".
> 0x0010:  c0a8 220b a157 0cea 6049 546a f15c f05f  .."..W..`ITj.\._
> 0x0020:  8018 05b4 b4ad  0101 080a 60a6 271b  `.'.
> 0x0030:  9ebf dbb9 4800 0001 8da6 0300  0001  H...
> 0x0040:  0800         
> 0x0050:      6d79 7468 7476 0014  mythtv..
> 0x0060:  c18a 400a ccf7 be84 35aa df4f dd48 f934  [EMAIL PROTECTED]
> 0x0070:  f16d 8e76 6d79 7468 636f 6e76 6572 6700  .m.vmythconverg.
>
> while mythfrontend looks like:
>
> 0x:  4508 0058 b25c 4000 4006 c2de c0a8 2201  [EMAIL 
> PROTECTED]@.".
> 0x0010:  c0a8 220b a11b 0cea 5f6d 528a f03e 2a70  .."._mR..>*p
> 0x0020:  8018 05b4 2aa8  0101 080a 60a5 e0e1  *...`...
> 0x0030:  9ebf 9582 2000 0001 8d20  006d 7974  .myt
> 0x0040:  6874 7600 5f5c 4952 555e 525d 006d 7974  htv._\IRU^R].myt
> 0x0050:  6863 6f6e 7665 7267  hconverg
>
> It looks like both of these packets end with username, obscured password,
> and database name but, but the mythfrontend is using fewer characters
> for the password, so it must be using some sort of different password
> obfuscation algorithm, or a different password.
>
> Any idea what could cause this?
>
> Both machines are Debian Sid running the same mythtv 0.18.1 packages.
>
> Eric
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users