August 25, 2003 at 9:01 am
Prior to the net admins installing the patch to 'sure' up the loop hole for the virus, I was able to connect to my server from a workstation via TCP/IP. Now I can only connect via named pipes. I am trying to research what exactly the patch does. I know for sure I was connecting prior to that patch. Any ideas?
August 25, 2003 at 9:15 am
That shouldn't be the problem. We have been patched and all of my servers (including a few that are TCPIP only) still work.
I'd check that something else didn't get changed.
Steve Jones
August 25, 2003 at 9:25 am
Even all my servers have been patched running NT 4.0 Server, Windows 2000 Server with MS03-026 few weeks back. I am still able to connect to my databases (SQL Server 6.5 / 7.0 / 2000) same as earlier. Never heard of any issues so far.
.
August 25, 2003 at 9:35 am
Are any of your servers running the base line version of SQL 2000? NO sps? and Win 2000 sp2?
August 25, 2003 at 9:53 am
Yes. One of the Test Server which I have released last week, had Windows 2000 Server SP3, SQL Server 2000 Baseline. The reason we have not installed SPs on this one is we borrowed this server only for short duration & did not have time to install SPs.
I did connect to this last week after installing the patch. Everything was fine till releasing.
.
August 25, 2003 at 2:12 pm
We did the patch on two SQL servers a couple of weeks ago with no issues for TCP/IP. Both servers are 2000/SP4 and SQL/SP3.
Although one thing to note is that the security patch, MS02-061, is part of the SP3 for SQL. If you read this document from MS, it says that you should be running the latest SP for SQL:
http://support.microsoft.com/default.aspx?scid=kb;en-us;813440
All the best,
Dale
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
August 25, 2003 at 2:20 pm
I'm sorry. That was the update for the Slammer Worm. View this document for the Blaster Worm update, MS03-026:
http://www.microsoft.com/security/incident/blast.asp
This is an excellent article on the cumulative security patch for SQL. Should give you some info about what is happening with named pipes:
http://support.microsoft.com/default.aspx?scid=kb;en-us;815495
All the best,
Dale
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
August 25, 2003 at 2:26 pm
It's possible that an Admin modified TCP/IP Filtering after installing the patch:
http://support.microsoft.com/?id=309798
All the best,
Dale
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
August 26, 2003 at 8:02 am
One other thing to check...did the admin change the port SQL Server is listening on?
On the server, open Enterprise Manager, right click on the server, select Properties, select General tab, click on Network Connections..., in the right window pane of the popup, select TCP/IP, then click on Properties. Check what the port number is.
The patch doesn't change the port number, but the sysadmin may have decided to make the change and 'forgotten' to tell anyone.
Also, make sure TCP port 1433 hasn't been blocked at the firewall.
-SQLBill
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply