Best
that I can tell, the database server know/has the route out.
How
can I see the returned connection to the client?? In the log, I only see the
initiating connection. Is there another log that shows all transactions even if
they fit in the window of the initial TCP connection?
This
is a plain connection, no SR.
Thanks!
Title: SQLnet over NAT issue..Does your DB server have a valid route back to the initiating client? That's the most common problem; if that's not the problem, check the logs on the FW to see if the DB server is trying to create a back connection to the client (you must be logging on your "cleanup" drop rule to see this). If you are using SecuRemote to connect in, check out www.phoneboy.com/fw1/faq/0308.html (states that SR build must be later than 4005 for SQLNet v2 connections to work)Hope that's a start...Dan Hitchcock
MCSE, CCNA
Network Engineer
HomeStreet Bank
206.389.4467
[EMAIL PROTECTED]-----Original Message-----
From: Joe Delsol [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 09, 2000 3:20 PM
To: FW-1 List (E-mail)
Subject: [FW1] SQLnet over NAT issue..
Our database is on a non-routable address and we are allowing connections from the outside to it via the SQLnet protocol.
The clients connection is received by the server, but the client claims it was not able to establish the connection.
Any ideas?
