Crash in msmapi32.dllwhen adding an Exchange connection

Setup:
Outlook 2003 (with all current updates)
Exchange 5.5 (latest service pack)

Steps which cause crash:
- Add new mail account
- Select Exchange Server connection
- Insert server name and mailbox name
- Click 'next'

"Run a DLL as an App has encountered a problem and needs to close." etc.

AppName: rundll32.exe
ModName: msmapi32.dll
ModVer: 11.0.6361.0

It happens whether I do it via Outlook, or through the Mail icon in control panel. I'm completely stuck on this one. I've got no anti-virus software installed, and the rest of the machine was only built a few days ago, everything else works fine.

Any ideas much appreciated... I've posted this in the Exchange Server section too, just in case.
tjrobinsonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

travalCommented:
Are you on the LAN with the Exchange Server, or is a VPN or some other remote connection involved?

If you click START->RUN->"cmd" (w/o quotes) and type in "ping <servername>" (w/o quotes and substituting the server name for <servername>) do you get 4 times returned back?
tjrobinsonAuthor Commented:
There is a VPN involved. Local network is 192.168.0.* and the remote is 192.168.1.*

Pinging gap-pdc [192.168.1.2] with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time=194ms TTL=128
Reply from 192.168.1.2: bytes=32 time=40ms TTL=128
Reply from 192.168.1.2: bytes=32 time=42ms TTL=128
Reply from 192.168.1.2: bytes=32 time=65ms TTL=128

Ping statistics for 192.168.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 194ms, Average = 85ms

Thanks
travalCommented:
OK, we have a connection thru the VPN, so that's good.  Can you access other resources thru the VPN?

Have you tried a repair of Office?  If not try that by clicking HELP->DETECT&REPAIR.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

tjrobinsonAuthor Commented:
I can access other resources including HTTP traffic to the remote webserver/intranet as well as file shares. I'm pretty sure that side of things is working ok.

I've tried an Office repair as well as reinstalling Outlook (but leave the rest of Office as it is).
travalCommented:
Are you running Windows XP and if so do you have SP2 installed?  If not install that, there was a problem like this that was addressed by SP2.

Are you connecting via RPC Over HTTP?  Or just regular RPC?  There was another issue with Outlook 2003 where, when you tried to configure "more settings" before checking the name, it would check the name and fail because the "more settings" were'nt correctly configured.  This doesn't seem to be your scenerio, but thought I would mention it just in case and say I think it was fixed in Office 2003 SP1.

Do you have this regkey, and if so what does it contain?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols
tjrobinsonAuthor Commented:
I'm not at home at the moment so can't answer the last question, but...

1. I'm running XP SP2, but I don't have any way of downgrading as I used a streamlined SP2 CD to install XP.

2. I'm connecting directly to RPC, via the VPN.

3. I'll check the registry later.
tjrobinsonAuthor Commented:
I should probably add that before my recent reinstallation it was all working fine, SP2, same firewall client, same version of Outlook (fully patched).
tjrobinsonAuthor Commented:
I've got it working!

I decided to uninstall the NVidia ForceWare Network Access Manager (can't remember which version) and after a restart all seems to be working fine. I has the firewall disabled so I didn't think this was likely to be the cause of the problem but it seems it was. Although I'm using the Marvell Yukon adapter on my motherboard rather than the NVidia adapter it still seems to have caused a problem somewhere.
GhostModCommented:
PAQed with points refunded (500)

GhostMod
Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.