Could I have more details regarding the problem, like did you install any new s/w etc. and the other stuff. I can first relate this to the patch cords. or the n/w point itself. check the event logs and do revert back.
Main Topics
Browse All Topicswe have an exchange 2003 server and after it was moved to a new location, every once in a while it will become unresponsive. This means that you can't ping it and e-mail will stop being sent and received, but otherwise the computer seems to be okay.
Only after a reboot will the exchange start to work again and become reachable via ping.
Does anyone know what might cause this and how it can be fixed?....without have to reinstall exchange again, etc.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
okay, the only things I can find in the event viewer for the same day that the connectivity problem happend were in the application log.
Event ID:1400 MSExchangeSRS
The Microsoft Exchange Site Replication Service could not initialize its Exchange database (EDB) and returned error 1. The Site Replication Service will wait in a semi-running state so the database can be restored from backup and the SRS can mount it.
---------
Event ID:2219 MSExchangeMTA
The MTA is running recovery on the internal message database because the MTA was not shut down cleanly. This operation may take some time. Status updates will be written to the Windows 2000 Event Log. [DB Server MAIN BASE 1 0] (14)
---------
Event ID:5008 MSExchangeSA
The message tracking log file C:\Program Files\Exchsrvr\JAWS.log\20
---------
All of these were just warnings though. I can't find anything critical in the event logs that seems to say something about why the connectivity would fail.
There were also another couple of warnings that said that the recovery of the MTA went successfully, but I didn't bother putting those in there.
I just didn't think it would be the patch cord because this is a very once in a while thing. It might be something like once every two weeks, so I thought the failure of a patch cord would be a little more frequent.
Business Accounts
Answer for Membership
by: gpriceeePosted on 2005-07-09 at 17:15:27ID: 14405300
Hi. By, new location, do you mean 10 feet, or do you mean another building? city?
xchange/do wnloads/20 03/ default .mspx
The reason is that a Global Catalog server might not be in the same site as the Exchange server anymore, or that the connection between the Exchange server and the GC is too slow. Other reasons could be network changes or failures. Is the patch cord new? Is the speed of the switch different? Is a different DNS server at the new location? Is the server on another VLAN? Does it have a hosts file?
I'd start with the easy things first . . . patch cord, event log, connectivity between the Exchange box and the GC, nslookup. Then, I'd go for the hard things: http://www.microsoft.com/e
go down about 2/3 and use the MTA check.
Hopefully, it's just something simple!