Re: Ports to open in Windows Firewall for SQL Server 2005

Hi there michael,
If your connecting fine to the database and it accepts data exchange,
perhaps you might look at the database permissions. Rather than any more
ports.

Opening 1433 within the firewall as far as im aware, is all you need for
admin.

Give the test account full sysadmin rights, and try that.

regards..

"michael" <howlinghound@xxxxxxxxxxxxx> wrote in message
news:601836B2-038B-47C1-B1D5-99230963883A@xxxxxxxxxxxxxxxx
> After a little searching, I thought that simple enabling port 1433 on the
> server machine's fire wall would do the trick. It does allow connection to
> the server for data exchange but it does not allow remote administration
> via
> the SQL Server Management Studio. What additional port need to be opened
> to
> allow this?
>
> --
> Michael Hockstein
>
>
> "Roger Wolter[MSFT]" wrote:
>
>> Did you also enable and start the sqlbrowser service?
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>>
>> "michael" <howlinghound@xxxxxxxxxxxxx> wrote in message
>> news:171212F6-D91C-4A02-AB42-23BEC0C325EB@xxxxxxxxxxxxxxxx
>> > I'm running the Develpers version of SQL Server 2005 on my developer
>> > machine.
>> > I want to test an application from another machine but can neither log
>> > on
>> > nor
>> > use the SQL Server Management Studio from the remote machine unless I
>> > turn
>> > off the Windows Firewall on the development machine. (I made sure to
>> > enable
>> > remote connections via the Surface Configuration Tool too).
>> >
>> > Though I seem to have the correct services listed in the "Exclusions"
>> > of
>> > the
>> > Windows Firewall, I think that I should probably explicitly open the
>> > ports
>> > that SQL Server and the Management Studio use. What are the correct
>> > ports
>> > or
>> > is there a better way to work through the Windows Firewall. (This
>> > problem
>> > should only exist in my development environment because I would not use
>> > the
>> > Windows Firewall in a production setting on the Server)
>> >
>> >
>> > --
>> > Michael Hockstein
>>
>>
>>


.

Relevant Pages

  • Re: SQL Server Specific Windows Firewall Exception
    ... if I've gone into the Surface Area Configuration and enabled remote ... Windows Firewall" articles than I would like. ... several policies to open different ports and/or point at different EXE's ... SQL Server 2005 so that we don't have to add a number of different program ...
    (microsoft.public.sqlserver.connect)
  • Re: Windows XP Pro Sp2 cannot connnect to SQL Server 2005
    ... Based on the error message, it sounds like SQL2005 didn't set itself up to ... I have no problem connecting with local machine to ... Windows Firewall exception for port 445, set alias for SQL Server ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP Pro Sp2 cannot connnect to SQL Server 2005
    ... Based on the error message, it sounds like SQL2005 didn't set itself up to ... I have no problem connecting with local machine to ... Windows Firewall exception for port 445, set alias for SQL Server ...
    (microsoft.public.windowsxp.general)
  • Re: How to connect a workstation to SQL Server 2005 thru ODBC?
    ... and open the port in the Windows XP ... Welcome to the Getting Started with the Database Engine tutorial. ... Connecting to the Database Engine ... Either SQL Server Management Studio or Management Studio Express. ...
    (microsoft.public.sqlserver.connect)
  • Re: Cannot connect a remote sql server
    ... I too have written quite a bit about connecting. ... Hitchhiker's Guide to Visual Studio and SQL Server ... such as the server's firewall, SQL Server's remote connection setting, ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.adonet)
Loading