RPC over HTTP - have you gotten it to work?

[Bill Hobson]

I have followed KB833401 to the letter, but no luck on getting it to work. I
have verified the server side (at least according to the article), but it
still won't connect. Has anyone found out some magic to make it work?

 

[neo [mvp outlook]]

I think the step below is misleading. Make sure you perform step 2 on all
Global Catalog servers that Exchange 2003 looks to. (This registry edit
does not apply to workstations or member servers since they do not hold a
copy of the NTDS [aka Active Directory/Directory Store]) And for what its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over HTTP for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

 

[Bill Hobson]

OK, I finally got it to work (soft of). It takes a very long time to sync
and the diags show that it is still trying to use a server that is no longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other than the
ones in the article and the Exchange 2003 Deployment Guide that might have
influence over this? On the Exchange 2003 server, I did set the keys as in
the Deployment Guide, page 179-180 (HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443 open and
the DC/GC set as the RPC proxy server and GC, with no ports open through the
firewall..

Is there something else I am missing?

I think the step below is misleading. Make sure you perform step 2 on all
Global Catalog servers that Exchange 2003 looks to. (This registry edit
does not apply to workstations or member servers since they do not hold a
copy of the NTDS [aka Active Directory/Directory Store]) And for what its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over HTTP for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

I have followed KB833401 to the letter, but no luck on getting it to

work.

I
have verified the server side (at least according to the article), but it
still won't connect. Has anyone found out some magic to make it work?

 

[neo [mvp outlook]]

Go into the Exchange System Manager. Highlight your Exchange server object
and select properties. From memory, I believe there is a Directory Access
<?> tab. Choose Global Catalog servers from the dropdown list and see if
the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

OK, I finally got it to work (soft of). It takes a very long time to sync
and the diags show that it is still trying to use a server that is no longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other than the
ones in the article and the Exchange 2003 Deployment Guide that might have
influence over this? On the Exchange 2003 server, I did set the keys as in
the Deployment Guide, page 179-180 (HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443 open and
the DC/GC set as the RPC proxy server and GC, with no ports open through the
firewall..

Is there something else I am missing?

I think the step below is misleading. Make sure you perform step 2 on all
Global Catalog servers that Exchange 2003 looks to. (This registry edit
does not apply to workstations or member servers since they do not hold a
copy of the NTDS [aka Active Directory/Directory Store]) And for what its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over HTTP for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

I have followed KB833401 to the letter, but no luck on getting it to

work.

I
have verified the server side (at least according to the article), but it
still won't connect. Has anyone found out some magic to make it work?

 

[Bill Hobson]

Well, as of last night I got it to stop looking for the old GC - it turned
out that the Exchange 2003 server still had the LDAP key in the registry
that pointed to the demoted server.

Despite that change, Outlook tried to go to a DC that was not listed in the
HKLM\ \Software\Microsoft\Rpc\RpyProxy, so today I have added all of the GCs
to that list of ports to see if that speeds things up.

I spent several days beating my head against the wall trying to remember
where the Domain Controllers list was and you mentioned it in this note!
Thanks! The DC/GC listed as the Domain Configuration Controller is the
first thing contacted by the Outlook client, so adding it the the registry
key above may help.

Thanks a bunch for your help! I probably would still be spinning my wheels
if your hadn't taken the time to respond. I hope this is a good resource for
others facing these problems getting it to work!
I will test again this evening and we will see if all is well now. I sure
hope so...

Go into the Exchange System Manager. Highlight your Exchange server object
and select properties. From memory, I believe there is a Directory Access
<?> tab. Choose Global Catalog servers from the dropdown list and see if
the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

OK, I finally got it to work (soft of). It takes a very long time to sync
and the diags show that it is still trying to use a server that is no longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other than the
ones in the article and the Exchange 2003 Deployment Guide that might have
influence over this? On the Exchange 2003 server, I did set the keys as in
the Deployment Guide, page 179-180 (HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443 open and
the DC/GC set as the RPC proxy server and GC, with no ports open through the
firewall..

Is there something else I am missing?

hold

a

copy of the NTDS [aka Active Directory/Directory Store]) And for what its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over

HTTP
for

directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.


I have followed KB833401 to the letter, but no luck on getting it to work.
I
have verified the server side (at least according to the article),

but
it

still won't connect. Has anyone found out some magic to make it work?

 

[neo [mvp outlook]]

Your welcome and once you get the kinks worked out, would love to hear how
you like RPC/HTTPS connectivity.
--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

Well, as of last night I got it to stop looking for the old GC - it turned
out that the Exchange 2003 server still had the LDAP key in the registry
that pointed to the demoted server.

Despite that change, Outlook tried to go to a DC that was not listed in the
HKLM\ \Software\Microsoft\Rpc\RpyProxy, so today I have added all of the GCs
to that list of ports to see if that speeds things up.

I spent several days beating my head against the wall trying to remember
where the Domain Controllers list was and you mentioned it in this note!
Thanks! The DC/GC listed as the Domain Configuration Controller is the
first thing contacted by the Outlook client, so adding it the the registry
key above may help.

Thanks a bunch for your help! I probably would still be spinning my wheels
if your hadn't taken the time to respond. I hope this is a good resource for
others facing these problems getting it to work!
I will test again this evening and we will see if all is well now. I sure
hope so...

Go into the Exchange System Manager. Highlight your Exchange server object
and select properties. From memory, I believe there is a Directory Access
<?> tab. Choose Global Catalog servers from the dropdown list and see if
the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

OK, I finally got it to work (soft of). It takes a very long time to sync
and the diags show that it is still trying to use a server that is no longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other

than
the

ones in the article and the Exchange 2003 Deployment Guide that might have
influence over this? On the Exchange 2003 server, I did set the keys

as

in

the Deployment Guide, page 179-180 (HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443

open
and

the DC/GC set as the RPC proxy server and GC, with no ports open

through
the

firewall..

Is there something else I am missing?

I think the step below is misleading. Make sure you perform step 2

on
all

Global Catalog servers that Exchange 2003 looks to. (This registry edit
does not apply to workstations or member servers since they do not

hold

a
copy of the NTDS [aka Active Directory/Directory Store]) And for

what
its

worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over HTTP
for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft
cannot guarantee that you can solve problems that result from using
Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click
Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

sent

to

 

[Bill Hobson]

Last question (I hope)! How long a delay between initiating the connection
and a working connection? After clicking Connect and then entering my
password, I have a 30 second delay and then get the Retry prompt and then
about 30 seconds later, I am in business. This is over a Cable Modem
connection (~128KBS upstream and 1MB downstream). Is this about what to
expect? Or do I need to keep looking for a sliver bullet?

Your welcome and once you get the kinks worked out, would love to hear how
you like RPC/HTTPS connectivity.
--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

Well, as of last night I got it to stop looking for the old GC - it turned
out that the Exchange 2003 server still had the LDAP key in the registry
that pointed to the demoted server.

Despite that change, Outlook tried to go to a DC that was not listed in the
HKLM\ \Software\Microsoft\Rpc\RpyProxy, so today I have added all of the GCs
to that list of ports to see if that speeds things up.

I spent several days beating my head against the wall trying to remember
where the Domain Controllers list was and you mentioned it in this note!
Thanks! The DC/GC listed as the Domain Configuration Controller is the
first thing contacted by the Outlook client, so adding it the the registry
key above may help.

Thanks a bunch for your help! I probably would still be spinning my wheels
if your hadn't taken the time to respond. I hope this is a good resource for
others facing these problems getting it to work!
I will test again this evening and we will see if all is well now. I sure
hope so...

see

if

the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.


OK, I finally got it to work (soft of). It takes a very long time to sync
and the diags show that it is still trying to use a server that is no
longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other than
the
ones in the article and the Exchange 2003 Deployment Guide that

might
have

influence over this? On the Exchange 2003 server, I did set the keys

as

in
the Deployment Guide, page 179-180 (HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443 open
and
the DC/GC set as the RPC proxy server and GC, with no ports open through
the
firewall..

Is there something else I am missing?

I think the step below is misleading. Make sure you perform step

2

on

all
Global Catalog servers that Exchange 2003 looks to. (This

registry
edit

does not apply to workstations or member servers since they do not hold
a
copy of the NTDS [aka Active Directory/Directory Store]) And for what
its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over HTTP
for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft
cannot guarantee that you can solve problems that result from using
Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click
Modify.
6.. In the Value data box, type ncacn_http:6004, and then click OK.
7.. Quit Registry Editor, and then restart the computer.

sent

to
this account will be deleted w/out reading.


I have followed KB833401 to the letter, but no luck on getting

it

to article),
but

 

[neo [mvp outlook]]

Good question and I guess it is always going to depend on what the network
is like between the client/server. From my experience from home/work, it
comes up right away w/ no retry prompt. When you configured the RPC/HTTP
settings, did you check both boxes dealing with connecting over HTTP first
then fall back to TCP/IP?

The reason that I ask is that Outlook will consider the broadband connection
as fast (always). From memory, anything less that 128kbit is considered
slow (read modem). Therefore if the box for fast is unchecked, Outlook
could be trying a standard RPC connection (gives the prompt) and then falls
back to HTTP/s. Might also consider switching to header only to see if it
makes a difference.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

Last question (I hope)! How long a delay between initiating the connection
and a working connection? After clicking Connect and then entering my
password, I have a 30 second delay and then get the Retry prompt and then
about 30 seconds later, I am in business. This is over a Cable Modem
connection (~128KBS upstream and 1MB downstream). Is this about what to
expect? Or do I need to keep looking for a sliver bullet?

Your welcome and once you get the kinks worked out, would love to hear how
you like RPC/HTTPS connectivity.
--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

Well, as of last night I got it to stop looking for the old GC - it turned
out that the Exchange 2003 server still had the LDAP key in the registry
that pointed to the demoted server.

Despite that change, Outlook tried to go to a DC that was not listed

in
the

HKLM\ \Software\Microsoft\Rpc\RpyProxy, so today I have added all of

the
GCs

to that list of ports to see if that speeds things up.

I spent several days beating my head against the wall trying to remember
where the Domain Controllers list was and you mentioned it in this note!
Thanks! The DC/GC listed as the Domain Configuration Controller is the
first thing contacted by the Outlook client, so adding it the the registry
key above may help.

Thanks a bunch for your help! I probably would still be spinning my wheels
if your hadn't taken the time to respond. I hope this is a good

resource
for

others facing these problems getting it to work!
I will test again this evening and we will see if all is well now. I sure
hope so...


Go into the Exchange System Manager. Highlight your Exchange server
object
and select properties. From memory, I believe there is a Directory Access
<?> tab. Choose Global Catalog servers from the dropdown list and

see

if
the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

sent

to other
than keys
as 443
open

step

2

on
all
Global Catalog servers that Exchange 2003 looks to. (This registry
edit
does not apply to workstations or member servers since they do not
hold
a
copy of the NTDS [aka Active Directory/Directory Store]) And

for
what

its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over
HTTP
for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause
serious
problems that may require you to reinstall your operating system.
Microsoft
cannot guarantee that you can solve problems that result from using
Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String
Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click
Modify.
6.. In the Value data box, type ncacn_http:6004, and then

click
OK.

7.. Quit Registry Editor, and then restart the computer.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent
to
this account will be deleted w/out reading.


I have followed KB833401 to the letter, but no luck on getting

it

to
work.
I
have verified the server side (at least according to the article),
but
it
still won't connect. Has anyone found out some magic to make it
work?

 

[Bill Hobson]

I have both checked and it still delays. I am going to go through all of the
registry settings again on the client, even though all of the check boxes
are right. There still has to be something going on to slow it down.

I do like the performance once I get connected. And the fact that if I do
have a VPN or in-office connection, it still works great without having to
re-configure makes it a win-win configuration. Now if I can just figure out
how to get rid of the pesky RPC delay...

Good question and I guess it is always going to depend on what the network
is like between the client/server. From my experience from home/work, it
comes up right away w/ no retry prompt. When you configured the RPC/HTTP
settings, did you check both boxes dealing with connecting over HTTP first
then fall back to TCP/IP?

The reason that I ask is that Outlook will consider the broadband connection
as fast (always). From memory, anything less that 128kbit is considered
slow (read modem). Therefore if the box for fast is unchecked, Outlook
could be trying a standard RPC connection (gives the prompt) and then falls
back to HTTP/s. Might also consider switching to header only to see if it
makes a difference.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.

Last question (I hope)! How long a delay between initiating the connection
and a working connection? After clicking Connect and then entering my
password, I have a 30 second delay and then get the Retry prompt and then
about 30 seconds later, I am in business. This is over a Cable Modem
connection (~128KBS upstream and 1MB downstream). Is this about what to
expect? Or do I need to keep looking for a sliver bullet?

Your welcome and once you get the kinks worked out, would love to hear how
you like RPC/HTTPS connectivity.
--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails sent to
this account will be deleted w/out reading.


Well, as of last night I got it to stop looking for the old GC - it turned
out that the Exchange 2003 server still had the LDAP key in the registry
that pointed to the demoted server.

Despite that change, Outlook tried to go to a DC that was not listed in
the
HKLM\ \Software\Microsoft\Rpc\RpyProxy, so today I have added all of the
GCs
to that list of ports to see if that speeds things up.

I spent several days beating my head against the wall trying to remember
where the Domain Controllers list was and you mentioned it in this note!
Thanks! The DC/GC listed as the Domain Configuration Controller is the
first thing contacted by the Outlook client, so adding it the the registry
key above may help.

Thanks a bunch for your help! I probably would still be spinning my wheels
if your hadn't taken the time to respond. I hope this is a good resource
for
others facing these problems getting it to work!
I will test again this evening and we will see if all is well now.

I
sure

hope so...


Go into the Exchange System Manager. Highlight your Exchange server
object
and select properties. From memory, I believe there is a Directory
Access
<?> tab. Choose Global Catalog servers from the dropdown list

and
see

if
the retired server is still showing.

There are also some client side keys you can check to see where Outlook
wants to go. Start with:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272290

it has links to other articles that might be helpful.

sent

to
this account will be deleted w/out reading.


OK, I finally got it to work (soft of). It takes a very long

time

to

sync
and the diags show that it is still trying to use a server that

is
no

longer
a GC - it was demoted several weeks ago and the mail server has been
restarted since then. Do you happen to know the registry keys other
than
the
ones in the article and the Exchange 2003 Deployment Guide that might
have
influence over this? On the Exchange 2003 server, I did set the keys
as
in
the Deployment Guide, page 179-180
(HKLM\Software\Microsoft\Rpc\RpyProxy)
for the proper GC.

My configuration has the Exchange 2003 server with ports 80 and 443
open
and
the DC/GC set as the RPC proxy server and GC, with no ports open
through
the
firewall..

Is there something else I am missing?

I think the step below is misleading. Make sure you perform

step

2
on
all
Global Catalog servers that Exchange 2003 looks to. (This registry
edit
does not apply to workstations or member servers since they do not
hold
a
copy of the NTDS [aka Active Directory/Directory Store]) And for
what
its
worth, RPC over HTTPS works great!

Step 2: Configure your computer to use specific ports for RPC over
HTTP
for
directory services
To do this, follow these steps:
1.. Start Registry Editor.

Warning If you use Registry Editor incorrectly, you may cause
serious
problems that may require you to reinstall your operating system.
Microsoft
cannot guarantee that you can solve problems that result from using
Registry
Editor incorrectly. Use Registry Editor at your own risk.
2.. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

3.. On the Edit menu, point to New, and then click Multi-String
Value.
4.. Name the new registry value NSPI interface protocol sequences.
5.. Right-click NSPI interface protocol sequences, and then click
Modify.
6.. In the Value data box, type ncacn_http:6004, and then click
OK.
7.. Quit Registry Editor, and then restart the computer.

--
Neo [MVP Outlook]
Due to recent events in spam and malicious programs, all e-mails
sent
to
this account will be deleted w/out reading.


I have followed KB833401 to the letter, but no luck on

getting
it

to
work.
I
have verified the server side (at least according to the article),
but
it
still won't connect. Has anyone found out some magic to make it
work?