[quoted text, click to view] "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 ?