From: "Robert Comer" 

Yuck...

- Bob Comer


"Ellen K"  wrote in message
news:1096c5.c308a1{at}harborwebs.com...
> I left the script running and actually there were timeouts pretty much all
day.
>   :(
>
> > From: "Robert Comer" 
> > That's NT to me...  Interesting, I never have run into that
configuration,
> > but it sure sounds like a performance problem more than hardware fault
given
> > the timing.
> > - Bob Comer
> > "Ellen K"  wrote in message
> > news:5096be.c2a39b{at}harborwebs.com...
> >> W2K
> >>
> >> > From: "Robert Comer"

> >> > Running on top of NT?
> >> > - Bob Comer
> >> > "Ellen K." 
wrote in message
> >> > news:8m2sb09ba4d51l6ol7n9iu91eufvre8anj{at}4ax.com...
> >> >> We don't have AD, we are still using NDS.  
(Migrating by the end of
> > the
> >> >> year.)
> >> >>
> >> >> On Wed, 2 Jun 2004 12:31:30 -0400, "Robert Comer"
> >> >>  wrote in message
> >> >> :
> >> >>
> >> >> >AD replication maybe?
> >> >> >
> >> >> >- Bob Comer
> >> >> >
> >> >> >
> >> >> >"Ellen K."
 wrote in message
> >> >> >news:9murb0pkbme0kelhi9psq99hv6ndnjrcgn{at}4ax.com...
> >> >> >> Ha, I caught it.   :)
> >> >> >>
> >> >> >> Multiple "Request timed out" s at
6:09, 6:10, 8:11, 8:12, 8:16.
> >> >> >>
> >> >> >> Think I'll let it continue for awhile to
see if it does it again
> > around
> >> >> >> 10:10, that would indicate something
happens about every two
hours.
> >> >> >> But 6:09 I think is the EXACT same time it
happened to me once
> >> >> >> interactively.
> >> >> >>
> >> >> >> Of course, this doesn't tell the REASON,
but at least now I have
> >> >> >> documentation of the problem.   :)
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >>

--- BBBS/NT v4.01 Flag-5