running sql on a different port

sql 2k, sp3a
For security reasons, I changed sql to run on a different port. I'm able to
get into Enterprise Manager and Query Analyzer just fine. However, when I
try to go into Object Manager in QA, I get a message that the connection has
been broken. It never allows me to see the objects. Is this a bug? Is
there a workaround?
As long as sql is running on port 1433 I can get into the object manager
just fine.
Thanks, Andrehave you tried creating an alias in client network utility and using the
alias to connect to the server?
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> sql 2k, sp3a
> For security reasons, I changed sql to run on a different port. I'm able
to
> get into Enterprise Manager and Query Analyzer just fine. However, when I
> try to go into Object Manager in QA, I get a message that the connection
has
> been broken. It never allows me to see the objects. Is this a bug? Is
> there a workaround?
> As long as sql is running on port 1433 I can get into the object manager
> just fine.
> Thanks, Andre
>|||I have that in place.
"Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> have you tried creating an alias in client network utility and using the
> alias to connect to the server?
> --
> Carlos E. Rojas
> SQL Server MVP
> Co-Author SQL Server 2000 Programming by Example
>
> "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> > sql 2k, sp3a
> >
> > For security reasons, I changed sql to run on a different port. I'm
able
> to
> > get into Enterprise Manager and Query Analyzer just fine. However, when
I
> > try to go into Object Manager in QA, I get a message that the connection
> has
> > been broken. It never allows me to see the objects. Is this a bug? Is
> > there a workaround?
> >
> > As long as sql is running on port 1433 I can get into the object manager
> > just fine.
> >
> > Thanks, Andre
> >
> >
>|||Actually, that worked. I'd created the alias but was still connecting to
'.'. Connecting to the alias was the trick. Thanks!
Andre
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:OcKVNbuAEHA.1964@.TK2MSFTNGP11.phx.gbl...
> I have that in place.
> "Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
> news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> > have you tried creating an alias in client network utility and using the
> > alias to connect to the server?
> >
> > --
> > Carlos E. Rojas
> > SQL Server MVP
> > Co-Author SQL Server 2000 Programming by Example
> >
> >
> > "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> > news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> > > sql 2k, sp3a
> > >
> > > For security reasons, I changed sql to run on a different port. I'm
> able
> > to
> > > get into Enterprise Manager and Query Analyzer just fine. However,
when
> I
> > > try to go into Object Manager in QA, I get a message that the
connection
> > has
> > > been broken. It never allows me to see the objects. Is this a bug?
Is
> > > there a workaround?
> > >
> > > As long as sql is running on port 1433 I can get into the object
manager
> > > just fine.
> > >
> > > Thanks, Andre
> > >
> > >
> >
> >
>