Enterprise Manager Connection

I need to open up my firewall so that a client can access my SQL server
using the Enterprise Manager. I opened up port 1433, but apparently
that's just the data connection port, not for management.
Where can I get a list of all SQL related ports?
Thanks!
--DaveINF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/defaul...2&Product=sql2k
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a959ad45c280f7a989782@.news-40.giganews.com...
> I need to open up my firewall so that a client can access my SQL server
> using the Enterprise Manager. I opened up port 1433, but apparently
> that's just the data connection port, not for management.
> Where can I get a list of all SQL related ports?
> Thanks!
> --Dave|||You can use 1433 for management if the client is connecting using TCP
Sockets. They can create an alias or change the NetLib choice in the Client
Network Utility to use 1433 for this. If they are using Named Pipes
(probably) then they are using the same ports as TCP over NetBios. I think
it is 135, 137, and 138. If they are using MultiProtocol (doubt it) they
are using the ports for RPC, 135 for the mapper and then 50,000 and up.
Christian Smith
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a959ad45c280f7a989782@.news-40.giganews.com...
> I need to open up my firewall so that a client can access my SQL server
> using the Enterprise Manager. I opened up port 1433, but apparently
> that's just the data connection port, not for management.
> Where can I get a list of all SQL related ports?
> Thanks!
> --Dave|||In article <OPZAL5Z8DHA.2480@.TK2MSFTNGP12.phx.gbl>,
SRDBA@.Careerbuilder.com says...
> INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
> http://support.microsoft.com/defaul...www.sqlpass.org
> "Dave Navarro" <dave@.dave.dave> wrote in message
> news:MPG.1a959ad45c280f7a989782@.news-40.giganews.com...
Thanks for the URL.
Unfortunately, I can't connect to the server using Enterprise Manager.
I can connect to it from ASP, however. The FAQ isn't specific as to
what the connection is used for, but from experience it's used to send
queries/receive data (strictly for data access).
When I am "inside" the firewall and use Enterprise Manager to connect
from another computer on the same network, it works just fine. But I
can't connect to it using Enterprise Manager from outside of the
firewall.
--Dave|||In article <u39HU5Z8DHA.1632@.TK2MSFTNGP12.phx.gbl>, csmith@.digex.com
says...
> You can use 1433 for management if the client is connecting using TCP
> Sockets. They can create an alias or change the NetLib choice in the Clie
nt
> Network Utility to use 1433 for this. If they are using Named Pipes
> (probably) then they are using the same ports as TCP over NetBios. I thin
k
> it is 135, 137, and 138. If they are using MultiProtocol (doubt it) they
> are using the ports for RPC, 135 for the mapper and then 50,000 and up.
> Christian Smith
> "Dave Navarro" <dave@.dave.dave> wrote in message
> news:MPG.1a959ad45c280f7a989782@.news-40.giganews.com...
Thanks for the info. I can successfully connect to port 1433 on the
server using ASP code running in IIS from outside the firewall.
However, Enterprise Manager will not make a connection to the server at
all.
--Dave|||I download TDImon from www.sysinternals.com and watched the
connections...
Enterprise Manager uses port 1433 for its data connection and port 1434
for the management connection.
It's working now.
--Dave
In article <MPG.1a9600c12aad755f989784@.news-40.giganews.com>,
dave@.dave.dave says...
> In article <u39HU5Z8DHA.1632@.TK2MSFTNGP12.phx.gbl>, csmith@.digex.com
> says...
> Thanks for the info. I can successfully connect to port 1433 on the
> server using ASP code running in IIS from outside the firewall.
> However, Enterprise Manager will not make a connection to the server at
> all.