RPC over HTTP wont work after reinstall of IIS and Exchange 2003
I have been running RPC over HTTP fine (without certificates) for the last two years on my standalone 2003 Server Standard w/Exchange 2003 Enterprise SP2. Last night my exchange server experienced some SMTP problems which required me to reinstall IIS and Exchange 2003. I restored the metabase files in IIS and followed microsoft's instructions to restore the server. Everyhthing works fine (OWA, ActiveSync) except for RPC/HTTP. I get a password prompt but cannot login in like I normally did with my domain/username and P/W when i am off and on the network.
To troubleshoot I uninstalled the HTTP/RPC service then reinstalled the component, configured the virtual directories security permission as advised, and configured the registry keys using the RPCNOFRONTEND utility. Also configure ESM with the appropriate settings - still no dice.
Been working on this for hours and am going nuts trying to figure out what i am missing...Any suggestion would be much appreciated! I got this working before..not sure what is blocking it from working again....
Thanks,
-Travis
To troubleshoot I uninstalled the HTTP/RPC service then reinstalled the component, configured the virtual directories security permission as advised, and configured the registry keys using the RPCNOFRONTEND utility. Also configure ESM with the appropriate settings - still no dice.
Been working on this for hours and am going nuts trying to figure out what i am missing...Any suggestion would be much appreciated! I got this working before..not sure what is blocking it from working again....
Thanks,
-Travis
What happens on the remote client? Does it keep prompting for credentials when trying to connect?
ASKER
yes..its prompts repeatedly and it never accepts the credentials...on the LAN i can connect a client (that is not on the domain) to exchange but when i try to add the proxy server address it says it cant resolve the server...on the outside I use the same FQDN for both the server and the proxy (ctsindiana.dyndns.org) and it always worked..now when the prompt pops up it changes the domain to the NETBIOS NAME/USERNAME... weird....
I dont have any users on the LAN so I have been cocentrating on getting this work from the WAN side....does this help you out?
I dont have any users on the LAN so I have been cocentrating on getting this work from the WAN side....does this help you out?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.