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

Tell me a bit about the capabilities of exchange server?

0 Answers  

---

Why do I need microsoft exchange?

0 Answers  

---

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

0 Answers  

---

What is managed store in exchange 2013?

0 Answers  

---

Are there any other installation considerations?

2 Answers  

---

What is forms Based Authentication

1 Answers  

---

What is circular logging

4 Answers   IBM,

---

Can I use exchange 2000 tools to manage exchange 2003 servers?

0 Answers  

---

Explain how do I enable the security tab for the organization object?

0 Answers  

---

What are Query Based Distribution groups?

2 Answers  

---

Do I need windows xp to use outlook rpc over http?

0 Answers  

---

user not able to see his email address in GAL ,but able to send and recieve emails.Why ?

5 Answers   IBM, Wipro,

---