Azuull
10-28-2014, 08:27 PM
Okay, I haven't seen this issue with eqitems.exe.
Server is Debian 7.7.0 (virtual machine, same physical machine.) - 10.0.0.32
I am running Windows XP SP3 (for the tools, virtual machine.) - 10.0.0.34
Using peqbeta_* from September as the October release is missing tables.
I can successfully log into the server with EverQuest.
MySQL Workbench connects fine from LAN machine (another physical machine).
Fixed db.ini to reflect my requirements.
Registered all OCXs with no issue.
Installed MySQL Connector ODBC 3.51.2 32bit with no issue.
MySQL TEST: MySQL Connection SUCCESS.
I've tried the root user and the 'eq' user, with hostname and IP address (along with default 3306 port). 'eqitems.exe' just refuses to connect.
Firewall is disabled (no anti-virus on XP machine).
Within /etc/mysql/my.cnf -
#bind_address is commented out (tried from a Stack Overflow post about making MySQL on Debian available to remote connections.)
No bueno. :(
Any help would be greatly appreciated.
Server is Debian 7.7.0 (virtual machine, same physical machine.) - 10.0.0.32
I am running Windows XP SP3 (for the tools, virtual machine.) - 10.0.0.34
Using peqbeta_* from September as the October release is missing tables.
I can successfully log into the server with EverQuest.
MySQL Workbench connects fine from LAN machine (another physical machine).
Fixed db.ini to reflect my requirements.
Registered all OCXs with no issue.
Installed MySQL Connector ODBC 3.51.2 32bit with no issue.
MySQL TEST: MySQL Connection SUCCESS.
I've tried the root user and the 'eq' user, with hostname and IP address (along with default 3306 port). 'eqitems.exe' just refuses to connect.
Firewall is disabled (no anti-virus on XP machine).
Within /etc/mysql/my.cnf -
#bind_address is commented out (tried from a Stack Overflow post about making MySQL on Debian available to remote connections.)
No bueno. :(
Any help would be greatly appreciated.