RE: RPC over HTTP: - Problems accessing from outside our network.
- From: "Lloyd Williams" <Williams@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Sun, 3 Apr 2005 14:05:24 -0400
Yes that is the case
________________________________
From: Ara [mailto:ara@xxxxxxxxxxxxx]
Sent: Sunday, April 03, 2005 1:53 PM
To: [ExchangeList]
Subject: [exchangelist] RE: RPC over HTTP: - Problems accessing from
outside our network.
http://www.MSExchange.org/
Hi
Is your external registered domain differs from internal? Domain.local
and domain.com scenario?
________________________________
From: Lloyd Williams [mailto:Williams@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Sunday, April 03, 2005 10:27 AM
To: [ExchangeList]
Subject: [exchangelist] RE: RPC over HTTP: - Problems accessing from
outside our network.
http://www.MSExchange.org/
The microsoft example for how you configure the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy
ValidPorts registry key says:
the Value data box, should have:
ServerNETBIOSName:6001-6002;ServerFQDN:6001-6002;ServerNetBIOSName:6004;
ServerFQDN:6004
Initially I had my external FQDN in the value ServerFQDN
and I did not work internally. I changed it to my internal FQDN then it
worked internally
How would I edit this registry key to include both the internal and
external FQDN?
________________________________
From: Michael B. Smith [mailto:michael@xxxxxxxxxx]
Sent: Sunday, April 03, 2005 12:54 PM
To: [ExchangeList]
Subject: [exchangelist] RE: RPC over HTTP: - Problems accessing from
outside our network.
http://www.MSExchange.org/
you probably don't have enough entries in the rpcproxy registry key. you
need one for the netbios name, one for the internal dns name, and one
for the external dns name. i think that all the microsoft examples
assume that the internal dns name and the external dns name are the
same. The external DNS name must be the name for which the SSL
certificate was issued.
it is expected behavior for the Control Panel -> Mail -> E-mail account
to have the internal DNS name, after it has been resolved. It means you
are probably pretty close. :-)
________________________________
From: Lloyd Williams [mailto:Williams@xxxxxxxxxxxxxxxxxxxxxxx]
Sent: Sunday, April 03, 2005 12:22 PM
To: [ExchangeList]
Subject: [exchangelist] RPC over HTTP: - Problems accessing from outside
our network.
http://www.MSExchange.org/
I have a single server Exchange 2003 running on Server 2003.
I am having problems getting rpc over http working from home.
The configuration works from inside our network as I use Outlook
/rpcdiag and I see outlook connects as HTTPS.
However from outside the network I just get a server unavailable
message.
I have a feeling the problem is that the outlook client is trying to
access the server with the internal DNS name.
When I set up the outlook client the internal DNS A record pops up in
the client control panel.
I would have though the solution would be to put entries for the
internal DNS name in the client hosts file but this doesn't seem to
work. Even though I can access OWA over SSL using the internal DNS name
in the host file. So that indicated name resolution is going OK
Does any one have any suggestions
Thanks
Lloyd Williams
-
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
williams@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
Other related posts:
