April 15, 2003 at 7:50 am
Run server network utility --> highlight TCP/IP network library --> click EDIT button --> verify "Proxy Address" is empty or not. I think a Proxy Address is set to the External IP address of the Proxy server. If it does, remove the proxy address, restart SQL Server and you will be able to connect in with TCP/IP.
I think your client has setup proxy server to prevent unauthorized users from connecting to their private network and they may not agree to let you remove the proxy server address from SQL Server network utility as mentioned above. You have to verify with them what kind of proxy server they are running and go from there.
April 15, 2003 at 11:47 pm
We had the identical problem at our place and it was highly intermittent. In our case it turned out that the sql server (backend to a web server) had two default routes (0.0.0.0) in the routing table (c>route...). We had to clear the routing table.
Bill
April 16, 2003 at 11:03 am
Thank You. That did it.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply