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!
--DaveYou 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|||INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932&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|||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/default.aspx?scid=kb;en-us;287932&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 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 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 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...
> > 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 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.

Enterprise Manager 2/ Me 0

Oi! Not that anyone will ever see this post again - but it was McAfee's
Entercept Agent causing the problem - the version we had apparently didn't
like comments (!) in stored procedures, and when it came across one, would
destabilize the server and cause it to crash (v 42.58)..... the latest
version (42.59) fixed the problem.
"B@.DJJ" wrote:

> Ahoy All!
> Say I come in, bright-eyed-and-bushy-tailed in the AM and say "Hey! I thi
nk
> I'll add a field to a table this Bright and Glorious morning!" so I fire u
p
> Enterprise Manager (v 2.0) with the SQL Enterprise Manager (v 8.0) (runnin
g
> on XP SP2 hitting a SQL Server 2000 SP4 DB running on W2k3 Server) and go
to
> design view, add my tiny little field (this time an int, default 0), click
> Apply, click Yes Please (actually OK), and then, lo and behold, I get this
> little gem:
> 17310 :
> SqlDumpExceptionHandler: Process 848 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> No further access via EM or QA at that point.
> So I stop the SQLService on the server, count to 10 and sprinkle a little
> pixie dust about, restart the SQLService, and voila! sometimes my field i
s
> in the table, sometimes it isn't, and if it isn't, I add it in, click Appl
y,
> click Yes Please, and double-viola! It works like a charm - then, for the
> rest of the day, all is well (can add fields, update sprocs, modify trigge
rs,
> you-name-it).
> Any thoughts and suggestions would be appreciated. Haven't tried it via Q
A,
> though, next time I think I'll give 'er a whirl.
> Thanks
>Simply ridiculous.
ML
http://milambda.blogspot.com/