Currently Being ModeratedFeb 9, 2012 9:09 AM (in response to markymark8)
The only thing you gotta do is follow this intructions: http://support.apple.com/kb/TS3367?viewlocale=en_US&locale=en_US
Somehow facetime for iPhones and Macs computers are directly liked with data & time.
Some issues with network might occur but for me was just setting date & time to automatic.
The article on the link above helped me as a tip from one of the guys on the forums
I still want to know why the rellation with date & time. If anyone has an asnwer, please share.
Currently Being ModeratedFeb 25, 2012 12:42 AM (in response to Steve Paris)
that is good advice but my ipod still will not let me get into facetime..... and i have also resored it and what should i do? is there anyway??? please help
Steve Paris wrote:
Changing the DNS settings to Google's worked for me
To help others, this is how I did it:
1. On my iPod touch, I went to the Settings App.
2. Tap on Wi-Fi
3. Your chosen network will be ticked. Tap on its white arrow over a blue circle button to its right
4. Tap on DNS
5. Replace the current information with 22.214.171.124,126.96.36.199
6. Try visiting a website with Safari to see if this works
7. Try registering with FaceTime (I hear that your username needs to be an email address). It finally worked for me
Currently Being ModeratedApr 5, 2012 12:50 PM (in response to Dave1130)
got methodology to solve the issue by changing DNS on following link
Currently Being ModeratedApr 17, 2012 3:21 PM (in response to Steve Paris)
I had the same problem and I tried all the the tips previously given. Finally, after hours of messing with it and getting ready to take it back, it worked! I'm not sure which one of these actually did the job:
1. changed dsn to 188.8.131.52
2. took a couple of pictures with the camera to make sure it was functioning
None of these worked for me:
1. turned wireless on and off
2. changed dsn to 184.108.40.206.220.127.116.11
3. restored original wireless settings
4. turned ipod off
5. restarted ipod
6. erased all content and settings
7. reset all settings
8. double checked time and date
9. made sure there were no restrictions on the camera or facetime
Currently Being ModeratedDec 18, 2013 9:37 AM (in response to Steve Paris)
I had this problem with my iPad Air. I did a research and everyone says to cheach the connection and to be sure that the ID is working and all the emails are verified. I followed all the steps and nothing worked for me. My Wifi Works as a charms. Loging to the Apple using my ID working fine and all the emails "VERIFIED".
Her is my expereiance and the solution:
Nothing to do with your ID or the Internet connection or the WiFi setting. The problem is on Apple Server OR on the device it self.
What I did to solve this problem is going to the General --> Reset All the Settings. Be sure not to delete your data. Just reset all the settings. Then turn on your device and try again to sign in.
For me, I was able to sign in and verify to Facetime with my ID and the same WiFi connection that everyone was saying to check them. For the iMessage, I was able to sign in but not to verifying... it start to give me "iMessage Server Error ... Try again" on this phase. I tried to verifying more than 3 times, same error. Then I just turned my iPad Air off and turn it on again. I went to the iMessage to try again. I suprized to see the the iMessage was successfully setup!! and everything working great.
Note: iPad Air crashing a lot. One example: I want to setup my email: Setting --> Mail, Contact, Calendar --> Add new mail account ------> I gave the parameters then ---> Next CRASHED HERE. Tried again, it worked fine. Another day setup another email account ---> CRASHED in again during the setup in different place. Change the Background ---> some times Crashing. Brwosing the web ---> Crashing ........
However, new product means problems at the begining. I just want to say: Don't guys always pushing the problems to be the client resposibilities. Apple is not perfect, No one is perfect, We need help from you guys when we need it. The above problem is caused by Apple Server NOT by the user!