Firewall: Error sending to the socket, server is not responding.
Hi all,
I'm trying to connect AIX machine to NT DB2 Database through JDBC with a firewall. I'm using the standard port 6789 in JDBC Applet Server in NT DB2. But I've gotten the following message:
COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0614E Error sending to the socket, server is not responding. SQLSTATE=08S01
The connection chain I'm using for AIX side is:
jdbc:db2://192.168.3.4:6789/DATABASE
I've configured the firewal to allow the port 6789 to be used, and also the other port 51544 (it's for remote administration, I think). I've also checked that wires and other stuff is working fine, but stil I cannot connect to the Database.
I don't know if there's something missing on the firewall configuration. Before, everything was working without the firewall.
Any help will be apreciated, THanks.
Rodrigo, SPAIN
[904 byte] By [
vissi] at [2007-9-26 4:28:35]
One possibility is that the firewall configuration is setup to require a specific clien-side port. Normally these are emphemeral ports (they come and go) and the port numbers cannot be predicted.
Make sure that the fire wall rules allow any port on the client IP address (or any IP address if it's a many-client system) can talk to the required ports and IP address combinations on the DB server.
Chuck
It looks like no port problem is happening, because we freed all the ports just to see if client tried to use some of them without our knowing. But it was still the same.
We were thinking about routing issues, but we were able to ping from client to server, and ports 6789 and 51544 were open as well. Maybe JDBC Client Driver is looking for an different IP address than 192.168.3.4. We know the firewall doesn't receive any query from JDBC Client, and that's very strange because if you see the routing tables in AIX machine, the default route is the firewall. Of course, there's not any other static defined route for the server (192.168.3.4), so it's supposed that default route is going to be used. But it's not.
We also restarted client machine from scratch but nothing. Maybe this problem happens because there's something wrong in AIX networking settings.
Rodrigo
vissi at 2007-6-29 17:39:10 >
Hi all,
We know more stuff about this issue. We were able to pass through the firewall in order to make the database connection properly, but we still had the same behaviour. We realized that some of the packets (NetBIOS) were dropped out by the firewall, but we fixed it and still the same. Right know, all the packets are delivered thru the 6789 DB2 port using the firewall, but still cannot establish the connection, same error message.
Any idea? Thanks.
Rodrigo
vissi at 2007-6-29 17:39:10 >
