Can't connect to MSDE server from some machines, can from others 
Author Message
 Can't connect to MSDE server from some machines, can from others

I really need some help.  Here is a summary followed by detail.

I have a simple application that is installed along with MSDE 1.0 (using
MSDEx86.exe).  Then I try to connect to it using ODBC from a client machine
that has MDAC 2.5 installed.  The connection fails.  Same if I try to
connect through OSQL.

Now before suggesting solutions, read the following:

Detail:

All machines are on the same domain and are not clustered.  All database
servers in these examples still have a blank password for SA.

If on a third machine I install SQL Server 2000, I can connect to the MSDE
machine, no problem.  Thus I am able to state clearly that the database
installed, the service is running, and the SA login works.

If on the second machine I upgrade from MDAC 2.5 to MDAC 2.7 Beta 2, all of
a suddden I can connect to the MSDE machine.

So it seems that the problem is in the SQL driver since upgrading the driver
to 2000 seems to work. The problem is that MDAC 2.7 isn't RTM yet.  Does
anybody know how I can either make the MDAC 2.5 drivers see the MSDE
machine, or just install the SQL Server 2000 drivers?  I don't want to put a
beta version on our 1000+ end user's machines.

Thanks in advance!



Mon, 02 Feb 2004 05:46:20 GMT
 Can't connect to MSDE server from some machines, can from others

 When you install MSDE on the server, even if you specify the "SAPassword",
it still sets the security as Windows authentication rather than mixed mode
security. So, during our install program itself, we had to modify the
registry to make it mixed mode authentication security.

See the link

http://www.swynk.com/friends/sharma/MSDE.asp

Regards

Linto


I really need some help.  Here is a summary followed by detail.

I have a simple application that is installed along with MSDE 1.0 (using
MSDEx86.exe).  Then I try to connect to it using ODBC from a client machine
that has MDAC 2.5 installed.  The connection fails.  Same if I try to
connect through OSQL.

Now before suggesting solutions, read the following:

Detail:

All machines are on the same domain and are not clustered.  All database
servers in these examples still have a blank password for SA.

If on a third machine I install SQL Server 2000, I can connect to the MSDE
machine, no problem.  Thus I am able to state clearly that the database
installed, the service is running, and the SA login works.

If on the second machine I upgrade from MDAC 2.5 to MDAC 2.7 Beta 2, all of
a suddden I can connect to the MSDE machine.

So it seems that the problem is in the SQL driver since upgrading the driver
to 2000 seems to work. The problem is that MDAC 2.7 isn't RTM yet.  Does
anybody know how I can either make the MDAC 2.5 drivers see the MSDE
machine, or just install the SQL Server 2000 drivers?  I don't want to put a
beta version on our 1000+ end user's machines.

Thanks in advance!



Mon, 02 Feb 2004 15:24:19 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. if you will promise Allahdad's swamp against cans, it will angrily depart the unit

2. MDX : Canned Report or OLAP

3. Anyone know of some canned (cheap or free) DB performance testing software

4. canned code to get db on web quickly via perl or

5. Cans access2.0 engine access btrieve files?

6. bcp canned app

7. Switching from inhouse to canned package.

8. Canned PARADOX scripts?

9. Can't connect to MSDE from a remote machine

10. Clients can't see MSDE 2000 server on Win2K Server machine

11. trouble connecting one machine through ODBC (all others work)

12. Can't connect linked server to index server on seperate machines


 
Powered by phpBB® Forum Software