RE: Unable to connect to SQL 2000 engine on other machine from SSM

Hello Robert Hartskeerl,

thank you very much!
Your answer is very, very helpful.

We had following problem:
We distribute our software with MSDE 2000 SP3a.
By default, DISABLENETWORKPROTOCOLS = 0, connection from a client was no
problem.

Now, MS Windows 2003 Server ships with new SS Express Edition 2005 (Backup).
Installation of our software including MSDE works fine, running it on the
server is ok, but connection from client is not possible. Error:
[DBNETLIB]ConnectionOpen (Connect()), Server does not exist.

I thought, it's no problem to run both MSDE 2000 and SSEE 2005 on one server.
Generally, it works perfectly on the server.
But client-access is blocked by default, and I don't know where I can unblock.

Long text, short question:
Do you (or anybody) know, where I can change the behaviour of SSEE 2005, to
block client-access to my MSDE 2000 instance?
It would be easier for us, to change one setting on the server instead of
changing all client-connectionstrings from servername to servername,port.
More over, you have to change port setting from dynamic to static and tell
our customers how to find out port number.

I tried Configuration-Manager, but didn't succeed. Firewall is not the
problem.
Could the problem sit in the UDP 1434 routine how to find MSDE instance?

Thank you for your help,
Migeold.

P.S.: Do you think this behaviour could be a bug in SSEE2005? Software with
a well tested installation routine is not working any more, when you install
it on a pc running SSEE2005?
I tested only with SSEE2005, but I think it's the same problem with all
versions of SQL Server 2005.

"Robert Hartskeerl" wrote:

Ronald,

Try giving the portnumber when you connect. In SSMS type SERVERNAME,1433 as
the servername. Replace 1433 with your portnumber if you changed the default
or running an instance.
--
Robert Hartskeerl, MCTS
http://hartskeerl.nl/blogs/robert/


"Ronald Bijlhouwer" wrote:

On my machine I have installed both SQL Server 2000 as SQL Server 2005.
On another machine SQL Server 2000 is installed.
I am able to connect to my local SQL Server 2000 Engine from within both
Enterprise Manager as SSMS.
Enterprise Manger also allows me to connect to the other machine, however
when I try to connect to it from SSMS I receive a timeout error.
In both cases I have used SQL Server authentication.

Any help appreciated!
.

Relevant Pages

  • Re: Unable to connect to SQL 2000 engine on other machine from SSM
    ... Upgrade MSDE to SP4: not ok. ... Windows 2003 Server ships with SSEE preinstalled (for ... > port information to your client. ...
    (microsoft.public.sqlserver.connect)
  • Re: MSDE and IIS - Web Hosting
    ... sites getting over 3M hits per month and MOST of those hits were on ... when going to Windows 2003 Server and running very SMALL sites using ... coding for MSDE instead of Access because it's really our only option. ... but not as well as SQL Server who knows. ...
    (microsoft.public.sqlserver.msde)
  • Re: MSDE help
    ... there is no limit to the number of connections on an MSDE server. ... I'm working with SQL Server Magazine to put together a weekly newsletter ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: version & instances
    ... Microsoft MVP ... Hitchhiker’s Guide to Visual Studio and SQL Server ... MSDE has a limited database size ...
    (microsoft.public.sqlserver.msde)
  • Re: version & instances
    ... Hitchhiker’s Guide to Visual Studio and SQL Server ... SQL 2000 SP3a for Antivirus app ... Consider that MSDE as a product is somewhat dated ...
    (microsoft.public.sqlserver.msde)