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

Tech-Archive recommends: Speed Up your PC by fixing your registry

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: SQL2005: Cannot connect error 11001
    ... The famous Windows Firewall (turned on my Server from which I'm trying to ... Exception Details: System.Data.SqlClient.SqlException: Login failed for user ... Try starting the SQL Server ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • Re: Failed connections to remote 2k SQL Server
    ... It could be a port issue - that would be my first guess. ... you need to open up UDP 1434 for SQL Server name ... TCP Ports Needed for Communication to SQL Server ... >server's network utility, and client network utility, and ensured that they ...
    (microsoft.public.sqlserver.setup)
  • Re: Connecting to an instance in a cluster
    ... Each virtual server has its own IP address so you can reuse port numbers between instances. ... Microsoft SQL Server MVP ... "Geoff N. Hiten" wrote: ...
    (microsoft.public.sqlserver.clustering)
  • RE: Some technical errors
    ... If the SMTP server is not running on port 25 TCP it is not a public ... Manager - Computer Assurance Services BDO Chartered Accountants & ...
    (Security-Basics)
  • Re: hack using xp_cmdshell
    ... I'm no security expert, so please forgive if I'm not using the right ... install SQL Server in Windows Only mode and then Switch down to Mixed mode, ... Is the SQL Server instance a default instance? ... > port 65300, which has never been open on my firewall. ...
    (microsoft.public.sqlserver.server)