0 pts.
 SQL Website
Hello again. We have an internal web server that is built using SQL Developer 2000. THis is on our DMZ on the firewall. we can not link to it from our internal network to transfer data to the sql tables. to test i opened all traffice between dmz and the internal network to test and no success. is it because it is the developer edition???

Software/Hardware used:
ASKED: December 29, 2004  12:23 PM
UPDATED: December 30, 2004  12:31 PM

Answer Wiki:
Stupid question.... Is the SQL Server instance communicating using Named Pipes only, or TCP/IP as well? On the firewall/router, you *should* only need to have TCP/1433 (someone please correct me if I have the port wrong, but I think that's right) open to/from the SQL box. Also, you should probably make sure that your routes are set up properly; if the internal network doesn't know how to get to the SQL box's subnet and vice versa, that could be the problem.
Last Wiki Answer Submitted:  December 30, 2004  7:31 am  by  Sonotsky   680 pts.
All Answer Wiki Contributors:  Sonotsky   680 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Melvin,

Could be several things.

I assume since the SQL server is in the DMZ, you have some type of 192.xxx.xxx.xxx IP scheme going on. If this is so, make sure your workstations can ping it. If they cant, a simple route add command to the workstation route table is neccesary.

Secondly, do the users have the correct rights to the server and/or database where the tables are stored? These rights are from you AD, not necessarily from rights to the SQL table. If the users do not have read/write access to the physical resource, they will not be able to update the tables.

 0 pts.

 

That should work. I would first check the network settings on you SQL server and verify first that you are using IP and your port is set for 1433. Not knowing how you are connecting I would setup an ODBC and verify connectivity that way. You can also try and telnet to 1433 so see if it repsonds. you can also do a netstat -a on the sql server to verify what ports it is listening on.

 0 pts.

 

thanks,
As an admin i tried to create an odbc connection to the sqlbox on the dmz and it times out. I can ping the sql box fine.
any other ideas and thanks for the help so far

 0 pts.