"Andrey Hristov" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >> > Hi, > AFAIK MySQL on windows by default tries to use TCP/IP, this differs from > the > default behavior on *nix, where it tries to Unix socket and after that > TCP/IP. > On windows nt one can use named pipes, however they are not enabled by > default. Use --enable-named-pipe, or just --skip-networking. The latter > instructs > MySQL not to use TCP/IP. > More info here : > http://dev.mysql.com/doc/mysql/en/Can_not_connect_to_server.html
Thank you. If that is what is happening then I agree that it is not PHP issue, so I am happy to go elsewhere for help. The only relevant suggestion is that it might help to impove the warning message and to put something in the php documentation to help people know where to look. Many people are having problems with this. I have seen the "MySQL Manual | A.2.2 Can't connect to [local] MySQL server" page. It is confusing, since the title says "[local]" yet the last item on the page that says to check the firewall says "to allow external access", which I interpreted to mean not-local access. I wish I knew what the disadvantage of pipes are. That is not a php issue, though; it is something that the MySQL documentation should clarify. Probably pipes work great if there is no need to access MySQL outside of the system it is installed in. If so, then it would help for the MySQL documentation to say so explicitely. It might say that, but I have not seen it said. I know that MySQL does poll the internet very, very often and if turning off it's use of the network eliminates access to the internet then that is one less thing to be concerned about. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
