Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Outlook  not connecting to to Exchange after switch failure

Posted on 2011-02-15
4
Medium Priority
?
1,172 Views
Last Modified: 2012-05-11
Hi Guys

We had a network failure caused by an unknown fault.  We diagnosed the system by restarting each of our switches as well as shutting down our non-critical servers.

Since then two of our 35 users cannot connect to our exchange server.  We are running Small Business Server 2003 with Exchange, and the user is using Windows 7 + Outlook 2010.  We can ping the Primary DC, and our Secondary DC.  Pinging the domain comes back with Sec DC's IP address.  We can force the domain to return the Primary DC's IP using the host file which works.  We have renewed the DHCP address as well as flushed the DNS.

All our other users can connect to Exchange no worries.

Any help would be appreciated.
0
Comment
Question by:lemonville
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 13

Accepted Solution

by:
BCipollone earned 2000 total points
ID: 34902540
Could always try flushing the ARP tables as well. Can you ping the exchange?... if You type Ping FQDN does it return the correct IP? IF not set the FQN and IP in the Hosts file.

Run outlook.exe /safe and see if it comes up and connects to the exchange. Make sure you check the mail profile to see how it is addressing the exchange server and be sure it can ping and resolve the correct IP for that server.
0
 
LVL 1

Author Comment

by:lemonville
ID: 34902827
Excellent, it would appear deleting the ARP Cache fixed it.  Any idea as to why that would happen? And to only one user?
0
 
LVL 13

Expert Comment

by:connectex
ID: 34902914
I've often had issues with ARP tables or/and DNS caching when swapping out switches or routers during business hours. The best option is to clear the table on each system or just to have the user's reboot their system if they have problems after the change.
0
 
LVL 1

Author Closing Comment

by:lemonville
ID: 34903364
Great solution, we should have known but we didn't change any switches, just turned a few off.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question