I have two database servers SRVA and SRVB (both SQL2000 on Win 2000). SRVB is setup as a Linked Server in SRVA and they were on the same 100MB LAN. In Query Analyzer, running a stored procedure on SRVB while being connected to SRVA presented good performance and no problems.
Moved SRVA to another site about 15 km away which had a 2MB WAN connection to the site where SRVB is located. I started to get an error which, after checking it out, points to a Remote Login Timeout error. But this is not always the case. Most of the time, I can connect to SRVB and get my results back very fast (like 7 out of ten tries - BUT when it does timeout - it takes like 10 secs - all remote login timeout errors).
My network engineers say the 2MB line is stable and maybe SQL Server is at fault.
Why is this happening and is there anything I can do in SQL Server to solve this problem?
Note: In SRVB, I see BROWSER errors in the Event Log in Windows 2000 (i.e. it cannot get a list of servers...from the master browser, etc.) Is this in anyway connected to my problem? But this BROWSER error problem has always been there even when SRVA was on the same LAN (which provided error free query performance).