Activesync problems

[aquila125]

Hi all,

we have an exchange 2003 installation (SP2) and try to connect with a handheld device with mobile 6 on it. We keep getting eventid 3005 in the eventlog and the synchronisation fails every time.
I already created the exchange-oma vdir, checked all of the permissions (basic auth, no ssl) but it still doesn't work..

Does anyone know what else I can try?

Thanks!

 

[MarkArnold]

There are a lot of possibles unfortunately.

http://www.eventid.net/display.asp?eventid=3005&eventno=2656&source=Server ActiveSync&phase=1

is not a bad place to start. Have a look to see what you can exclude.

 

[aquila125]

I already checked most of these.. but still no succes :'(

 

[MarkArnold]

Is this all accounts?
"Most"? But you haven't checked all?

 

[aquila125]

Currently only our CEO is using the activesync option. I'll recheck all of the items on the eventid.net site and let you know.

 

[aquila125]

We found the problem!

Our exchange server has 2 nic's (LAN and OOB). IIS was only listening on the LAN interface, but the exchange-oma was using the OOB interface IP address to connect. So we added the OOB IP to the default website of IIS and all worked well...

 

[hanoirocks]

Another work around is setting up a gmail account and do a forward option.

Under Exchange active users and computers, go to the account you want configured. Go to the properties on the user account,
Go to Exchange General/Delivery Options, Check forward to and put in gmail address and also check "deliver messages to both forwarding address and mailbox.

This is an easy work around if you don't want the hassle.

You'll also need to add that gmail addy as a "new contact" in exchange beforehand.

 

[MarkArnold]

Hmmm. Your Exchange server should only have one NIC (or a pair in a teamed config)
You only need the internal IP address on it. Any external IP address should be on the firewall or router or whatever and then you do port forwarding to send the right protocols to the necessary server(s).

 

[aquila125]

The Exchange server has one internal IP (LAN) and one IP for a seperate network (Out Of Band) which we use to monitor/maintenace our servers and to take backups. All of our servers are behind firewalls

 

[MarkArnold]

Ahhhh, that's ok then (almost). Your problem is that the Backup LAN card is talking on the main network.
It must be on a separate physical network (otherwise there's no point in having it) and on a completely separate subnet. Also the network configuration needs to have everything unticked (file sharing, MS client etc. etc) and for it not to be reporting itself to DNS.

 

[aquila125]

It is a complete seperate network (different IP range), but it does allow file sharing and stuff. We could disable that.. that's true..