Exchange Server Forums

RE: RPC over HTTP frustration

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Outlook Web Access >> RE: RPC over HTTP frustration

Page: << < prev 1 [2]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

RE: RPC over HTTP frustration - 1.Feb.2005 8:28:00 PM

anonim

Posts: 34
Joined: 27.Jan.2005
From: US
Status: offline

GERob,

I am having the exact same problems that you had. I am on a single server with Win2003 and Ex2003, serving as DC and GC.

I am able to connect inside my network via TCP/IP even though I have both checkboxes selected to use HTTP(S).

Please throw out any other ideas you have.. thanks.

(in reply to GERob)

Post #: 21

Featured Links*

RE: RPC over HTTP frustration - 1.Feb.2005 8:46:00 PM

anonim

Posts: 34
Joined: 27.Jan.2005
From: US
Status: offline

quote:
Originally posted by GERob:

I've confirmed that in both my DC and EX server that we are set for 600# ports. I ran rpccfg /hr (or hd can't remember) and it shows the ports that are supposed to be used.

When I run "rpccfg /hd", which is supposed to display current port range settings, I get the following error:

"Error: Expected ':' in string '.
The command did not complete successfully.

I don't think this is expected behavior. Any suggestions?

(in reply to GERob)

Post #: 22

RE: RPC over HTTP frustration - 11.Feb.2005 12:28:00 PM

Guest

Hello everyone.
As I now has tried everything (a lot) I now has to resign. I really need some input here.
My configuration is as followed:
Single server Exchange on the inside of a firewall.
I have opened port 80, 443, 6001-6004 through the FW against the exchangeserver. The RPC over HTTP proxy is up and running on the exchangeserver.
The computer on the outside have the servername.domain.local in the hosts file and if I telnet the 600x ports the ncacn_http is answering.
The certificate for SSL is selfeissued and downloaded to the client-pc.
I can connect if I move the server out on DMZ. Then I can connect and make a local copy of the mailbox.
But when the server is back on the LAN I get several enties in the FW log with traffic on the port 135. If I open that port I get traffic on port 1047 or another high port. But I have learned that the ports should be fixed to SSL(443) and 6001-4

What can be the problem here?

Btw since everything works with the server on DMZ I do not think the problem is DNS related. The traffic is going to the right place but not on the right ports.

Luke of Norway

(in reply to GERob)

Post #: 23

RE: RPC over HTTP frustration - 12.Feb.2005 2:07:00 PM

Guest

Hurray.

Now it's working.
An article at: http://www.kuhnline.com/index.php?id=51 told me the importanse of making the SSL certificate in the right way.
I followed this and everything is allright now.
I think Outlook client defaults to port 135 if there's no trust with the server.

(in reply to GERob)

Post #: 24

RE: RPC over HTTP frustration - 2.Mar.2005 1:31:00 AM