Thanks Coraleigh!
I'll check the event logs and see exactly what errors are going on. These
machines are out of the country, so it's a little tough...
Thanks!
....Joe
"Coraleigh Miller" wrote:
> The default Site Link Replication Interval is set to 180second retry
> interval regardless of whether or not the line between is down or not.
> Check that you have an interval time set in your Site Link Replication
> Interval in your AD Sites and Services -> Inter-Site Transports -> IP (or
> SMTP).
> If this is configured correctly, let us know if you have an error in your
> event log during a time when your server loses connection as that should
> give us some more info to go on.
>
> Coraleigh Miller
>
>
> "racerx94022" <(E-Mail Removed)> wrote in message
> news:8BA684D5-1C90-4C73-A903-(E-Mail Removed)...
> > Hello Everyone,
> > I've got an issue I hope someone has a fix for... I'll be as specific as I
> > can.
> >
> > I've got a site setup with headquarters and a bunch of remote sites. These
> > sites are connected via DS3 lines, and crypto gear... I have one domain...
> > Headquarters has a couple of DC controllers, and the remote sites have one
> > DC
> > controller and a second server. The servers are all running Windows 2003
> > Ent, SP1.
> >
> > Periodically, a DS3 will go down for an indeterminant amount of time.. The
> > remote server loses it's connection to the DC server at headquarters and
> > stops talking to the main DC servers... The only way to get the remote
> > server
> > back to talking on the domain is to remotely connect to it and reboot it.
> > This is happening consistently at all remote sites.
> >
> > Does anyone know of a way to make the remote servers not give up on
> > retrying
> > to make a re-connection to HQ when the line goes back up?
> >
> > Thanks!
> >
> > ...Joe
>
>
>
|