connectivity to the databse in SQL server 7

Can somebody tell me, how can I connect to the server(OS WIN NT server 4.0). I have created one database(microsoft SQl server 7.0) in my company server.And I tried to connect using ODBC Data source administrator to connect to it. It's failed. This error prompted.

Connection failed
SQL state'28000'
SQL server driver'18456'
[Microsoft ][ODBC SQL server driver ][SQL server] Login failed for user 'faraidba']

do I need check my login ID for the database I have created or my ODBC driver is obsolete. Please help as I'm new with it.Did you select NT authentication or Server authentication?
I suspect it was server authentication, You have either supplied an invalid username, an invalid password, or some combination of both.
If you used NT authentication, your problem is that your network id has not been setup as a valid login.

If you wish to test your login you can always use I/OSQL.EXE. If you are using NT authentication you should be able to login in using "OSQL -S <your server name> -E", and if using Server authentication try "OSQL -S <your server name> -U <your user id> -P <your password>". If either of these work then you have a problem with ODBC.

give this some thought and let me know what you find.|||Thanx.

I've followed ur suggestion. I used the correct login name and password. The network library: I chose 'name pipes' connection in ODBC to connect to the server and this message propmted;

Connection failed
SQL state:'08004'
SQL serve error:4062
Server rejected the connection;
Access to selected database has been denied

Should I use TCP/IP(network libraries) instead?|||Thanx.

I've followed ur suggestion. I used the correct login name and password. The network library: I chose 'name pipes' connection in ODBC to connect to the server and this message propmted;

Connection failed
SQL state:'08004'
SQL serve error:4062
Server rejected the connection;
Access to selected database has been denied

Should I use TCP/IP(network libraries) instead?

I try to connect using server authentication.|||Okay, I think your problem is that the usreid you are using has not been granted access to the DB you are trying to connect to.

Again if you use I/OSQL.EXE to try and connect as I outlined before you would have connected to your default database. Most of the time this is the master db. If you try usng I/OSQL again but add "-d <your db name>" and see if you don't get a similar message or connect as before and issue the T-SQL command "use <your db name> go".

The NETWORK Library you are using is just fine. The fact that you have connected to the SQL engine is evident by the error message.|||you're correct. now i'm able to do the connection.

hope to seek ur help next time.. ;)
thanks, freind

laziaf238
KL,
Malaysia

Connection Timeouts - a tough one!

I'm having major problems with SqlClient Data provider connections in my application. I'm using Win 2003 Server with SQL Server 2000 (both on the same machine), and my application is developed in VB.NET.

I'm using the following db connection string:
Data Source=(local);Initial Catalog=database;Uid=user;Pwd=password;max pool size=100;

As you can see max pool size is set to 100. The SQL Database has it's MAX_CONNECTIONS property set to >32000.

The symptoms are that at seemingly random times, not nessecarily during peak hours, the application becomes extremely slow and stops responding. The error message that is beeing generated is "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

After monitoring and debugging, I've found two things.

1) At random times, zero-three times a day, the number of database connections (according to performance monitor) rises from normally 2-8 up to 20-25. After a while, usually 10-60 minutes, it drops back to normal. This is directly related to when the timeout errors occur. It doesn't seem to happen more often during peak load, for some reason. I suspect there is connection leakage in the application, but I've done extensive debugging, and I just can't find any. Also, since the peaks occur randomly and I can't reproduce the error in my development environment, I have no solution to this problem. A few weeks ago, the application ran during heavy load without this problem for 7 days. Before and after that, there have been errors at least every second day. That confuses me even more.

2) The number of connections (monitored in perf mon) never reach above 25. Why? I'm using SQL Server enterprise edition, it's connection limit is over 32000. ADO pool size is 100, and I can't find anything else that would limit the amount of concurrent connections. I'm totally confused. Why does number of connections never rise above 25? Is there a setting hidden somewhere that I just can't find? Also, according to Performance Monitor, I don't get any failed connects, I just get failed commands. Maybe that's a clue? Could the problem some kind of deadlocks in the database that causes timeout?

I realize this entire post is rather confusing. It reflects the state of my mind, I guess, after working around the clock on this issue for a month :)

Any help is deeply appreciated!Hi,
I'm facing similar problem as well on my local machine (Windows 2000 advance server + SQL Server 7.0). The difference is that when i check the number of connections, they had reached the max size of 100.
I think my problem lies in connections that remain open after the page is loaded. For example whenever I run a particular page(that shows a complex report), 14 more connections are added to User Connections in Performance Monitor.
Can anyone tell me why the connections remain open even after the page is executed? Shouldn't they be closed once the page is loaded and returned to the connection pool to be reused?

Any help/suggestion will be highly appreciated.

Thanks|||The common reason for the problems you are having (often referred to as "connection leakage") is that the database connection object is not closed after the page is finished using it. If you don't close the object manually, it won't be returned to the pool until it times out.

Example of syntax:

Dim objConn As New SqlConnection( ConnectionString )

objConn.Open()
' put code to communicate with database here
objConn.Close()

If you are sure that you are closing all connections properly, and still are experiencing this problem, I'm all out of ideas..

Connection String Error

Hi Team

I am new to WEB sites as I normal work with Win apps.

I am using Server 2003 with SQL server 2005 Delevoper.

The server is on my own network in the same room..

I have made a new Web Site in Visual Studio 2005 DotNet Framework 2.0. It runs fine on testing.

I can log in and move around just fine. BUT when I publish it to the server the following happens:

I Can find the web site in internet explore from my Domain name (www.rbsoft.com.au) or Static IP. I get the default page up ok.

Then when I click on login I will get the login page. So I fill it in and click Login.

Then I get the follwing Error message.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

The Connection string is as follows:

<connectionStrings>

<add name="ConnectionString" connectionString="Data Source=RBSOFT-SERVER\MSSQLSERVER;AttachDbFilename=\App_Date\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>

</connectionStrings>

I seems to me that the web site can not find the ASPNETDB.MDF database.

I can see the database on the server with "SQL Server Management Studio Express"

I spent many hours trying to find out why it will not work.

Can any one help me - Please

Regards

Ron B

please check spelling of \App_Date\*.mdf
DatE or Data

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
your network documentation.
Sometimes there is no error but the Tests failed' and DSN is not created!
In the SQL Error log the messages are like "Unable to create Login
packet(s)"
With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message
"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."
We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.
It was working fine yesterday!
Any help would be appreciated."Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-berlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can connect
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving the
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.
Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?
Just a thought...|||Seems like we had client problems like this and it turned
out that the clients swicthed the connection properties in
ODBC to tcp/ip sockets when we were using named pipes on
the server side. This happened after the installation of
an application on the clients. Maybe try different
options in the client config options in odbc on the
clients?

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is

Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
your network documentation.

Sometimes there is no error but the Tests failed' and DSN is not created!

In the SQL Error log the messages are like "Unable to create Login
packet(s)"

With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message

"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."

We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.

It was working fine yesterday!
Any help would be appreciated."Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-berlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can connect
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving the
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.

Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?

Just a thought...

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
your network documentation.
Sometimes there is no error but the Tests failed' and DSN is not created!
In the SQL Error log the messages are like "Unable to create Login
packet(s)"
With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message
"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."
We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.
It was working fine yesterday!
Any help would be appreciated.
"Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-berlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can connect
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving the
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.
Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?
Just a thought...

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
your network documentation.
Sometimes there is no error but the Tests failed' and DSN is not created!
In the SQL Error log the messages are like "Unable to create Login
packet(s)"
With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message
"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."
We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.
It was working fine yesterday!
Any help would be appreciated.
"Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-berlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can connect
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving the
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.
Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?
Just a thought...

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
your network documentation.
Sometimes there is no error but the Tests failed' and DSN is not created!
In the SQL Error log the messages are like "Unable to create Login
packet(s)"
With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message
"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."
We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.
It was working fine yesterday!
Any help would be appreciated.
"Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-berlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network error. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can connect
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving the
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.
Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?
Just a thought...

Connection Problems to SQL 6.5

We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine then
the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
(192.168.0.2 where its connecting fine). The error when creating ODBC DSN is
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(recv(
)).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server][TCP/IP Sockets]General network erro
r. Check
your network documentation.
Sometimes there is no error but the Tests failed' and DSN is not created!
In the SQL Error log the messages are like "Unable to create Login
packet(s)"
With the SQL Enterprise manager running on the client machines I can connect
to the server (sometimes!) but it does not expand the databases etc or any
thing listed under the server. However now its not connecting and giving the
message
"A connection could not be established to 202.64.213.11 - [DB-Library]
Possible network error: Write to SQL Server Failed. General network error.
Check your documentation."
We've tried different things like creating user accounts on the multihomed
and client systems again. changing password to log on to Win XP etc.
Upgrading on one machine to MDAC 2.8 but there is no success etc.
It was working fine yesterday!
Any help would be appreciated."Mansoor Azam" <mansoorb@.shoa.net> wrote in message news:<c5oimj$44h14$1@.ID-31123.news.uni-b
erlin.de>...
> We connect to a SQL 6.5 server (IP for example 202.64.213.11) on WIN NT
> using ODBC DSN and / or SQL Client (DB-LIB). Everthing was working fine th
en
> the some XP client machines (192.168.0.1 and 192.168.0.3) started giving
> problems. All TCP/IP connections go thru the WIN 2000 multihomed machine
> (192.168.0.2 where its connecting fine). The error when creating ODBC DSN
is
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 10054
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]ConnectionRead(rec
v()).
> Connection failed:
> SQLState: '08501'
> SQL Server Error: 11
> [Microsoft][ODBC SQL Server][TCP/IP Sockets]General network er
ror. Check
> your network documentation.
> Sometimes there is no error but the Tests failed' and DSN is not created!
> In the SQL Error log the messages are like "Unable to create Login
> packet(s)"
> With the SQL Enterprise manager running on the client machines I can conne
ct
> to the server (sometimes!) but it does not expand the databases etc or any
> thing listed under the server. However now its not connecting and giving t
he
> message
> "A connection could not be established to 202.64.213.11 - [DB-Library]
> Possible network error: Write to SQL Server Failed. General network error.
> Check your documentation."
> We've tried different things like creating user accounts on the multihomed
> and client systems again. changing password to log on to Win XP etc.
> Upgrading on one machine to MDAC 2.8 but there is no success etc.
> It was working fine yesterday!
> Any help would be appreciated.
Is it possible that the WinXp clients have somehow enabled IPV6
support and may be garbling the traffic to the server ?
Just a thought...