SQL Server should be in firewall exception list

  • Thread starter Thread starter Jon Davis
  • Start date Start date
J

Jon Davis

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
 
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" <[email protected]> a écrit dans le message de
%23p%[email protected]...
| 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.
 
Back
Top