• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 593
  • Last Modified:

Can't connect to exchange, site lost internet connectivity

I have a facility that has lost power & internet connectivity due to hurricane Isaac. The power came back (still no internet) and now when clients (win 7 & XP) open their Outlook 2007, it prompts them for login credentials, and then won't connect to exchange (SBS2011). I've attached a pic of the exchange services running on the server. The clients have no problem accessing file shares on the server. I don't know if the internet connectivity issue is causal or coincidental, but I was hoping someone might have some ideas.
0
msatterlee
Asked:
msatterlee
2 Solutions
 
Nagendra Pratap SinghCommented:
I cannot see a pic attached!
0
 
markcharletonCommented:
A few questions first...

Can you ping the FQDN of the server on the lan? eg sbs2011.mydomain.local
Can you ping its IP directly from a client machine on the lan?

Have you run outlook.exe /rpcdiag from the Run command dialog box? This should give you an idea of if it is connecting or failing.

If you control + right click the outlook icon in the system tray by the cocl you will have an extra option of "test outlook connectivity" - Hit this and it will run through a series of tests and give you results. If you cant work out from this, post the results and i'm sure we can  all have a look and see.
0
 
Sumit GuptaCommented:
If you have different domain controller then reboot first Domain controller and then Exchange server. This might help..
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
msatterleeAuthor Commented:
Here's a second attempt to attach a picture of the running services.

The domain controller and the exchange server are the same server.

I'll go over an try your suggestions, mark charleton, and get back with you.
Exchange-services.jpg
0
 
markcharletonCommented:
What version of exchange are you running? i know 2007 has an issue if you have less than 4GB of space available on the installation drive then the transport service shows as started but crashes in itself. Though i think this was fixed with SP1.
0
 
msatterleeAuthor Commented:
Ok, I got connectivity restored to the facility, everyone can browse the internet now, but the inability to connect to exchange remains. To answer the ping questions, Mark, I could ping the server IP and the servername, but I couldn't ping FQDN (servername.domainname.local). This got me poking around, and I found that the client PCs were configured with static IPs that were pointing to the old server as their DNS. I changed one PC's static IP to have the new server as it's DNS and another PC I converted to dynamic IP (which accomplished basically the same thing) . Both PCs now, when you open Outlook, give the following error:

Cannot start Office Outlook. Cannot open the outlook window. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance.

Where as before, outlook would open and in the lower right it would report "disconnected".

The version of exchange is 2010, I'm running on a SBS2011 server, which is also the domain controller.

The other thing I should mention is that this is a new server that we just migrated from a SBS2003 server. The email has been functioning fine for the past 3 weeks or so.

I also check the space on the installation drive, and it has plenty of space. That issue happened during the migration 3 weeks ago, the log files filled the C: drive on the server and stopped the send/receive capabilities of the server, but we resolved that.

I also rebooted the server to see if that would help, but it didn't. When I ran the Outlook /rpcdiag it showed that it established directory connection, but the mail connections fail.
0
 
msatterleeAuthor Commented:
Ok, It's fixed. The problem ended up being the RPC Client access service wasn't starting. I started it and the outlook on the client PCs connected.
0
 
msatterleeAuthor Commented:
I'm putting my comment as the solution because the solution wasn't suggested by other comments, however markcharleton got the ball rolling in the right direction, so I'm awarding the points to him. <br /><br />Thanks for everyone's efforts though.
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now