lemonville
asked on
Outlook not connecting to to Exchange after switch failure
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
Great solution, we should have known but we didn't change any switches, just turned a few off.
ASKER