Exchange 2007 and windows server 2008

I am using Windows 2008 Server with Exchange 2007, every thing has been working godd, but after about 4 months of working fine, the outlook 2007 clients form remote are asking for login usernames and passwordd.

The client can enter the correct username and password but exchange will not connect. Give the server about an hour or two and they will start connecting like normal with no problems. This is only effecting the external users, internal users are not having the issue I cannot find anything in the event logs nor the server settings that would cause this problem. When the problem is happening the users can log into the OWA and work with no problems, and authenticate with no prblems, but the outlook clint will not.

Who is Participating?

is this affecting all outlook clients, or only a few? When someone with a problem is trying to authenticate, have you ran outlook /rpcdiag to see if the clients are where the problem is? Anything in the app logs for a client pc?

Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.

That is what is meant to happen. The /rpcdiag switch simply runs Outlook in the usual fashion, but the second popup is just a box showing troubleshooting information, so we can see where the exact problem is. You need to login using the usual method (this must be done anyway) and then the part the RPC fails on will be reported in the RPC Diagnostics popup, and you can post a screenshot here for us to take a look at.

Hmm... don't seem to see any screenshot I'm afraid - I guess you missed it?! :(

0

geekalternativeAuthor Commented: 2008-10-08

Sorry, it did not seem to attach where i wanted it to. I am waiting on Microsoft to call me back, but i have noticed that i am getting an event id 24 and 18 on the server if this helpes anyone, then this morning i started getting a id 1058, i have made no changes to the system at this time, but it seem to be getting worse.

It sounds like something quite serious. Are Microsoft calling back today?

0

geekalternativeAuthor Commented: 2008-10-14

Ended up being the rpcproxy.dll was causing all the problems, once i removed it and put it back the server is now working fine with no problems, thank you for all the suggestions, microsoft is the one the gave the solution, but caos 275.00