Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL 2KSP4, Win 2K3SP1, NT domain no TCP 1

Status
Not open for further replies.

hyperiest

Technical User
Dec 26, 2002
35
US
Ok, this is my first post on this site in a long time. Please excuse me if I am asking a question that has already been asked and answered a dozen times on this site. I have been beating my head against the keyboard for so long now that I no longer have time to browse the thousands of posts on this site. That said...

I am running SQL Server 2000 SP4 (Enterprise Ed) on Windows Server 2003 SP1 (Enterprise Ed) on a Windows NT domain. I have installed SQL Server according to the default settings on setup, including setting TCP/IP on port 1433 (it is a closed DoD network, so I'm not too worried about Blaster). The problem is that I cannot get the server to listen for inbound TCP requests on port 1433, no matter what I try.

I have installed all of the applicable security patches and re-checked to make sure that none of them inadvertently blocked TCP traffic on 1433 (none of them do). I have checked the Server and Client network utilities to ensure that 1433 is the port set for TCP and it is. I have ensured that the box "Hide Server" is not checked. I have checked the properties of the SQL Server instance to make sure that it showed 1433 as the port for TCP, just like the Server and Client network utilities do. I have checked the SuperSocketNetLib for the SQL Server instance in the Windows Registry and TCP is set on port 1433.

But when I check the SQL Server logs, I get only that the Server is listening on Shared Memory and Named Pipes (no TCP!!). I also get no error message that SQL Server failed to bind TCP on port 1433. Also, when I run netstat -an in cmd, it clearly shows that the system is not listening on port 1433.

Thinking that perhaps it was a conflict with the NT domain and the fact that Windows 2003 is looking for the Active Directory for inheritable policies, I have tried removing the system from the domain, but with the same results. I have ensured that a local policy set by default (or conflicting because it is not defined) in Windows 2003 has not interfered.

I have scoured the net looking for an answer, but everything I find tells of people having problems with WinXP SP2 and firewalls, SQL Server 2000 pre-SP3a, or SQL Server 2000 Standard Edition, but nothing for my configuration.

Any help anyone could lend would be greatly appreciated. I am truly at my wit's end. Thank you.

-Captain D


Captain_D
"Taking Care of America's Sons and Daughters"
 
First SQL 2000 Standard or Enterprise are basically the same thing. Anything that you found for SQL Standard also applies.

Do you see any messages in the Event Log (I didn't see that in your doc)?

If you do the netstat is something else using port 1433?

If there any funky DoD software installed which is preventing SQL from listening?

Have you checked the Windows firewall? SP1 turns the firewall on and port 1433 is blocked by default.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
mrdenny, thanks for the prompt response.

When I ran netstat, nothing else was using 1433.

I am one of the SysAdmins here and am completely confident that we have no DoD software installed that is preventing listening on 1433 (we have Win2K/SQL2K machines that listen on 1433 just fine).

I have the firewall from SP1 disabled in the registry and by policy and on the off-chance that those two measures didn't work, I named SQL server port 1433 as an exception in the firewall settings anyway.

I checked the event log, but found no error messages. I did find an entry where it states that I am running a version of SQL Server 2000 or MSDE that has problems with Win2003 and that TCP/UDP has been disabled. But I am running SP4, so that doesn't make much sense.

Captain_D
"Taking Care of America's Sons and Daughters"
 
I'd reinstall SP4. Sounds like it didn't install correctly.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Thanx for the advice, mrdenny. I reinstalled SP4 and it is working just fine now.

Captain_D
"Taking Care of America's Sons and Daughters"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top