|
|
Question : SQL Connectivity through a router/firewall, from DMZ to LAN
|
|
Hi,
I have two production web-servers in a dmz. I'm in the process of cut-over between them.
The database servers are on the internal LAN.
But I've been asked to set up a site for UAT by our users. But the webserver can't see the development database server - it can connect to the production database server though.
I'm using odbcping and telnet to try and verify connectivity.
The production database server is SQL 2000 on Windows 2000 as the default instance
The development database server is SQL 2000 on Windows 2003 as a named instance - SQL2000. This is on port 1199 (Looked up in Server Network Utility.)
The router/firewall is remoted managed by our ISP.
What ports and protocols do I need to have them open up so I can connect?
The books suggest that 1434 UDP and 1199 TCP. But I still can not connect ...
Suggestions please.
Regards David
I get results from odbcping and telnet on port 1433 to the production database server.
|
Answer : SQL Connectivity through a router/firewall, from DMZ to LAN
|
|
Hello,
whenever I ran into this type of problem is was always an unusual answer such as port 39 or something needed. Your best bet is to install the free Tiny firewall (renamed now but a google serach still find it). Load it on a SQL test server and run your application against it. The firewall will show what ports your application is opening and why. Very simply tool and very easy to install, run, stop, and uninstall once complete. No configuration needed as you are not blocking or allowing only logging.
It solved my problem every time.
Hope this helps
|
|
|
|
|