September 21, 2006 at 7:58 am
I set up a new server which seems to work fine locally, but cannot be accessed by any remote computers on the network. I've disabled all firewalls and spyware software. When I check the server logs, there is no indication that the server is listening to either a port or named pipes, just shared memory. I've used the server and client utilities on the appropriate machines and all seems correct. I've read most of the articles relating to connection problems, tried all the solutions, nothing seems to explain or fix the problem. What dumb thing am I overlooking?
September 21, 2006 at 12:06 pm
Greetings,
1. What version of sql server is it and which servicepack do you have applied to it. SP3a or higher is required for sql server 2000 on a windows 2003 OS before it can be accessed via TCP/IP.
2.Have you checked your connectionstring. Have you tried to use the ip instead of the name to rule out nameconversions.
3.Are you using sql authentication or windows authentication?
September 21, 2006 at 1:50 pm
If this is SQL 2005, you will need to go into the SAC tool and enable remote connections
A.J.
DBA with an attitude
September 21, 2006 at 2:36 pm
The dumb thing I was overlooking was that I had to re-install the server from scratch and never upgraded to Service pack 3a. As soon as I did, the problem went away. Thanks to Jo Pattyn for the great tip! Problem solved.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply