I meant is sqlbrowser enabled through the firewall.

--
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

[quoted text, click to view]

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..

[quoted text, click to view]

Hi Michael,

As Grumpy has mentioned, generally 1433 port is enough for connecting to
SQL server database engine. Also, for 2005, you can also try opening the
1434 UDP port since it will be used for establishing linked connection from
other applications. See the following article which describes the
"Connecting SQL Server over internet....":

Connecting to SQL Server over the Internet
http://msdn2.microsoft.com/en-us/library/ms175483.aspx

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------
| From: "grumpy" <dtREMOVE2k@blueTHISyonder.co.uk>
| Newsgroups: microsoft.public.sqlserver.connect
| References: <171212F6-D91C-4A02-AB42-23BEC0C325EB@microsoft.com>
<#imE4XEJGHA.3904@TK2MSFTNGP10.phx.gbl>
<601836B2-038B-47C1-B1D5-99230963883A@microsoft.com>
| Subject: Re: Ports to open in Windows Firewall for SQL Server 2005
| Lines: 71
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <x%dDf.11677$wl.6669@text.news.blueyonder.co.uk>
| Date: Mon, 30 Jan 2006 01:31:09 GMT
| NNTP-Posting-Host: 82.42.42.142
| X-Complaints-To: abuse@blueyonder.co.uk
| X-Trace: text.news.blueyonder.co.uk 1138584669 82.42.42.142 (Mon, 30 Jan
2006 01:31:09 GMT)
| NNTP-Posting-Date: Mon, 30 Jan 2006 01:31:09 GMT
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!newsfe
ed01.sul.t-online.de!t-online.de!solnet.ch!solnet.ch!newsfeed.freenet.de!bor
der2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!p
e2.news.blueyonder.co.uk!blueyonder!pe1.news.blueyonder.co.uk!blueyonder!tex
t.news.blueyonder.co.uk!53ab2750!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46765
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| 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..
|
[quoted text, click to view]
| > 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
| >
| >
[quoted text, click to view]
| >
| >> 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
| >>
[quoted text, click to view]
| >> > 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
| >>
| >>
| >>
|
|
|

That's the trick! Enable the SQL Browser and Port 1433 in the Windows
Firewall and you get both connectivity and the ability to remotely
administer. Thanks!


--
Michael Hockstein


[quoted text, click to view]