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

Did you every figure this out?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"migeold" <migeold@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6F992918-CFCD-40D3-B2C2-4F601F75423B@xxxxxxxxxxxxxxxx
I've made these tests:
- Alias with port number: ok
- Upgrade MSDE to SP4: not ok.
- Stop Service SQL-Server 2005: not ok.
- Stop Service SQL-Browser: not ok.
- Altered start order of services (used DependOnService in Registry): not ok.

So, I'm very frustrated. Seems, BOL is wrong respectively SQL Browser is not
working correctly.

If I don't get any solution in this newsgroup the next days, I'll post a bug
report.

"migeold" wrote:

Hi Rick,

thank you very much for your help!
First of all, it's no network problem. I can pass through firewall, I can
ping the server and yes, I can connect to MSDE when I use
ServerName\Instance,Port.

But, I can't connect when I only use Server\Instance. I'm sure, it's the way
how SQLServer-Browser resolves portnumber of MSDE named instance.

I made following tests on a clean Windows XP SP2 Prof.:
1.) Install MSDE 2000 SP3a first, then install SSEE 2005 -> Connection is ok!
2.) Install SSEE first, then install MSDE -> Connection is not ok!

In both cases, I used a named instance for MSDE and SSEE. I explicitly
enabled SQLServer-Browser service.

I found an very useful articel in BOL (see
http://msdn2.microsoft.com/en-us/library/ms165724(d=printer).aspx) descriping
how SQLServer-Browser works (or should work). Acording to it, MSDE 2000 SP3a
works together with SSEE without any problem. But it doesn't...

Of course, your advice should work (I'll test it shortly). I could use alias
or move port-number.
But, our main problem is: we do have an installation routine (well tested)
to install our software with MSDE for server/client. Everything was working
very well.
Since a few months, Windows 2003 Server ships with SSEE preinstalled (for
backup) and now, our setup fails (clients are not able to connect).

For us and our customers, it would be easier to change SQLServer settings in
one place instead of changing many clients.

I'll test shortly:
1.) Your advice with alias.
2.) Upgrade MSDE SP3a to SP4.
3.) Disable SQLServer-Browser service and SSEE 2005, acording to BOL, MSDE
SSRP (SQL Server Resolution Protocol) is activated.

BOL says, in case of problems you should alter start sequence of services
(Browser and MSDE). I tried that manually, but it didn't work. Do you know,
where I can alter start sequence, so I can test it after reboot?

Migeold.

"Rick Byham, (MSFT)" wrote:

> 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: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: Redirecting data sent to a local printer to another host and port on the network
    ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
    (comp.unix.sco.misc)