RPC/HTTP works only after first LAN connection

I've gotten RPC over HTTP to work for any client as long as I set it up
on the LAN first. These clients can then go out on the internet from
any connection and connect without any problems. Any client I try to
setup on the internet to use RPC over HTTP as the first connection it
fails. Running outlook.exe /rpcdiag shows two connections attempting
to go, but the connection method remains blank (doesn't show TCP/IP or
HTTPS).



Jason

.

Relevant Pages

  • Re: Mcafee FTP Mirror Sites and ISA Server 2004 Authentication
    ... Client IP: ... Destination IP: ... Protocol: http ... Action: Failed Connection Attempt ...
    (microsoft.public.isa)
  • Re: McAfee AV server Mirror Task fails authentication
    ... Client IP: ... Destination IP: ... Protocol: http ... Action: Failed Connection Attempt ...
    (microsoft.public.isaserver)
  • Re: proxy supporting HTTPS
    ... > I am implementing a proxy supporting HTTP and HTTPS. ... I found the first packet from the client is kind of: ... Are you saying that you were not able to establish a connection to the Host ...
    (microsoft.public.win32.programmer.networks)
  • Re: Detect File is Completely Download by Client
    ... > this has the minor hole, that the last write may not be received by the ... > client even though the server successfully sent it.. ... Unless the client needs to talk in HTTP 1.0 (extremely ... rare) or you're explicitly sending a 'Connection: ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: RPC/HTTP works only after first LAN connection
    ... on the LAN first. ... These clients can then go out on the internet from ... any connection and connect without any problems. ... setup on the internet to use RPC over HTTP as the first connection it ...
    (microsoft.public.exchange.admin)
Loading