August 18, 2004 at 7:09 am
Microsoft has issued XP Service Pack 2. It is affecting 50 known products and one of them is SQL Server.
The issue is that the service pack turns on the built-in firewall. This firewall is capable of blocking incoming and/or outgoing traffic by ports.
Can you guess what two of the blocked ports are? Did you guess 1433 and 1434? Yep. Microsoft blocks the default ports used for their own product.
Check the following link (MS Knowledgebase Article) for more information.
http://support.microsoft.com/default.aspx?kbid=842242
-SQLBill
August 18, 2004 at 9:33 pm
The security community has basically (finally) adopted deny all by default as a best practice. Quite a few were screaming the firewall deny all to start with, and the user being required to open up the required ports. BTW, you essentially do the same thing with products like ZoneAlarm and the like, so this is a common practice with personal firewalls.
K. Brian Kelley
@kbriankelley
August 19, 2004 at 7:31 am
Good point Brian. My main reason for the post is to let everyone know about this issue with XP SP2. On another site I use, a poster wanted help with connecting to SQL Server from their XP box and they had applied SP 2. That's when I found out about the port blocking. I figured post it and it might help others who are needing to upgrade their XP.
MS's web site makes it look like they didn't do DENY ALL, since they list only 50 applications that don't work. But it might be that those are the only ones they know of at this time.
-sQLBill
August 19, 2004 at 7:34 am
Those are the major ones people are screaming about. I think the general consensus is the XP firewall is a good step in the right direction, but grab another one and turn XP's off. It's not as feature-rich and user-friendly as the ones which are commercial but free to home users.
K. Brian Kelley
@kbriankelley
August 19, 2004 at 9:17 am
Just to toss in another 2 cents, if anyone is using an XP machine as a server running MSDE (some of my clients do it in a Novell environment), they need to be aware that SP2 also disables the network protocols. They need to turn them back on using the svrnetcn.exe utility to enable TCP/IP and named pipes, if applicable.
Don
September 1, 2004 at 9:29 pm
Every time I try to install SQL 2000 Personal Edition on my WinXP (SP2) box, it fails when trying to start up and configure the server. Of course, it then removes all the files and I get nothing in the ERRORLOG. Here are the last few lines of the log:
2004-09-01 21:48:18.56 spid4 Starting up database 'master'.
2004-09-01 21:48:18.85 spid4 Server name is 'SIZZLE'.
2004-09-01 21:48:18.85 spid5 Starting up database 'model'.
2004-09-01 21:48:18.85 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-09-01 21:48:18.85 spid4 Skipping startup of clean database id 4
2004-09-01 21:48:18.85 spid4 Skipping startup of clean database id 5
2004-09-01 21:48:18.85 spid4 Skipping startup of clean database id 6
2004-09-01 21:48:18.92 server SQL server listening on Shared Memory, Named Pipes.
2004-09-01 21:48:18.92 server SQL Server is ready for client connections
2004-09-01 21:48:19.00 spid5 Clearing tempdb database.
2004-09-01 21:48:19.50 spid5 Starting up database 'tempdb'.
2004-09-01 21:48:19.57 spid4 Recovery complete.
2004-09-01 21:48:19.60 spid4 Warning: override, autoexec procedures skipped.
2004-09-01 21:48:28.75 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager.
I've been hunting on the web, and it seems that the Windows Firewall in SP2 has been the cause of many problems. So I turned it off. Same problems. I've tried setting up UDP and TCP ports, still had problems.
I've been to URLs like:
I've added TCP Port 135 and UDP Ports 1433 amd 1434 to the Firewall exceptions. I've tried adding Port 445 to the Firewall -- it tells me "...(SMB over TCP) already enabled".
Many of the articles say to install SQL SP3a. But I need an instance of SQL Server to do that. Other articles say to look for the ports SQL Server is communicating on -- same issue; I dont' have an instance installed. I'm mad ... and tired of looking at hundreds of "helpful" articles.
I need some direction / help / support. Anyone else had this headache and figured out the solution?
October 5, 2004 at 1:08 pm
Not sure how applicable this is but here is a scenario I faced today and in searching for other information that is out there about it, I found this website.I am in a training class that required us to create a Connection Pool in Weblogic 8.1 SP 2. The OS we have is XP with SP2 as well. When trying to establish a connection to the SQL Server, on the same machine, we were getting Connection Refused socket connection error.
After turning off the firewall completely we still were not able to connect. Reading about, found on BEA site a message to try and telnet to the port you are trying to connect to, even that was refused. So, with the firewall completely turned off, we couldn't establish a connection. As the class was losing time and these are just imaged training laptops, we removed WinXP SP2 and the connection was established without changing anything else.
I am not sure why the firewall would be blocking any ports if it is completely turned off and now that it is no longer on the machine, I can't play around with opening up ports etc. Just wanted to throw this out there for anyone trying to connect to SQL Server using Connection Pools on Weblogic.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply