Hi;

Ok I installed SqlServer 2000 on a machine that already had SqlServer 2005.
When I installed I had to enter an instance name for it and entered the name
SqlServer2K.

I can bring it up on the server using EnterpriseManager fine. But I cannot
connect with EnterpriseManager from my workstation. I can still convert to
Sql Server 2005, but not Sql Server 2000.

I have tried both Windows Authentication and the sa login from my
workstation. I get cannot establish connection or cannot login.

Also, when I run the wizard to connect, it does not show the server as a
choice - I have to type it in.

Any ideas?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm




"Arnie Rowland" wrote:

> You can install them both without conflict. There will not be any port
> conflicts.
>
> One will be the default Server, known as {computername}, and the other will
> have an Instance Name, and be addressed as {computername\InstanceName}. Any
> application seeking a SQL Server by the IP will be directed to the default
> server.
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
>
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> You can't someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
>
> "David Thielen" <thielen@nospam.nospam> wrote in message
> news:7C6CF9B6-CB9A-4E15-B8E5-9531057768FB@microsoft.com...
> > Can I put both on the same server without any conflicts or other problems?
> > Or
> > do they fight for the TCP port to respond to client requests?
> >
> > --
> > thanks - dave
> > david_at_windward_dot_net
> > http://www.windwardreports.com
> >
> > Cubicle Wars - http://www.windwardreports.com/film.htm
> >
> >
>
>
>