I would appreciate any help and recommendation to solve the following problem in our Client/Server applications:
our client programs communicate via the default net-library, Named Pipe with the SQL Server 6.5. Because of changes in the C/S environment (that is the client and the
server should be in different domains), we had to change from Named Pipe to TCP/IP communication.
The following problems we "generated" after this change: every 3-4 days the new connections are refused by the SQL Server without any error message.
We have to restart the SQL Server service to solve this conection problem.
ANY IDEAS
Billy H
bill@xhog.co.uk
our client programs communicate via the default net-library, Named Pipe with the SQL Server 6.5. Because of changes in the C/S environment (that is the client and the
server should be in different domains), we had to change from Named Pipe to TCP/IP communication.
The following problems we "generated" after this change: every 3-4 days the new connections are refused by the SQL Server without any error message.
We have to restart the SQL Server service to solve this conection problem.
ANY IDEAS
Billy H
bill@xhog.co.uk