Communication error with transactional replication

I have been receiving the following errors from time to
time during my nightly processing. At this time we
replicate a large amount of commands. The funny thing is
after these errors occur once, the next run is successful.
General network error. Check your network documentation.
The error code is 11.
immediately followed by:
Communication link failure with an error code 08S01.
I have increased my querytimeout to 900 from 300 in my
distribution agent profile, based on a post I read, and no
luck.
We run the same process in our another environment without
any issues. The only difference in this environment is
that it is on clustered hardware.
Any advice where to look? How to troubleshoot?
This means your network has hicupped. QueryTimeout set the timeout for
internal queries it has no effect on your network and won't help to reduce
this error. You have to contact your network admin to help resolve this
error.
"Kartik" <anonymous@.discussions.microsoft.com> wrote in message
news:1625201c41bec$c2624b30$a601280a@.phx.gbl...
> I have been receiving the following errors from time to
> time during my nightly processing. At this time we
> replicate a large amount of commands. The funny thing is
> after these errors occur once, the next run is successful.
> General network error. Check your network documentation.
> The error code is 11.
> immediately followed by:
> Communication link failure with an error code 08S01.
> I have increased my querytimeout to 900 from 300 in my
> distribution agent profile, based on a post I read, and no
> luck.
> We run the same process in our another environment without
> any issues. The only difference in this environment is
> that it is on clustered hardware.
> Any advice where to look? How to troubleshoot?
>