sql server should in firewall exception list

Just an observation. I disabled all options in the firewall and added tcp port 1433 and still could not connect to my local copy of SQL Server 2005 Express (which had TCP/IP enabled). I turned off the firewall and it worked.
Microsoft should add SQL Server to the list of firewall exceptions.
Jon

I don't think that's a good idea http://www.symantec.com/avcenter/venc/data/w32.sqlexp.worm.html
Please tell me you will change the default port
"Jon Davis" wrote in message

Just an observation. I disabled all options in the firewall and added tcp port 1433 and still could not connect to my local copy of SQL Server 2005 Express (which had TCP/IP enabled). I turned off the firewall and it worked.
Microsoft should add SQL Server to the list of firewall exceptions.
Jon

The SQL worms were addressed in SQL2000 SP3/SP4.
As I said, I'm using SQL2005. And it's a service I require on the default port.
Jon
"Howard" wrote in message

I don't think that's a good idea http://www.symantec.com/avcenter/venc/data/w32.sqlexp.worm.html
Please tell me you will change the default port
"Jon Davis" wrote in message Just an observation. I disabled all options in the firewall and added tcp port 1433 and still could not connect to my local copy of SQL Server 2005 Express (which had TCP/IP enabled). I turned off the firewall and it worked.
Microsoft should add SQL Server to the list of firewall exceptions.
Jon

In Admin Tools, you can access the firewall admin console, which lets you create all the rules you want, both for incoming and outgoing connections. But you're right, when you install SQL2005 it should offer to open the port it uses. -- Pierre Szwarc Paris, France PGP key ID 0x75B5779B ------------------------------------------------ Multitasking: Reading in the bathroom ! ------------------------------------------------
"Jon Davis" a écrit dans le message de news: %23p%23N4VHgGHA.5096@TK2MSFTNGP02.phx.gbl... | Just an observation. I disabled all options in the firewall and added tcp | port 1433 and still could not connect to my local copy of SQL Server 2005 | Express (which had TCP/IP enabled). I turned off the firewall and it worked. | | Microsoft should add SQL Server to the list of firewall exceptions. | | Jon | |

I had no Problem's Whatsoever Installing the Express Edition of SQL Server 2005 on Beta 2, Just FYI.
"Jon Davis" wrote in message

Just an observation. I disabled all options in the firewall and added tcp port 1433 and still could not connect to my local copy of SQL Server 2005 Express (which had TCP/IP enabled). I turned off the firewall and it worked.
Microsoft should add SQL Server to the list of firewall exceptions.
Jon