Bug #65221 I cannot connect to MySQL with shared-memory via IP address
Submitted: 7 May 2012 8:27 Modified: 7 May 2012 11:36
Reporter: bingo meng Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.5.21.0 OS:Microsoft Windows (xp sp2)
Assigned to: CPU Architecture:Any
Tags: IP address, remote, shared-memory

[7 May 2012 8:27] bingo meng
Description:
Server: my.cnf / my.ini:

[mysqld]

# The TCP/IP Port the MySQL Server will listen on
#port=3306

skip-networking 
shared-memory 
shared-memory-base-name = MyName

...

Client:

 "mysql -h localhost -u root -p --procotol=memory --shared-memory-base-name=MyName"

  It successfully connect to MySQL with Memory procotol. I can use database and select anything.

But, when I use the following command line with IP address instead of localhost, it failed.

"mysql -h 127.0.0.1 -u root -p --procotol=memory --shared-memory-base-name=MyName"
"mysql -h 192.168.1.149 -u root -p --procotol=memory --shared-memory-base-name=MyName"

The root user had been granted all privileges on any remote client with '%'.
The localhost had been mapped to the IP address in the host file.
I tried to uncomment the "skip-networking", but It was invariable.

Can anyone help me to solve the problem?
Does the shared-memory connection only work for localhost? not for IP address or remote client.

How to repeat:
ERROR 2047(HY000): Wrong or unknown protocol
[7 May 2012 11:36] MySQL Verification Team
Thank you for the bug report. You are using skip-networking  which disables TCP/IP connections.