Hello TestMachine1 runs SQL2005 SP2 and has as linked server myRemoteServer (SQL2000) server. I run an stored procedure in TestMachine1 which inserts about 20,000 rows to a table in myRemoteServer and brings back a similar quantity of rows. This stored procedures take about 1.5min to complete, but no error appears (not executed within a distributed transaction). When running the same stored procedure in TestMachine2 (also SQL2005SP2), the following error appears after about 1 minute of execution (not the exact text): SQLNCli. TCP Provider: network name is no longer available... communication link failure. The stored procedure can be resumed as (the where claused has been omitted): insert into myRemoteTable select * from myLocalTable -- This takes 19 seconds to finish execute synonym_MyRemoteSP -- This remote SP makes updates and inserts insert into myLocalTable select * from myRemoteTable Please note that the stored procedure worked before on TestMachine2 (but with less than 10,000 rows) and that connectivity is proven among TestMachine2 and myRemoteServer, since I can execute "select * from synonym_MyRemoteTable" with no problems at all in the TestMachine2's Management Studio. TestMachine1 and TestMachine2 have Windows XP Professional SP2; myRemoteServer has Windows 2003 and SQL Server 2000 SP4. All the 3 machines are in the same LAN. Can you please help me to avoid this error? Would you recommend to use Named Pipes instead?