Hi Guys, I have ISA 2004 and Exchange 2003. I am trying to get RPC over HTTP working correctly. I have published Exchange 2003 and OWA and Active Sync are working fine. However, i get the following error: Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) Now. I have attempted to telnet to this port locally on the Exchange machine. I cannot connect. I can connect on 6001, 6002, 6003. Is this normal? I have run the program NORPCFRONTEND. The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. Doing a netstat -ano on the exchange server I can only see the following ports listening: TCP 0.0.0.0:6001 0.0.0.0:0 LISTENING 5524 TCP 0.0.0.0:6002 0.0.0.0:0 LISTENING 4500 Current proxy registry key: server:6001-6002;server.internal.server.co.nz:6001-6002;webmail.server.co.nz:6001-6002;server:6004;server.internal.server.co.nz:6004;webmail.server.co.nz:6004 What should I be looking at next?

Where did you get this Exchange 2004? Where are you getting this error message? If it's in the event log, please post the entire event log entry. You can use the handy-dandy copy-to-clipboard button to help with that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Where did you get this Exchange 2004? Where are you getting this error message? If it's in the event log, please post the entire event log entry. You can use the handy-dandy copy-to-clipboard button to help with that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Sorry, typo, Exchange 2003 :) This error is from the exchange connectivity test (website).

Sorry, typo, Exchange 2003 :) This error is from the exchange connectivity test (website).

Were you running this for a reason? Clients can't connect?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Correct.

Were you running this for a reason? Clients can't connect?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Correct.

In general, it's recommended you use RPCPing for troubleshooting this kind of problem. You might start inside your network, then outside. If it works inside and not outside, then you probably have a firewall and/or ISA problem. Like, is there a rule allowing 6004 into your netowrk? Are you using ISA to publish Outlook Anywhere, or just as a firewall? Those kinds of questions need answers for you to know what's going on.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

In general, it's recommended you use RPCPing for troubleshooting this kind of problem. You might start inside your network, then outside. If it works inside and not outside, then you probably have a firewall and/or ISA problem. Like, is there a rule allowing 6004 into your netowrk? Are you using ISA to publish Outlook Anywhere, or just as a firewall? Those kinds of questions need answers for you to know what's going on.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes, but I can't even telnet locally on the exchange server to port 6004... rpcping isn't going to work.

Yes, but I can't even telnet locally on the exchange server to port 6004... rpcping isn't going to work.

Hi infused, The registry key is setup correctly though the external domain is not required. Please add below entry on Global Catalog server and then REBOOT to apply the change: HKLM\System\CurrentControlSet\Services\NTDS\Parameters - Type: REG_MULTI_SZ - Name: NSPI interface protocol sequences - Value: ncacn_http:6004Fiona

Fiona; Does this reg entry (ncacn_http:6004 apply to win2k8r2/exchange 2010 environments? I haven't found any official documentation pointing to it. Thanks.Ernesto

Fiona; Does this reg entry (ncacn_http:6004 apply to win2k8r2/exchange 2010 environments? I haven't found any official documentation pointing to it. Thanks.Ernesto