*Resolved* Cannot telnet to MySQL port 3306
I cannot Telnet or connect via MySQL ODBC to the Kace DB.
i know what the default settings and passwords are. I know the user and database username.
I have a test Kace box that I can connect to just fine. Same ESX host same VLAN same switch and same copper backbone.
Any Ideas what could be causing this?
i know what the default settings and passwords are. I know the user and database username.
I have a test Kace box that I can connect to just fine. Same ESX host same VLAN same switch and same copper backbone.
Any Ideas what could be causing this?
2 Comments
[ + ] Show comments
-
this is enabled already. - kgeesaman 8 years ago
-
Have you restarted the appliance after making the change? - chucksteel 8 years ago
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
tekCTRL
8 years ago
You need to enable database access in Settings> Security Settings (highlighted in the screenshot below)
Comments:
-
Already enabled - kgeesaman 8 years ago
-
can you run nmap and see if port 3306/tcp is open? - tekCTRL 8 years ago
-
can you run nmap and see if port 3306/tcp is open? - tekCTRL 8 years ago
-
Starting Nmap 7.12 ( https://nmap.org ) at 2016-06-30 13:20 Eastern Daylight Time
Nmap scan report for 10.2.9.52
Host is up (0.00s latency).
PORT STATE SERVICE
3306/tcp closed mysql
Nmap done: 1 IP address (1 host up) scanned in 6.26 seconds
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
139/tcp open netbios-ssn
199/tcp open smux
443/tcp open https
445/tcp open microsoft-ds
8443/tcp open https-alt - kgeesaman 8 years ago
Posted by:
rockhead44
8 years ago
Have you verified that "Enable database access" is enabled under "Control Panel" and "Security Settings"
Comments:
-
Already enabled. thanks - kgeesaman 8 years ago
-
NOW your can access 3306 port?telnet 3306? - a83547 8 years ago
-
After this issue was resolved i can.
Not sure how your K1000 got into this state, but there were two copies of the MySQL configuration file on your K1000.
The second copy had the external DB access disabled and was taking precedence over the normal copy and was not being updated/changed when changes were made through the webUI. - kgeesaman 8 years ago
Posted by:
kgeesaman
8 years ago
Top Answer
An engineer was able to fix via tether.
Here is the response as to what happened.
Glad to hear it is now working.
Not sure how your K1000 got into this state, but there were two copies of the MySQL configuration file on your K1000.
The second copy had the external DB access disabled and was taking precedence over the normal copy and was not being updated/changed when changes were made through the webUI.
Here is the response as to what happened.
Glad to hear it is now working.
Not sure how your K1000 got into this state, but there were two copies of the MySQL configuration file on your K1000.
The second copy had the external DB access disabled and was taking precedence over the normal copy and was not being updated/changed when changes were made through the webUI.