[wangel88]

As a note: On this new install of Server 2003 R2, BES is NOT installed yet!

And now:


Ok guys ... I have a REAL brain buster. I've exhausted all of my knowledge and I've called Blackberry support. They could not find a fix and simply told me "Good luck".

Here's the deal. I've installed 2 different machines with server 2003 R2. My goal is to setup a BES Server.

Here's my environment.

Srv1 -- Running Server 2008 64 bit, GC etc ... my main server
Srv2 -- Running Server 2008 64bit, Exchange 2007. Member server
Srv3 -- Runing Server 2003 R2. Nothing is installed on this box, it's a fresh install

Srv1 has Backup Exec, and I've installed the Mapi client + CDO on my exchange server, Backup exec is backing up mailboxes correctly as far as I can tell. So Mapi is working

On Srv3, after a brand new fresh install of 2003 R2, I download the Mapi client it, install it. I download MFCMAPI to test. I create a new profile. MfcMapi HANGS. Eventually, after about 10minutes, it will error saying there are communication problems connecting to exchange.

I have multiple (50+) machines, all of them running outlook 2003 and I have no problems with them connecting to exchange. I can setup besadmin on another machine, with outlook installed, and it will connect and resolve the mailbox fine.

One interesting note is if I add the GC under Exchange server when setting up the profile, click Check Name, it will resolve and underline everything and change the server to srv2. This is correct, however mfcmapi will hang. It's almost like a mapi problem on server 2003. I can't pin point it.

On the exchange server, the mapi32.dll files in windows\system32 and windows\syswow64 are ver 1.0.2536.0 Product version: 6.0.6000.16386

On my server 2003 R2 server, the mapi32.dll file in windows\system32 is: 1.0.2536.0 Product Version 5.2.3790.3959.

I've followed Blackbery instructions I don't know how many times. Same for the guide Gary Cutri typed up.

I'm at a loss. I don't think it's a problem with BES ... but a Mapi problem somehow?

Any ideas. Like I said I've exhausted ALL of my knowledge and resources. I've spent 2+hrs on the phone with BES and they are at a loss.

Could it be Message Block signing problems with 2003 vs 2008? I don't know =(

Thanks guys!

[knottyrope]

Is srvr 3 joined to the domain?

[wangel88]

Yes, srv3 is a member server.

Dns works ... I can ping the server

I've gone as far as adding this to the hosts file

172.16.30.9 srv2 srv.name.local

I've tried EVERYTHING =(

[bulletooth]

do you have all the permissions set for your BESadmin account on both the Exchange Server and SRV3 - the soon to be BES.

Also, Is this BESadmin account a member of any Windows Domain admin groups?

Are you using the same install for the CDO stuff for both the Exchange box and the BES?

Are you running the BES install under your intended BES admin account?

Are there firewall rules blocking ports between the BES and the Exchange box?

Also- Is the BES admin Account hidden in the GC?

I'd go back the BES install guide and verify each step again.

Your setup is something similar to mine except that my Backup Exec isn't running on a DC/GC

[wangel88]

Update:

Installed server 2008 on the box that had server 2003. Mapi works. Of course, BES will not install on Server 2008 =(

Installed Server 2003 X64 (64 bit, not 32, read this close). Mapi DOES not work.

So .... here's a few things I've come to conclude

1) When inserting the 2003 R2 box into the domain (rclick computer, computer name, change ... when I typed in my domain in Netbios form (DOMAIN) it errored out and said it could not find a DC. Typing in the FQDN worked find (DOMAIN.LOCAL). Could this be a DNS issue? Maybe ... but why do the other 150 client pc's and the 1 2008 server I tested with mapi work?

2) I believe it to be a mapi problem with 2003 r2. I don't know how. Maybe the latest Exchangemapicdo.exe file from MS is busted on 2003 R2? I've tried finding an older version for testing but can't seem to find it anywhere.

Does anyone, ANYONE have my setup.

SRV-1 : 2008 64bit GC
SRV-2 : 2008 64Bit running Exchange 2007
SRV-3 : Server 2003 R2 ... connecting to Exchange 2007 with mapi and working 100% ??????

Please, someone help me =(

[CanuckBB]

A domain join request that responds to FQDN but not NETBIOS name usually is a sign the the computer is not in the broadcast domain of the DC. Are the servers on different subnets?

[Harry Azol]

Originally Posted by wangel88

Does anyone, ANYONE have my setup.

SRV-1 : 2008 64bit GC
SRV-2 : 2008 64Bit running Exchange 2007
SRV-3 : Server 2003 R2 ... connecting to Exchange 2007 with mapi and working 100% ??????

I unfortunately have no suggestions, but I do have a similar setup to the above
08 x64 multiple GC + DC
08 EXC 07 (single server x64 of course)
03 R2 BES

[marduo]

Try disabling Autotuning.

Description of the Receive Window Auto-Tuning feature for HTTP traffic on Windows Vista-based computers
Description of the Receive Window Auto-Tuning feature for HTTP traffic on Windows Vista-based computers

[TargetIT]

So Server 3 with W2K3R2 - is that 32 or 64 bit you've installed? And if it's 64, any reason why?

[KaniGT5]

wangel -

Ive got a much similiar setup to you right now, Only my 2008 DC is 32bit, and I have another (you could even call it a backup) that is 2003 32Bit.

I have Exchange 2007 on Srv2008Std (Both 64Bit)

I am installing BES on a Server2003 (32bit box) (NON-R2) and the MAPI profile / setup went smooth as butter, found and verified my new exchange box no problem.

Not working 100% yet - as I am having some issues w/ pending delete users staying - and being unable to pinpoint and remove the databases.

Although If I do get this up and running 100% I will keep you posted on what I've done.

Perhaps if your product key is a VLC from Microsoft? maybe if you called them they would be able to make an exception from R2 to just Standard.