Re: Cluster service, network name takes long time to start/fail
- From: Björn <Bjrn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 04:26:02 -0700
it dosent fail before starting, and the log dosent say anything after we
enabled kerberos for the resource network name, but it didnt help much.
"John Toner [MVP]" wrote:
> Check the event logs to see if the resource is failing before starting.
> Otherwise, check the cluster.log for hints. Cluster logs are located in
> c:\windows\cluster\cluster.log.
>
> Regards,
> John
>
> "Björn" <Bjrn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:9A07F30F-8179-4D6A-B72C-B48347495BBB@xxxxxxxxxxxxxxxx
> > Hi
> >
> > we have a new Cluster for Exchagne and it works fine but..
> > the Resourse Network Name takes about 2 min to start/"restart".
> > and i am realy new to cluster, were do i start looking for errors.
> > Network IP startes in about 5 sec.
> > and all the outher resoures starts fine.
>
>
>
.
- References:
- Cluster service, network name takes long time to start/fail
- From: Björn
- Re: Cluster service, network name takes long time to start/fail
- From: John Toner [MVP]
- Cluster service, network name takes long time to start/fail
- Prev by Date: Re: RAS and NAT
- Next by Date: RE: Serv. Perf. Advisor: Invalid Data Set Reports
- Previous by thread: Re: Cluster service, network name takes long time to start/fail
- Next by thread: Windows 2003 terminal services
- Index(es):
Relevant Pages
|