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

I'm not sure why the SQL Server Browser service isn't passing the correct port information to your client. All I can recommend is checking everything from start to finish.
Can the client ping the server? Can the client connect using IP address and port? Can the client connect using name and port? Can other clients connect? Can you connect locally using IP address and port, etc?

Other ideas:
You could move the SQL Server 2005 instance to a new port, letting the MSDE take port 1433, and that might help.
It sounds like you can connect to Computername,port. I presume you could set up a client side alias with the instance name and including the port.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"migeold" <migeold@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5CCC9339-734B-42C2-B80E-CD07252BFC71@xxxxxxxxxxxxxxxx
Yes, it is. Running services on my computer:
- MSSQL$INSTANCE [MSDE 2000]
- SQL Server (MSSQLSERVER) [SSEE 2005]
- SQL Server-Browser

"Rick Byham, (MSFT)" wrote:

Is the SQL Server 2005 Browser Service running on the server?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"migeold" <migeold@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5EC9DDA7-2232-4D56-9212-E85949FC6E8B@xxxxxxxxxxxxxxxx
> 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: Mysterious Port of SQL Server not shown by netstat
    ... If this fails then yoru SQL Server is not listening on 1433. ... port, only ms-sql-s). ... > My query analyzer client from local machine and remote machine> successfully connects to my server. ... There is a jdbc client which wants> to connect at port 1433 that fails saying could not establish network> connection at port 1433. ...
    (microsoft.public.sqlserver.programming)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Default protocols ..
    ... I checked the default port in the Client Utility on the ... "I checked the default port fort the TCP and it is the good ... And are you in a totally SQL Server 2000 environment? ... I set the TCP has the only one default client protocol with the CLICONFG ...
    (microsoft.public.sqlserver.connect)
  • Re: Access To SQL Server Behind Firewall
    ... Using the Client Network Utility on the SQL Client to ... you tell the client what port the "listening" SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... > I am also wondering if it has something to do with TCP port allocation. ... Once the client gets to port 5000 it seems to stop and then ... Normally I'd expect a different error from the SQL Server ...
    (microsoft.public.sqlserver.odbc)