December 2, 2008 at 7:42 pm
i'm currently running my sql server 2000 in windows server 2003 and i'm unable to bind my sql server 2000 to my IP.
my sql server 2000 is currently at SQL server 2000 service pack 4.
i had enable named pipe and TCP/IP in Server Network Utility. port for TCP/IP is set to 1433.
enabled RPC in Enterprise manager.
my computer is not under firewall
i tried to do a netstat and this is what i get.
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 1508
did a crosscheck from task manasger
Image Name PID
sqlservr.exe 1508
had been stuck with this for many hours and still unable to find a solution on how to get it to work. although i can set the winsock IP address and port to what i want but the Foreign Address still remains at 0.0.0.0.
hope someone with the knowledge of this can help. thanks a million
December 2, 2008 at 8:28 pm
Does anything show in the SQL Server error log?
December 2, 2008 at 8:56 pm
err.. i tink i missed out on some stuff..
anyway, my server 2 ip. 1 which is a static ip and another which is a public ip.
if ppl are to connect to my db they are suppose to go thru my public ip and the public ip itself will link over to my static ip.
however now it can't connect thru the public, i can connect it thru the static ip and local host onli.
telnet to my static ip possible but not to the public ip.
December 2, 2008 at 9:02 pm
In the SQL Server log what does it show as IP's, Ports and Protocols that SQL is listening on?
0.0.0.0 in the netstat generally means that it is listening on all IP addresses associated with the machine.
Do you have multiple IP's on the server and just want to bind to a particular one?
December 2, 2008 at 10:07 pm
in the server log its shows that its listening to my static IP as well as 127.0.0.1. both to port 1433.
SQL server listening on xxx.xxx.xxx.xxx: 1433.
SQL server listening on 127.0.0.1: 1433.
SQL server listening on TCP, Shared Memory, Named Pipes.
how can i set it to a particular ip?
December 3, 2008 at 5:12 am
So you have a public facing IP address (out in a DMZ for example), would this be through a NAT or via a switch that routes traffic from the public facing IP into your IP address that sits on the server?
If you have this public IP and it redirects to a local I'm not sure what problem you are having.
Your indications are that there are only two IPs that SQL is listening on, the localhost IP, and the IP out on the network. Unless you would only be connecting on the local machine I'm not sure why you would need a different configuration.
Either way, I am not aware can force SQL 2000 to listen on anything but all IP addresses (this is something that you can do on 2005, 2008). You could put a firewall rule in place on the server to prevent connections to SQL on that IP and Port, which would prevent connections.
December 3, 2008 at 7:35 pm
thnx for the help..
its my administrator that forgot to open the port for mi at firewall.. craps...
sorry for all the trouble.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply