3. I found a Microsoft article referencing the same problem with OL 2007 http://support.microsoft.com/kb/913843/en-us  In this article, it said to add an dword entry into the registry for Office\12.0\outlook\RPC. There was no RPC keyword under 11.0\Outlook so I tried to create one and that didn't fix the problem.

 

Luckily for my company, I am the guinea pig with Vista Business and I was debating whether to install Office 2007 on this machine or stick with 2003 for the time being. We really didn't want to invest the bucks into 2007 just yet, but unless someone has a solution, we are in trouble.

 

FYI: I am planning to migrate away from SBS and jump into Exchange 2007 on a hosted server, not sure if that will solve this problem, but I doubt it.

 

 

Thanks,

-Brian

Thanks, Michael.

 

I forgot to mention that in my post, but I did install the server certificate into the trusted sites group using IE7. Now when I connect to OWA it does not give me the magenta warning.

 

But since I am a remote user and I don't have a VPN connection to the SBS server, I don't know how to install the local cert. Perhaps I can create one like we did for the public cert?

Hi,

 

Problem solved for me. It turns out that this server had never been SP for both 2003 and and SBS 2003. So applied the patches as outlined in the wonderful guide from this site for applying SBS2003 SP1 (which requires many other patches to be installed first and in one hit so to speak).

 

Really should have checked this out first but, my mistake.

 

Cheers

 

Paul

My solution is different, but it worked for me:

 

After following the steps in the knowledge base article, outlook on my vista machine connected!

http://support.microsoft.com/default.aspx?scid=kb;EN-US;899148
 
(Note that this KB article was updated on June 27, after I reported the problem. It's not easy being in the bleeding edge ;-)
 
Here are the steps I took for your reference as we roll out new machines (although once we migrate to VIA this may not be as critical).
 
1. Click Start, click Run, type regedit, and then click OK
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc
3. Click the Edit menu, point to New, and then click DWORD Value. 
4. Type Server2003NegotiateDisable as the name of the new DWORD Value
5. Right-click Server2003NegotiateDisable, and then click Modify.
6. In the Value Data box, type 1, and then click OK.

Note This setting disables the bind time negotation and multiple transfer syntax negotiation.
7. Quit Registry Editor. Restart the computer.
8. After the firewalls and VPN devices are compatible with RPC on the computer, set the value for the Server2003NegotiateDisable entry in the registry to 0. Then, restart the computer.

 
Note: they also suggested the following although since I was successful after these 8 steps, I did not do this one:
 
Step 2: Please DisableTaskOffload on Vista machine.

1. Open the Registry and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

2. Add a new DWORD value named DisableTaskOffload and set it to 1.

3. Restart the system to make these changes take effect.

 

Glad this is checked off my list!

-Brian