Unable to connect to MSDE 7.0 from client machines

Unable to connect to MSDE 7.0 from client machines

Post by jsque » Mon, 07 Jan 2002 02:31:00



MSDE 7.0 was installed on an NT machine, and I can create the DSN on the NT
machine without any problem, but when we try to create a DSN from 3 Win98
machines we get a connection failed error.  When the DSN is created, we are
using SQL Server authentication and entering 'sa' for the login without any
password.   Not sure what version of mdac is installed on the client
machines, but could MDAC be a problem.

Any help would be appreciated!
Thanks

 
 
 

Unable to connect to MSDE 7.0 from client machines

Post by Jasper Smit » Mon, 07 Jan 2002 03:29:51


Can you ping and net view the MSDE server ?
If you can set up a DSN on the clients then the SQL driver is
installed so it may well be a network/name resolution issue

e.g.
ping SERVERNAME
net view \\SERVERNAME
net use \\SEVERNAME\IPC$

HTH
Jasper Smith


Quote:> MSDE 7.0 was installed on an NT machine, and I can create the DSN on the
NT
> machine without any problem, but when we try to create a DSN from 3 Win98
> machines we get a connection failed error.  When the DSN is created, we
are
> using SQL Server authentication and entering 'sa' for the login without
any
> password.   Not sure what version of mdac is installed on the client
> machines, but could MDAC be a problem.

> Any help would be appreciated!
> Thanks


 
 
 

Unable to connect to MSDE 7.0 from client machines

Post by jsque » Mon, 07 Jan 2002 06:23:04


I was able to ping the server.  I will try the net view and net use commands
on monday.

Even after pinging the server successfully, I was still unable to create a
DSN to this server.

Thanks,
Joe


> Can you ping and net view the MSDE server ?
> If you can set up a DSN on the clients then the SQL driver is
> installed so it may well be a network/name resolution issue

> e.g.
> ping SERVERNAME
> net view \\SERVERNAME
> net use \\SEVERNAME\IPC$

> HTH
> Jasper Smith



> > MSDE 7.0 was installed on an NT machine, and I can create the DSN on the
> NT
> > machine without any problem, but when we try to create a DSN from 3
Win98
> > machines we get a connection failed error.  When the DSN is created, we
> are
> > using SQL Server authentication and entering 'sa' for the login without
> any
> > password.   Not sure what version of mdac is installed on the client
> > machines, but could MDAC be a problem.

> > Any help would be appreciated!
> > Thanks

 
 
 

Unable to connect to MSDE 7.0 from client machines

Post by oj » Mon, 07 Jan 2002 09:59:43


joe,

click on 'client configuration' and select 'tcp/ip' as protocol in your odbc
connection wizard.

-oj


> I was able to ping the server.  I will try the net view and net use
commands
> on monday.

> Even after pinging the server successfully, I was still unable to create a
> DSN to this server.

> Thanks,
> Joe



> > Can you ping and net view the MSDE server ?
> > If you can set up a DSN on the clients then the SQL driver is
> > installed so it may well be a network/name resolution issue

> > e.g.
> > ping SERVERNAME
> > net view \\SERVERNAME
> > net use \\SEVERNAME\IPC$

> > HTH
> > Jasper Smith



> > > MSDE 7.0 was installed on an NT machine, and I can create the DSN on
the
> > NT
> > > machine without any problem, but when we try to create a DSN from 3
> Win98
> > > machines we get a connection failed error.  When the DSN is created,
we
> > are
> > > using SQL Server authentication and entering 'sa' for the login
without
> > any
> > > password.   Not sure what version of mdac is installed on the client
> > > machines, but could MDAC be a problem.

> > > Any help would be appreciated!
> > > Thanks

 
 
 

Unable to connect to MSDE 7.0 from client machines

Post by jsque » Mon, 07 Jan 2002 18:11:23


I have tried setting the client configuration to both tcp/ip and to other,
but neither works.


> joe,

> click on 'client configuration' and select 'tcp/ip' as protocol in your
odbc
> connection wizard.

> -oj



> > I was able to ping the server.  I will try the net view and net use
> commands
> > on monday.

> > Even after pinging the server successfully, I was still unable to create
a
> > DSN to this server.

> > Thanks,
> > Joe



> > > Can you ping and net view the MSDE server ?
> > > If you can set up a DSN on the clients then the SQL driver is
> > > installed so it may well be a network/name resolution issue

> > > e.g.
> > > ping SERVERNAME
> > > net view \\SERVERNAME
> > > net use \\SEVERNAME\IPC$

> > > HTH
> > > Jasper Smith



> > > > MSDE 7.0 was installed on an NT machine, and I can create the DSN on
> the
> > > NT
> > > > machine without any problem, but when we try to create a DSN from 3
> > Win98
> > > > machines we get a connection failed error.  When the DSN is created,
> we
> > > are
> > > > using SQL Server authentication and entering 'sa' for the login
> without
> > > any
> > > > password.   Not sure what version of mdac is installed on the client
> > > > machines, but could MDAC be a problem.

> > > > Any help would be appreciated!
> > > > Thanks

 
 
 

Unable to connect to MSDE 7.0 from client machines

Post by Bill Hollinshe » Wed, 16 Jan 2002 08:53:27


Hi Joe,

Make sure MSDE is listening upon tcp/ip and has been setup for standard
security. Also remove any advanced entry (in the client config utility).
You can test the preceding using odbcping.exe (see BOL). If the client is
using MDAC 2.6 (as determined by  Component Checker at
www.microsoft.com/data) then please apply the latest MDAC service pack and
test.

Hope this helps,
Bill

This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
--------------------


>Newsgroups: microsoft.public.sqlserver.connect




>Subject: Re: Unable to connect to MSDE 7.0 from client machines
>Lines: 72
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

>Date: Sun, 06 Jan 2002 09:11:23 GMT
>NNTP-Posting-Host: 24.30.128.112

>X-Trace: typhoon.san.rr.com 1010308283 24.30.128.112 (Sun, 06 Jan 2002
01:11:23 PST)
>NNTP-Posting-Date: Sun, 06 Jan 2002 01:11:23 PST
>Organization: Road Runner
>Path:

cpmsftngxa07!tkmsftngxs02!tkmsftngxs01!tkmsftngp01!newsfeed00.sul.t-online.d
e!t-online.de!skynet.be!skynet.be!newsfeed.online.be!sn-xit-01!sn-xit-04!sup
ernews.com!news-west.rr.com!cyclone.kc.rr.com!news.kc.rr.com!cyclone3.kc.rr.
com!news3.kc.rr.com!typhoon.san.rr.com!not-for-mail
>Xref: cpmsftngxa07 microsoft.public.sqlserver.connect:26089
>X-Tomcat-NG: microsoft.public.sqlserver.connect

>I have tried setting the client configuration to both tcp/ip and to other,
>but neither works.



>> joe,

>> click on 'client configuration' and select 'tcp/ip' as protocol in your
>odbc
>> connection wizard.

>> -oj



>> > I was able to ping the server.  I will try the net view and net use
>> commands
>> > on monday.

>> > Even after pinging the server successfully, I was still unable to
create
>a
>> > DSN to this server.

>> > Thanks,
>> > Joe



>> > > Can you ping and net view the MSDE server ?
>> > > If you can set up a DSN on the clients then the SQL driver is
>> > > installed so it may well be a network/name resolution issue

>> > > e.g.
>> > > ping SERVERNAME
>> > > net view \\SERVERNAME
>> > > net use \\SEVERNAME\IPC$

>> > > HTH
>> > > Jasper Smith



>> > > > MSDE 7.0 was installed on an NT machine, and I can create the DSN
on
>> the
>> > > NT
>> > > > machine without any problem, but when we try to create a DSN from 3
>> > Win98
>> > > > machines we get a connection failed error.  When the DSN is
created,
>> we
>> > > are
>> > > > using SQL Server authentication and entering 'sa' for the login
>> without
>> > > any
>> > > > password.   Not sure what version of mdac is installed on the
client
>> > > > machines, but could MDAC be a problem.

>> > > > Any help would be appreciated!
>> > > > Thanks

 
 
 

1. Conflict between running MSDE 2000 and SQL 7.0 on the same client machine

I have 2 accounting software packages that are loaded on 2
seperate servers.  One uses SQL 7.0 the other uses MSDE
2000.

When running the MSDE 2000 application I get timed out to
the server due to a conflict between the SQL 7.0
workstation application and the new MSDE 2000 workstation
application.

Does anyone know of a fix or workaround in running both on
the same workstation till we convert over to the new MSDE
2000 app.

2. DBCC CHECKIDENT from VB?

3. MSDE (Jr. SQL Server 7.0) will not start on Win98 machine using SQLDMO from remote machine

4. telnet timeout

5. MSDE 2000 compatibility with SQL 7.0 client-only tools (MSDE 2000 SP2 tested)

6. Purchase Orders

7. Cannot Detect MSDE or SQL Server 7.0 on the machine

8. Announcement: StarOffice/OpenOffice IFilter

9. Unable to connect to remote SQL server from Windows 2000 machine

10. SQL 7.0 MSDE and SQL 2000 on one machine

11. Unable to connect to an Oracle server from another machine

12. Can't connect to MSDE server from some machines, can from others

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