• February 24, 2025, 08:07:37 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: ActiveSync to get through DFL-210 to Sync  (Read 5995 times)

sslloyd

  • Level 1 Member
  • *
  • Posts: 3
ActiveSync to get through DFL-210 to Sync
« on: January 02, 2010, 03:58:00 PM »
First off we have just changed out our router to a DFL-210 prior to this we were using a WBR-2310 and activesync to our exchange server was working fine.  Now with the DFL-210 receiving error 85010014 when trying to sysnc.  I just went back to the WBR-2310 to check and was able to sync no problem.

I believe I have opened TPC inbound 990, 999, 5678, 5721, 26675; UDP outbound 5679 but still will not sync.

Can steer me in the right directions as am new to the DFL-210 and not real sure if configurating this properly

Thanks

Bill
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: ActiveSync to get through DFL-210 to Sync
« Reply #1 on: January 04, 2010, 09:26:15 AM »
What log messages if any were generated by your DFL-210?
Logged
non progredi est regredi

sslloyd

  • Level 1 Member
  • *
  • Posts: 3
Re: ActiveSync to get through DFL-210 to Sync
« Reply #2 on: January 05, 2010, 04:43:47 AM »
Nothing showing up in log!
Logged

Fatman

  • Level 9 Member
  • ****
  • Posts: 1675
Re: ActiveSync to get through DFL-210 to Sync
« Reply #3 on: January 05, 2010, 08:31:39 AM »
Ok, why don't we just jump to step 11, PM me a link where I can download your config file and I will take a look see.
Logged
non progredi est regredi

sslloyd

  • Level 1 Member
  • *
  • Posts: 3
Re: ActiveSync to get through DFL-210 to Sync
« Reply #4 on: January 05, 2010, 09:06:42 AM »
Problem resolved, what it actually turned out to be was remote management was turned on on the router therefore even though I had opened up 443 and routed it to the exchange server the router was capturing this port to itself for remote management purposes.  Changed the router port to 444 and then everything started working on the exchange server side.  The whole exercise of opening the ports listed above was an exercise in futility.

Thanks for responding to my query though.

Bill
Logged