Cannot connect to SQL Server after upgrading from Server 2003 to Server 2008
I upgraded my Windows Server 2003 x64 to Windows Server 2008 R2 x64, and I noticed that I cannot connect to SQL Server (from within the LAN) which is running on the computer. I ran the OpenSqlServerPort.bat script specified on http://support.microsoft.com/kb/968872/en-us, however the software Firewall is still somehow blocking access from within my LAN. I installed Microsoft's Port Query tool, and it verifies that the port is being FILTERED: TCP port 1433 (ms-sql-s service): FILTERED portqry.exe -n 192.168.1.15 -e 1433 -p TCP exits with return code 0x00000002. I can also see in the EventLog it's being blocked: The Windows Filtering Platform has blocked a packet. Filter Information: Filter Run-Time ID: 74459 Layer Name: Transport Layer Run-Time ID: 12 I wish there were a way to lookup the filter rule which is causing the block. I did not find anything using the run-time ID on Google. Anyone have any ideas?
July 20th, 2010 7:33am

Hi, As this issue is related to SQL Server, I suggest discussing it in our SQL Server forum. They should be the best resource to troubleshoot this issue. http://social.msdn.microsoft.com/Forums/en/category/sqlserver/ Tim Quan TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2010 5:27am

As this issue is related to SQL Server, I suggest discussing it in our SQL Server forum. They should be the best resource to troubleshoot this issue. http://social.msdn.microsoft.com/Forums/en/category/sqlserver/ Yes, I also entered a post there, on the SQL Server Setup & Upgrade forum. However, I can connect to SQL Server fine from within the Windows Server 2008 machine. If I try from another computer on the LAN, I can see from the Security Audit in the Eventlog, that Windows Server 2008 is blocking the connection. That's why I believe it's an issue with Windows Server 2008. Something else is blocking it even though I have a rule which allows port 1433.
July 21st, 2010 6:26am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics