Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jon3k
Starting Member
49 Posts |
Posted - 2004-02-02 : 17:06:53
|
| I can connect to the sql service locally, but not remotely. This has happened on the last two machines I installed the sql service on. I've added a tcp/ip alias and set it to automatically determine the port number, but I still can't connect to the port. Even if I telnet localhost 1433, it won't connect. Any ideas whats going on? This machine is not a member of a domain, and the service is running as the local administrator account. |
|
|
jon3k
Starting Member
49 Posts |
Posted - 2004-02-02 : 18:02:04
|
| Think I found the problem ...From the Application Event Log:"You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp"Looks like SP3 will fix the problem. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-02-03 : 12:36:50
|
| Don't set the alias so that it automatically determines the port number. Put the port number in the alias.Tara |
 |
|
|
|
|
|