How to securely connect Windows NT Web server to SQL Server |
 |
By Robyn Lorusso, Editor
04 Oct 2004 | ITKnowledge Exchange |
 |


|
The following is the ITKnowledge Exchange Tip of the Week for Oct. 4, 2004.
Question
"rmartinez78" of Fastrac 24/7 Corp. writes:
I've got an NT Web server in our DMZ that can't connect to an internal SQL Server 7.0 database in Windows 2000. ODBC returns an access denied/can't find server message. When I put the Web server inside our net, ODBC works fine. Other servers in DMZ can connect to the database. What is going on?
Responses
"Howard2nd" writes: Lies, damn lies, and NetBios that won't die. This is about permissions and the lack thereof. When your NT box is inside the firewall, it can use NetBios to resolve the server name. When it is outside the firewall it cannot and should not. ODBC uses the Name of the server to connect.
A best practice would be to use the TCP/IP address instead of the Name, then ODBC won't have to resolve the adress and there will be no NetBios traffic. I quit using names two years ago, and have no regrets. Using the TCP/IP address works in drive mappings, printer shares, ODBC and eliminates the name resolution hangup.
"andy123" writes: Try the user company number.
Install the SQL Client Network tools from SQL CD onto the NT server. Create an alias (if you want a name) linked to an IP and port. Make sure you use TCP/IP.
For additional security you may want to change the listening port for SQL on the server and client side from the default. If you need any help, please reply to the forum.
Start your own discussion
Do you you have a Windows security dilemma that needs quick attention? Talk about it in ITKE.
About the ITKnowledge Exchange
ITKnowledge Exchange is a place where IT pros can share ideas, expertise and get answers to their technical and strategic questions. It provides direct access between groups or individuals who are grappling with similar IT issues in a safe and seamless environment. Click to start participating today or go to the Tip of the Week archives.
');
// -->
|
 |
|
 |