cant reconnect after server restart 2

[Amboyduke]

We've been having an ongoing issue with 2 laptops with regards to the Outlook Client connection. They will work fine until we reboot the Exchange Server in the mornings. After Exchange comes back on line these two laptops will not recover the connection to Exchange. Closing and re-opening Outlook does not work. Rebooting the Laptops may work after one, two, etc. tries; it's a "crap shoot". Anyway, the only way to correct it is to temporarily disable either the Wireless or Hard LAN and then reboot the laptop. After that you can re-enable one or the other and all works fine until randomly the next time." This obviously is not want we want to have to do all the time. Any thoughts or suggestions. The text in qoutes is the email that my IT Manager sent to me.
Any help would be greatly appreciated.

 

[Davetoo]

First...why are you rebooting your Exchange servers every morning?

Troubleshoot the connection. After the server is rebooted, can you ping the server by IP? FQDN?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[Amboyduke]

As a side note. The reason for rebooting the exchange server everynight is because for whatever reason OWA will not work unless the server is rebooted every morning. This is an issue that started before my coming to work at this job. The IT manager has not had time to set down and find the problem. Any thoughts on it would be a plus.

 

[Amboyduke]

We may have found a solution. On MS website they had a article on computers using hard wired and wireless connections at the same time and the possible problems it might cause with certain progrmas. It said to go in and set the binding order to the preferred connection. In this case would be the LAN, since they use their laptops in docking stations.

 

[Davetoo]

If they are using wired docking stations, then disable the wireless while in the office.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[TechyMcSe2k]

As far as the OWA, try restarting IIS, in command prompt it is IISRESET and you can script and schedule it, instead of rebooting the whole server until you research your logs and resolve the issue.

 

[Zelandakh]

iisreset /noforce is nicer on the server but I agree that restarting each morning is not recommended or natural.

 

[TechyMcSe2k]

OK, Stars needed. for some of us. We saw your repost... and you pretty much got the same answer. I'll start with Zelandakh.

 

[Zelandakh]

I have given a star to Techy as well. Keep up the great work you are doing on this site.