Answer / ganesan

(Talking only about the mailbox server and not other roles).

The client connection to the server is lost. So we will
have the pop up stating that the connection to the exchange
server is lost. The client will again try to establish the
connection. This is easily seen in MS Outlook Client.

Next will be our ping test to the server to ensure the
server is alive.
Followed by the DNS – and NSLOOKUP test.
Final will be the telnet – ip address – port test.

If all these test passes then we can log into the exchange
box and start trouble shooting. Like restarting the
required services, finding if the mailbox store is mounted.
Or has the server reached back pressure and is not able to
process the t-logs.

From another exchange server launch the system manager and
navigate to GUI interface (tools – monitoring and status) ,
which will show the server (which is down) - status as
unreachable.

Needless to say – have a look in the event logs. (Hopefully
you have enabled the Diagnostic logging to capture the
required events)

Also larger Organization has monitoring tools which will
automatically send the alerts to the messaging team /
administrator that the server is down. Via Windows OS we
can configure the appropriate SNMP traps to trigger the
event.

I think these are basic things one has to do when a server
is down.

Answer / raghuma reddy

The client connection to the server is lost. So we will
have the pop up stating that the connection to the exchange
server is lost. The client will again try to establish the
connection. This is easily seen in MS Outlook Client.

Next will be our ping test to the server to ensure the
server is alive.
Followed by the DNS – and NSLOOKUP test.
Final will be the telnet – ip address – port test.

If all these test passes then we can log into the exchange
box and start trouble shooting. Like restarting the
required services, finding if the mailbox store is mounted.
Or has the server reached back pressure and is not able to
process the t-logs.

From another exchange server launch the system manager and
navigate to GUI interface (tools – monitoring and status) ,
which will show the server (which is down) - status as
unreachable.

Needless to say – have a look in the event logs. (Hopefully
you have enabled the Diagnostic logging to capture the
required events)

Also larger Organization has monitoring tools which will
automatically send the alerts to the messaging team /
administrator that the server is down. Via Windows OS we
can configure the appropriate SNMP traps to trigger the
event.

I think these are basic things one has to do when a server
is down.

Answer / gomoco

The client connection to the server is lost. So we will
have the pop up stating that the connection to the exchange
server is lost. The client will again try to establish the
connection. This is easily seen in MS Outlook Client

If its one server, Test MAPI conectivity to check they
connection to the server.

Answer / ekambaram

Using Micosoft Best Practise Anyalyzer also a good solution

Explain what is the oma?

0 Answers  

---

Explain how do I stop users from going to a bookmarked /logon.asp page after conversion to 2003 owa?

0 Answers  

---

What is exchange 2003 forestprep?

0 Answers  

---

If one exchange server failed means not working then how will you check?

4 Answers  

---

What is happening with public folders?

0 Answers  

---

How to retreive emails from mail server if the emails have been deleted unfortunately?

5 Answers   IBM,

---

Why do I need microsoft exchange?

0 Answers  

---

Explain how many global catalog servers should I deploy?

0 Answers  

---

Explain how do I add a disclaimer to outgoing smtp messages in visual basic/visual basic script?

0 Answers  

---

What do I need in order to install exchange 2003?

0 Answers  

---

Can I deploy oma in a mixed environment?

0 Answers  

---

Name some of the SMTP Virtual server configuration options.

1 Answers  

---