Re: Exchange 2003 Cluster Problem



Hi Rodney
I have not changed anything on Node1.There are no service packs installed
for WIndows 2003 Server.Exchange 2003 has Service pack installed.Both the
Nodes were working fine.This issue suddenly came up.I cannot see any errors
in the Event Log.Where can i check the Cluster Logs.
I can ping the Heartbeat connection between the two nodes.
Only thing is once i failback to Node 1,Users cannot open thier
Outlook,neither can i ping to Exchange MSDTC Virtual IP or the Name.
I know it is not a good idea to shut down Node1 but that is the only option
left till i find a solution.I haven,t turned on the Firewall.
I have two groups in the cluster
Windows cluster grouip
Exchange group having the resources fro Exchange 2003 Server.
The Network stack has two connections
Private and Public
I can ping to the Private IP of Node 2 from Node 1
I can ping to the Public IP of Node 2 from Node 1.
Both the Nodes are pointing to internal DNS.
I don,t why it is happening.
need help urgently
Regards
Fasahat


"Rodney R. Fournier [MVP]" wrote:

> So what has changed on Node1? Did you install SP1 and turn on the firewall?
> Was it patched? Did it ever work? What do the Cluster.log and Event logs
> tell you?
>
> Shutting down the node is probably not the best idea. How many Groups do you
> have in your cluster? What service pack(s) are you running for the OS and
> Exchange? What does the network stack look like on Node1? I simply need more
> information.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
>
>
> "Fasahat" <Fasahat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:AACA2B39-36CD-4C78-B493-3EA3C27E7BBD@xxxxxxxxxxxxxxxx
> > Hi Friends
> > I have an Exchange 2003 Cluster configured on Windows 2003 Server
> > Opearting
> > System.My exchange was working fine before two days.I suddenly got a
> > problem.Users cannot access the Exchange Cluster if the exchange resourecs
> > are on Node1.i cannot ping to the Exchange cluster Virtual name neither
> > the
> > exchange MSTDC IP Address.I can ping the windows Cluster.The Cluster
> > failover
> > and failback is working.There are no errors in theEvent Log.
> > Once i failover to NODE 2 users can access the exchange cluster and send
> > and
> > recieve mails.i can ping the exchange virtula IP Address.
> > If i failback to NODE1 the problem arises.
> > I have shut down the Node 1 and all the resources are on NODE2.
> > I tried to search Microsoft knowledge base,couldnt find the right
> > solution.
> > PLease Advice.
> > Regards
> > fasahat
> > --
> >
>
>
>
.



Relevant Pages

  • Re: Exchange 2003 Cluster Problem
    ... MVP - Windows Server - Clustering ... > in the Event Log.Where can i check the Cluster Logs. ... > Outlook,neither can i ping to Exchange MSDTC Virtual IP or the Name. ...
    (microsoft.public.windows.server.clustering)
  • Exchange 2007 SP1 Standard Edition - SCR on a Windows 2003 Cluster
    ... Two-node cluster of Windows Server 2003 Enterprise Edition with external ... transition from MS Exchange Server 2003 Standard Edition which resides on ...
    (microsoft.public.exchange.setup)
  • Please help, Exchange 2000 install on Windows 2003 cluster
    ... Currently we have Exchange 2000 running in cluster environment. ... Can I install the new cluster with Windows 2003, then install Exchange ...
    (microsoft.public.exchange2000.admin)
  • EX2K7-MBX-Rolle und Cluster (noch mal)
    ... Habe ein Problem mit Cluster aufbauen mit EX2K7. ... In der Domäne habe ich noch einen DC, Windows 2000 als DNS-Server. ... Ich führe gerade die Migration mit Exchange 2007, ... MSexchangesa und msexchangeis. ...
    (microsoft.public.de.exchange)
  • Re: Exchange 2003 Cluster Problem
    ... What does the network stack look like on Node1? ... http://www.clusterhelp.com - Cluster Training ... > I have an Exchange 2003 Cluster configured on Windows 2003 Server ... > exchange MSTDC IP Address.I can ping the windows Cluster.The Cluster ...
    (microsoft.public.windows.server.clustering)

Loading