| Bug #14864 | cannot connect through cisco vpn channel (client sw routes wrongly) | ||
|---|---|---|---|
| Submitted: | 11 Nov 2005 14:40 | Modified: | 28 May 2013 13:02 |
| Reporter: | thierry jacobson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S1 (Critical) |
| Version: | 4.1 | OS: | Any (client:win / server: Linux) |
| Assigned to: | CPU Architecture: | Any | |
[17 Nov 2005 0:56]
thierry jacobson
hi, i changed the cisco vpn client. (i made un-install and installed a NEW version : 4.7.00.0533) same problem. still critical ... somebody interested ?
[21 Nov 2005 18:49]
Valeriy Kravchuk
Thank you for a problem report. You choosed a wrong category for it, so it may stay Open for ages... Let's start with simple check. What port your server is listening to? 3306? Please, try to connect to your server with telnet to that port: telnet <your_server> <your_port> You should get something similar to: 7 5.0.15-nt... MySQL server version and some "garbage"... Please, try, and inform about the results.
[24 Nov 2005 2:34]
thierry jacobson
thank you for reply.
telnet (IP address) 3306 gives :
4.1.12)mCDifCZ{,☻{{uX<aS\UvqU
and then (directly) a connection loss (telnet connection)
(i can ping to the server without problem)
all software use the cisco tunnel (seen by ethereal trace)
only the mysql softs continue to use the 'hardware card' instead of the 'pseudo card' created by the cisco vpn client
very strange !
regards
[24 Nov 2005 2:40]
thierry jacobson
if this can help : MySQL administrator and query browser both give error 2003, can't connect on server '192.168.2.19' (10061) and 'unknown error' when the 'ping' button is tried
[24 Nov 2005 17:53]
Valeriy Kravchuk
OK, so connection to host with some (VPN) IP exists (is it 192.168.2.19?), and MySQL is listening on port 3306 waiting for your data. What host name are you connecting to in QB or Administrator? Are you sure it's name is resolved to the same (VPN) IP address. Have you try to set the VPN IP address directly as a MySQL host? And, finally, if it is really the same address, are you sure that you have the appropriate permissions in MySQL server to connect from that IP-address?
[25 Dec 2005 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[28 May 2013 13:02]
Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.
Description: hi, the problem: cannot connect through cisco vpn channel the configuration: - client : win xp2, mysql admin 1.0.21, mysql querybrowser 1.1.13, odbc 3.51, cisco vpn client 4.0.2(D) zone alarm 6.0.667 - server : Linux fedora core FC4, mysql server 4.x (came standard with fc4) best regards t. jacobson How to repeat: all those softs use the 'normal' network interface of the client and not the vpn one, also the routing table shows to use the vpn channel for that network. (as seen from ethereal) ping, vnc, ftp, ... work all correctly with the vpn tunnel strange think is that odbc (in control panel) replied positively to test the connectivity but failed within ms access 2003 there are NO filters from the router (vpn gateway) for the vpn channel the packets are wrongly routed from my pc allready i started the sql softs after the vpn channel was tested active (ping -t) this failure is permanent.