Error -3253 while downloading a movie.

Me too. This has been a problem since Apple 'fixed' ATV1's inability to access the iTunes Store about a week or so ago.

The same problem starting happening to me around a week ago when trying to download a movie from my Apple TV First Generation. Has anyone come up with the solution to fix this? Thanks.

I'm having this issue as well. I was wondering if it was just me or if everyone else ditched their ATVs and bought netflix. I've been sitting in front of my tv for an hour hitting download every time it errors out. Hopefully this get's fixed.

I'm in the same boat ... obviously not an isolated problem.

+ 1 for this issue.

No new software or network settings, now get 3253 every time.

Something's broken!

Agreed that this is an issue on Apple's side of the fence. I never encountered this issue before their last update so it does need to be examined and addressed by Apple's technicians.

I am running iTunes 11.1.5 (5) on an iMac operating w/OS X (version 10.9.2) with ALL updates installed.

Some problem here, just joining to get latest anwers and a solution:

Google results that didn't help:

- DNS Flush

- Change DNS servers to OpenDNS

No. Unforunately none of these recommendations (all listed above/earlier) did not help resolve this current issue.

Considering the number of others who are experiencing the same issue (check other listings within the Support Communities forums which refer to the 3253 error) it is something that had to have happened during Apple latest update as everything worked fine for me until then.

I'm currently expieriencing some large ammounts of crc errors (max. 200 / h) on my adsl connection. Maybe the appstore hash errors might have some relation to that.

I too get the same error message whenever I try to download a purchased movie. If I keep restarting the download, I eventually get it done. However, Apple needs to fix. Im using the latest version of iTunes and OSX but still having the issue. Come on Apple!

Same problem-ATV1

Changing DNS is a waste of time - does not resolve the error. Any eta on a real fix?

I'm having same problem.

Article on sidebar supposedly relating to this doesn't. Not helpful at all.

I just spent over an hour on the phone and working through Remote Advisor w/an Apple Technician (AT) going through a plethora of troubleshooting items - all to no avail.

The AT did provide me with his/her specific contact information and promised to get back to me with an update within 24-hours. Although there is no resolution at this time, I do at least have the comfort knowing that this issue has indeed been forwarded to the Engineering team for them to review and address.

I just hope that this is resolved sooner rather than later.

And as an FYI I did suggest that they check out the Community Forums to get better understanding that this is not an issue specific to me alone but to a much broader group.

Very disappointed in Apple's progress at this point... hopefully resolved soon!