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

Clients with RPC over HTTPS non exchanged mode receive server unavailable message after server reboot

I have clients that I set up to use RPC over HTTPS in non Cached mode.  This was working fine until I rebooted the server.  Now I am getting all these calls about an erro stating the server is unavailable.  I enabled cached mode on a few of them and they connect fine again.  OWA works as well.  What happened and how do I get this working again, and always, with non cached exchange mode?
0
askstevehow
Asked:
askstevehow
1 Solution
 
ATIGCommented:
Its possible you have latency issues when you online mode, you really should utilize cache mode as it increases  performance drasticsly.

If this was a non issue before the reboot, did you install patches or update network drivers before the reboot?
0
 
askstevehowAuthor Commented:
I rebooted the server and everything was fine.  I checked the services before I rebooted and everything was started accordingly.  This one was a mystery...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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