At 3:38 PM +0200 1999-12-25, <sinisa@stripped> wrote:
>Jim Sander writes:
> > > OK, then, it's not a TCP/IP problem, it's a MySQL problem.
>Have you tried
> > > putting all the host names in the host table? I wonder who MySQL thinks
> > > you are...obviously not who you think you are! ;)
> >
> > It's not a problem of mistaken identity, from a grant table perspective
> > at least. My "host" table is completely empty since I want to force
> > everyone to use passwords all the time. (our servers are open enough to
> > warrant this) Each user (other than root) has access to exactly one
> > database, which was set up with GRANT <list> for db@localhost (and %') -
> > cut-n-pasted from the manual.
> >
> > I still have a suspicion that this is NOT a MySQL problem- at least in
> > the traditional sense. I *can* connect using -h virtualserver.com from
> > another machine on our network, or in fact from any server on the
> > internet- not that I've tried them all obviously :)
> >
> > The problem only happens when using -h virtualserver.com from the
> > localhost. If you skip -h, you can connect using the mysql.sock - it's
> > like MySQL is refusing to use TCP/IP from the local host machine. This
> > makes not a bit of sense.
> >
> > I can "telnet virtualserver.com 3306" - but the mysql client gives a
> > "timed out" message, doing essentially the same thing. I have a
> > work-around solution, but remember- the big thing that's bothering me here
> > is the fact that I have 5 other servers with the identical setup that are
> > behaving. I don't want to have to say in the documentation for our
> > customers "hey, if you're on this flakey server you have to do something
> > different" since that can't be good for business.
> >
> > Anyway, this can certainly wait until the new year before I need an
> > answer. Happy holidays to everyone, especially those who have (tried at
> > least) helped me out with this problem, and the MySQL development team. In
> > a couple weeks we'll know if all the Y2K work paid off. :)
> >
> > -=Jim=-
> >
>
>Hi!
>
>Having host table empty is not recommendable.
Why is that? Or do you mean the db table?
>
>If you want to force all users to login with password, you should
>delete all anonymous users, the one which have '' in user column of
>the user table.
>
>If you have emptied host table, then only users which have '%' in host
>column of the user table can login.
host table? Do you mean db table?
--
Paul DuBois, paul@stripped
