hamel01
asked on
RPC not connecting
I am trying to get RPC over HTTP to work. I have set up 3 or 4 of these systems and have not had ay issues untill now.
System info:
Server 2003 SBE R2
Single Server running Exchange
Cable Internet with static IP
OWA works perfectly using Forms based auth. with SSL. Outlook works fine inside but will not use HTTP. I have outlook set to use RPC and is set to use it on slow and fast conecctions but it will not use it. I have checked the registry keys for the port information. I have run through the IIS setting and have double checked the Router configuration and everyting seems to be in order. Does anyone have any ideas where to start trouble shooting? I have tried to use the RPC ping utility but have had no luck getting it to work. Any help would be apperciated!!
System info:
Server 2003 SBE R2
Single Server running Exchange
Cable Internet with static IP
OWA works perfectly using Forms based auth. with SSL. Outlook works fine inside but will not use HTTP. I have outlook set to use RPC and is set to use it on slow and fast conecctions but it will not use it. I have checked the registry keys for the port information. I have run through the IIS setting and have double checked the Router configuration and everyting seems to be in order. Does anyone have any ideas where to start trouble shooting? I have tried to use the RPC ping utility but have had no luck getting it to work. Any help would be apperciated!!
ASKER
for the RPC settings i have mail.server.com and msstd:mail.server.com i did not try the browsing. I am moving the server now and as soon as i get it back up i will try.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is what i am thinking also but what would be the explanation for it not working outside of the network? You are correct in saying it is failing over to TCP but when it is external, TCP is not an option. On the other systems i have, i have done this same thing with the split DNS. Since this is done internally would it really help the external connections?
So, do you have a name resolution problem?
Let's get it working inside, then worry about outside.
One thing I have seen in testing, is that IIS security CAN do stupid things. The SBS CEICWizard should configure it properly - have you been using the wizards on this server?
Let's get it working inside, then worry about outside.
One thing I have seen in testing, is that IIS security CAN do stupid things. The SBS CEICWizard should configure it properly - have you been using the wizards on this server?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK i have done the split DNS and i had run through the configuration wizard. Sorry i didn't mention that. I think i have narrowed the problem down to useing the home grown SSL cert. Because of it being home grown you get a error everytime you try to connect to the server websites. I am guessing this is causing the problem. I will get a verisign cert if that is the case but are there any cheaper ones that will not cause the error regarding a untrusted cert.?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can also install the certificate so that you do not get the prompt. Why you waited until now to tell us you were getting certificate errors, when I asked in my first post, is a little worrying.
ASKER
Well after all of this I have it working. It was a combination of the DNS and vertificate error. I'm sorry redseatechnologies that I did not write that earlier. It was late and I had been working on it for a while and it just slipped my mind. We could of done without your comment though, I am sorry that I am not as perfect as you are!
Welcome to the list
If it is something like server.domain.com, which it should be, then try browsing to https://server.domain.com/rpc and tell me what comes up.
There should be a username and password box (don't bother entering details) and NO certificate prompt. If you do not get that, then open the command prompt and ping server.domain.com - does it come back with your internal or external IP?