ISA Firewall client blocks connection to SQL Server

Dear Experts,

I lost myself serching for the cure to connect my internal user to SQL Server through ISA Firewall Client. I am using ISA 2000 on the server. The point is that user's machine has two NIC's. One has LAT address and the other one has other subnet address wher SQL resides. I can ping SQL server. I can browse shared folders on it. But I can not telnet port 1433. If I disable Firewall client, I can get SQL server (even port 1433). And my application is connected successfully. If I turn it back on I gives me error, saying SQL server is unavailable or access denied. I tried to set [appl_file_exe_name] Disable=0 so that Firewall does not deal with it at all. Still I get the same error. I tried to set [appl_file_exe_name] RemoteTcpPorts=1433. Still no success.

If you have any ideas, please share it
I appreciate your help very much.

Looking forward to hearing from you  
Terrible_macroAsked:
Who is Participating?
 
DarthModCommented:
PAQed with points refunded (250)

DarthMod
Community Support Moderator
0
 
Keith AlabasterEnterprise ArchitectCommented:
The isa client is sending all traffic, web and socks, to the ISA server. If you check your isa logs you will see the deny errors listed in the fw log. Create a rule on ISA allowing internal to internal comms for the sql traffic.
0
 
Terrible_macroAuthor Commented:
Guys,

Thanks, but I have alredy found solution. The problem was with understanding LAT and ISA. The point is that ISA client checks IP queries with LAT, received from ISA server. If it does not find IP it routes request to ISA server. In my case, I did not put local SQL server subnet to LAT. When user opens application to receive data from SQL server it makes request to IP address from other subnet. ISA client looks for this IP in LAT. It can not find it there so it transfers it to ISA server. ISA server processes the request as external, but it can not find the IP address (because no routing is set on the server: host unreachable). Then ISA server returns to client "connection failed". I added SQL server subnet to ISA LAT so that requests to SQL server ip address avoid being sent to ISA server.

Again,
Sorry for bothering you guys.
Hope I can share my solution with other people.
0
 
Keith AlabasterEnterprise ArchitectCommented:
It is a requirement for the LAT on the ISA to have ALL addresses that it (ISA server) can access through its internal interface.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.