Require Passcode Immediately with Exchange 2003 and iPhone 3.0?

Before I upgraded to iPhone 3.0 I was syncing with Exchange 2003 SP2 and I had set my passcode to be required after 1 hour, which was changed from the default of 4 hours. On the Exchange server we have a policy in place to have a max of 12 hours before a passcode is required which works on my WM phones.
After upgrading to 3.0, the phone now immediately requires a passcode every time I turn it on. I went into the settings to change it to be a little longer, but the only option is to have it Immediately and I have lost all of the other options. Is there a way to get back at least 1 hour or something that reflects the 12 hour setting on my Exchange server?

I can confirm that you just need to turn OFF Mail, Contacts and Calendar sync within the Exchange account, set the timeout 4 hours (or whatever - it will automatically shrink down if your Exchaange administrator's policy is more restrictive), and then turn back ON Mail, Contacts and Calendar sync.
Note you'll get a scary warning that says all your Contacts and Calendar data will be deleted from the phone - Outlook users can ignore if you're syncing with Outlook, since it will re-sync when done.

Similar Messages

Exchange 2003 sp1 iphone 4(Logs inserted)

My iPhone 4 gets stuck while checking for e-mails from exchange server 2003 sp1. During that time in the iPhone configutation utility i see the below logs which is continious.
My iphone is on the corporate Wifi.
Could someone pls help.
Jan 25 14:28:06 unknown dataaccessd[54] <Notice>: 169470|EAS|Error|connection died with error Error Domain=ASHTTPConnectionErrorDomain Code=503 "The operation couldnt be completed. (ASHTTPConnectionErrorDomain error 503.)" 0x1e17f0
Jan 25 14:28:06 unknown dataaccessd[54] <Notice>: 169470|EAS|Error|ASFolderItemsSyncTask failed: Error Domain=ASHTTPConnectionErrorDomain Code=503 "The operation couldnt be completed. (ASHTTPConnectionErrorDomain error 503.)"
Jan 25 14:28:06 unknown dataaccessd[54] <Notice>: 169470|EAS|Error|Folder with id 2ce3707e3e43b240ba71254e97e7831d-6865c4 and title Calendar has failed to sync 9 time(s) in a row
Jan 25 14:28:08 unknown CommCenter[17] <Notice>: Client [com.apple.persistentconnection[dataaccessd,54]] is telling PDP context 0 to go active.
Jan 25 14:28:11 unknown bootpd[96] <Notice>: service time 0.000045 seconds
Jan 25 14:28:11 unknown bootpd[96] <Notice>: service time 0.000039 seconds
Jan 25 14:28:16 unknown wifid[30] <Error>: WiFi:[349180096.092950]: Client dataaccessd set type to background application
Jan 25 14:28:17 unknown bootpd[96] <Notice>: service time 0.000045 seconds
Jan 25 14:28:17 unknown bootpd[96] <Notice>: service time 0.000050 seconds
Jan 25 14:28:17 unknown bootpd[96] <Notice>: service time 0.000033 seconds
Jan 25 14:28:22 unknown bootpd[96] <Notice>: service time 0.000043 seconds
Jan 25 14:28:22 unknown bootpd[96] <Notice>: service time 0.000031 seconds
Jan 25 14:28:26 unknown bootpd[96] <Notice>: service time 0.000048 seconds
Jan 25 14:28:26 unknown bootpd[96] <Notice>: service time 0.000031 seconds
Jan 25 14:28:27 unknown bootpd[96] <Notice>: service time 0.000047 seconds
Jan 25 14:28:27 unknown bootpd[96] <Notice>: service time 0.000037 seconds
Jan 25 14:28:29 unknown profiled[189] <Notice>: (Note ) profiled: Idled.
Jan 25 14:28:29 unknown profiled[189] <Notice>: (Note ) profiled: Service stopping.
Jan 25 14:28:43 unknown bootpd[96] <Notice>: service time 0.000051 seconds
Jan 25 14:28:44 unknown bootpd[96] <Notice>: service time 0.000050 seconds
Jan 25 14:28:46 unknown bootpd[96] <Notice>: service time 0.000108 seconds
Jan 25 14:28:48 unknown bootpd[96] <Notice>: service time 0.000191 seconds
Jan 25 14:28:52 unknown bootpd[96] <Notice>: DHCP INFORM [bridge0]: 1,e6:ce:8f:b2:e9:49 <gfc-lp-0077>
Jan 25 14:28:52 unknown bootpd[96] <Notice>: ACK sent gfc-lp-0077 172.20.10.2 pktsize 300
Jan 25 14:28:52 unknown bootpd[96] <Notice>: service time 0.001809 seconds
Jan 25 14:28:52 unknown bootpd[96] <Notice>: service time 0.000051 seconds
Jan 25 14:28:54 unknown bootpd[96] <Notice>: service time 0.000054 seconds

You need to establish a VPN between your Iphone and the network where you work. I've just configure an Iphone to work with exchange 2003 and it can work. Your IT departement will pass a couple of hour to make this work. IF they currently have the ability and equipement to establish a VPN currently it can work.
The first step is to put a wireless router and disable its dhcp server and connect your network in the port 1, not in the internet port.
then your Iphone will connect to this wireless router with wifi. becoming a device on your network like your work computer.
If your IT departement have put to enable the mobile service on the exchange server (defaut setting), It will synch.
On the Iphone In the server field of the exchange configuration, I put servername.domaine.com (exemple exchange.apple.com) not the Outlook web access.
If it work by wifi inside your network, the next part is to configure the VPN...

I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

Office 2011 is not compatbile with Exchange 2003.
I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
http://answers.microsoft.com/en-us/mac

Running Unity with both Exchange 2003 and 2010?

My company is planning to upgrade from Exchange 2003 to 2010. We are
currently using Unity 7.0. We'd like to run the two in parrallel for a bit and take our time switching users over.
Now I've read that Unity can support Exchange 2010, but I haven't found anything about running Unity using both Exchange 2003 and 2010 in parrallel.
Is this something Unity can handle?

We're doing something similar, but we have an in-place Unity 7 and Exchange 2003 environment; we are putting some users from an org we support on an Exchange 2010 server, but do not want that to be the partner server (yet). The instructions seem to point you to making 2010 the partner; I'm wondering why Step 13 (of your link) we are uninstalling the Exchange Server 2003 System Management Tools, if it’s a mixed environment and 2003 will still be the partner server. I also saw somewhere that you don’t have to move the unitymsgstoresvc account to Exchange 2010 if you are in a mixed environment. Is that true? Thank you.

Outlook 2013 not compatible with Exchange 2003

Hello
Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
clients to 2013 version.
Microsoft, is this correct?!

If this post is hard to read, it's because of Dragonsoft!! (sometimes it is like auto-correct on the phone - "I said WHAT!??")
Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
Windows for which they are named. So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
package which could handle the intricacies of the licensing limitations on the SBS system.
SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version. You must purchase a new server, install the new SBS version, and migrate your
entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!) The whole process is rather daunting as not
all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
So off we went with our new installation of SBS 2003 R2. Then along came SBS 2008! I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware. (I was not going to get stuck in a hardware box that I could not replace
if I ever needed to restore the operating system due to a massive failure.) So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
that they modified, and even performed a little cleanup, after they performed their cleanup! I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false! I live in Texas, and the state of Texas DIR program has adopted standards which state that
you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional! Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
from, anyway?)
One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs.
I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
If you allow a client to be painted in a corner, then it's not their fault, it's your fault! Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
they are unwilling to spend money. You don't work for free.
One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well. I put it like this, "You pay me to make certain that your business operates in good times and in
bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully. The equipment that we have operating here is no longer
available on the market. If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years. We don't want to patch this together
and always have problems."
And just as a note, your customer can write off $10,000+ per year for new equipment purchases. I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
a month later, in the next year!

Calendar Notes - Bidirectional Sync with Exchange 2003 not working

I have Exchange 2003. Active sync works but when I change notes field in an appointment from the iPhone, it does not sync that change to Exchange server. I have an appointment on the iphone with notes, but I cannot see the notes I created from the iPhone on my Outlook connected to my Exchange server. Works fine with Exchange 2007 but not with 2003. Anyone else noticed this?

the new iphone does not sink with outlook 2003 and my sync with mac
is far far less than perfect (300 out of 2500 contacts sync). The iphone techs tell me this problem is universal. I sure didn't get this information when I bought the phone. The apple techs for cannot fix these problems. The software seems flawed.
<Edited by Moderator>

Read/Unread, Replied, & Forwarded status not syncing with Exchange 2003 SP2

Is there a solution to the email status syncing issue for Microsoft Exchange 2003? It had never work since the day we setup the exchange account on the iphone. Any suggestion is appreciated.
I posted the above question in May 2009. iOS is now at 4.2.1, I guess Apple has no plan on addressing these. Would it work with the latest Microsoft Exchange?

Read/Unread worked for me when we were on Exchange 2003, and it continues to work now that we are on 2007. So it's probably an issue in your Exchange server.

Unity 4.2 voice mail only with Exchange 2003

Hi Team,
we are replacing window 2000 OS with Win 2003 for unity 4.2. This is a single box solution. Exchange 2000 is installed on same unity server. Now we are upgrading the OS from 2000 to 2003. With window 2003 we have to installed the Exchange 2003. In unity installation 4.0(5) following paragraph is mentioned which means we need separate hardware for Exchange. Kindly advise whether we need a separate server for Exchange 2003 or we can install on the on unity box.
If you are using Exchange 2003, install Exchange 2003 administration software on the Cisco Unity server. (Exchange 2003 is installed on a separate server.)
If you are using Exchange 2000, you can install Exchange 2000 either on the Cisco Unity server or on a separate server. If you install Exchange 2000 on a separate server (typically for systems with a large number of subscribers), install Exchange 2000 administration software on the Cisco Unity server.
BR
Muhammad Irfan

Thank you Javalenc,
I can understand from following that Exchange 2003 can be installed on same server.
Voice Messaging
•Exchange 2003 on the Cisco Unity server or on a separate server. If you want to install Exchange 2003 on the Cisco Unity server, note the following:
–The Cisco Unity server must be running Windows Server 2003.
–Exchange 2003 can be installed only on the currently shipping servers supported for use with Cisco Unity 4.2 (MCS-78xx-x2, MCS-78xx-x3, or later, including IBM and HP equivalents). Currently shipping servers are listed in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/
As you know we are just replacing the OS, from win 2K to 2k3. So any thing I need to take care to back up the existing Unity with win 2000 and exchange 2000..
I am taking the back up of my unity 4.2 installed on window 2000 with DiRT and will restore on unity 4.2 with win 2003 and Exchange 2003.
Kindly advise.
BR

I'm trying to get organized and I just added a bunch of books and pdfs to my itunes library. They were all added immediately to my ipad and iphone even though, itunes automatically putting books on my idevices

I'm trying to get organized and I just added a bunch of books and pdfs to my itunes library. They were all added immediately to my ipad and iphone even though I did not want this. I added them to itunes using add to library and I have both devices set to sync only selected books.
How do I do this in the future so this doesnt happen? Its a lot of work to now manually erase them from each device and it sent my phone over capacity.
thanks

I dont see the difference in the posts. I dont think theres anything inaccurate or misleading about what I wrote. The items were immediately added to my ipad and my iphone, even though I have them both set to sync only select items. As soon as I added new titles to my itunes library, they were immediately added to the devices. Not on the next sync. Immediately. Both devices were plugged into the computer at the time. Sorry if I failed to mention they were plugged in but I dont see the signifigance youre making out of it. The problem persists anyway.
Now that I did a test without the devices plugged in, the new items were still added as soon as I plugged my devices into the computer ( I do not have them set to sync over wifi).
Since I have both devices set to manually select items to sync, of course I want to manually select new items to sync. For instance, I am not going to read any of these magazines or books on my phone, ever, and I dont want to waste valuable space with them.
So I'm trying your advice:
I just tried deselecting sync books. It erased all content from ibooks on my device. I then dragged
one title onto the device, and it just goes back to syncing select books, with the one title selected.
It appears that wont work to solve my issue. The next time I add something to itunes it will be put on my phone. Is this really something most people want? To select to manualy control what content is synced, but then have things automatically added. It seems inconsistent to me.

Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time. I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know. Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Removing dead Exchange 2003 and Exchange 2000 Server from the domain

Hi Team,
I have come across a client who wants to migrate to O365 from existing Exchange 2003 environment through the Hybrid Model. I am trying to introduce 2010 Sp3 to the environment. While checking the environment using Exchange pre-deployment found 2 servers
in the environment which is not present on the network now. Client has no clue what they are.
One is Exchange 2003 and the other is Exchange 2000. The problem here is i cannot introduce Exchange 2010 Sp3 unless all the Exchange servers are running minimum Exchange 2003 Sp2.
At present i find only 2 exchange 2003 Sp2 server which are in production. Need kind assistance to move forward.

Hi,
I recommend you follow the steps below:
1. Please upgrade Exchange 2000 and Exchange 2003 to Exchange 2003 SP2 at first.
2. Deploy Exchange 2010 servers in this order: CAS, Hub, UM and Mailbox. For more information, here is an article for your reference:
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
3. Install Exchange 2010 SP3.
Here is an article for your reference.
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
About a hybrid deployment with Microsoft Office 365 using Microsoft Exchange Server 2010 servers, here is an article for your reference.
Understanding Upgrading Office 365 Tenants for Exchange 2010-based Hybrid Deployments
http://technet.microsoft.com/en-us/library/jj945383(v=exchg.141).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Lion Mail.app won't sync with Exchange 2003

Hello,
After upgrading to Lion, I am having an issue with my Exchange email in Mail.app. I get new emails, however if I file any emails from the Inbox into another folder and then leave view another folder or exit Mail, when I return the emails are back in the Inbox again. It is as if Mail is not syncing my changes up to the Exchange account.
This issue did not begin until I moved to Lion. I have compared my settings to another co-worker, who is also on Lion and connecting to Exchange 2003 and everything appears to be the same.
Thoughts? Solutions?

RevRangwar,
Yes, I think I was. I went ahead and removed my Exchange account from Mail and re-created it as Exchange IMAP, and it appears to have resolved the issue.
Thanks for the help.

HT204053 I have an Apple ID and use I Cloud with my Ipad and Iphone. I am trying to publish a website from my macbook but my user name and password is not recognised when I try?

I have an Apple ID and use I Cloud with my Ipad and Iphone. I am trying to publish a website from my macbook but my user name and password is not recognised when I try?

Ken.Lloyd wrote:
Sorry for the delay. System preferences icloud is not an option for me. Syst preferences mobileme is
The minimum requirement for iCloud is Lion 10.7.2 - earlier systems don't show the iCloud preference pane. If you want to use iCloud you will have to upgrade to Lion or Mountain Lion (assuming your computer meets their requirements) but even so you won't be able to publish web pages to iCloud because it does not provide web hosting. This page examines that situation in more detail:
http://rfwilmut.net/missing2

Connector help ( Coexistence Exchange 2003 and Exchange 2010)

Dear all,
we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
On Exchange server 2003 we have two connectors 1) Internal 3) External
1) Internal connector is used to have mail flow between postfix mail and Exchange server.
2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
if these works then delete connectors on legacy server and go ahead with for rest migration
is it possible if not then how do it ?
TheAtulA

Hi AtulA,
Thank you for your question.
Internal:
To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
2003 as Exchange Routing Group within Exchange Administrative Group.
During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
Exchange 2010 servers, regardless of the Active Directory site in which they reside.
Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
this routing group for communication with Exchange 2003.
External:
We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

TS3899 Cannot send email with new iPad air. Works fine with old iPad and iPhone.

Cannot send email with new iPad air. Works fine with old iPad and iPhone. I have deleted account and reinstalled.

Thanks. I got the problem fixed. Spent time with the Apple folks and was kicked up to a senior advisor. It seems the problem was with my internet provider - Tmie Warner. Remember I could use the old ipad and the iphone to send mail. I checked all the specifics between the three units. It seems that TW is changing over from the RR.com to TWC.com. Since the new ipad air was just set up, it fell under the new TWC mail specifics.

Require Passcode Immediately with Exchange 2003 and iPhone 3.0?

Similar Messages

Maybe you are looking for