RPC/HTTP doesn't use the RPC application filter. Any "real" RPC traffic you see is a result of client misconfiguration. What is the client you're using (OS/SP/Office ver / patches)? Where is the client operating from; internal or external to ISA? ------------------------------------------------------- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/Jim_Harrison/ <http://isaserver.org/Jim_Harrison/> http://isatools.org <http://isatools.org/> Read the help / books / articles! ------------------------------------------------------- ________________________________ From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, February 22, 2005 13:14 To: [ISAserver.org Discussion List] Subject: RPC over HTTP problems Hi, I have setup RPC over HTTP along with OWA using Tom's Exchange / ISA info. Though I don't think there is any problem with his material I am having a problem wirh RPC. The OWA with SSL works flawlessly. When I setup the log in ISA to only look at the machine that we are using on the external side to connect to RPC over HTTP its able to negoicate with HTTPS on 443 without any problems but the RPC (all interfaces) id denied access by the default rule. I am wondering is there something else I need to set on ISA to enable the RPC protocol to work? Thanks Andrew All mail to and from this domain is GFI-scanned.