The answer to this question/challenge may not be easily found. We have been unable to download Adobe applications using the Adobe Download Manager or any other method except a direct download for as long as I've worked here. I'm not the IT guy, and he's stumped as well. I know it's not a computer or system issue. I mostly use my personal laptop and downloads from Adobe work just find at home, at the coffee shop, out on the street--just about anywhere except when connected to our network (wired or wireless). OK, I know this isn't enough information to help find an answer, but does anyone have any suggestions as to were to look on the network side? Is there anything obvious about the way Adobe Download Manager, Akamai Download Manager, or any other download tool used by Adobe handles connections that could be disrupted by a server setting, router setting, firewall setting? This situation is unique to Adobe downloads. We download things from other software vendors without problems. It's been an issue for a long time. I decided to seek an answer because of the pending release of CS6.
As far as download attempts, the Adobe Download Manager does nothing when it attempts to initiate a download. Attempting today, the app launches, a screen pops up with the heading "Make the Most of Your Trial." The download bar appears and shows "downloading XXXX mb - about 356 hours." And that's where it sits. It always says 356 hours, and no download. A file is created in the chosen directory usually with 0 kb, but on a few attempts 64 kb. If I walk to the restuarant down the street and use their public wifi, no problems downloading. Same laptop. Same browser window. The only thing that's different is the network. The above applies to all computers in the building (and connected to the network).
PC/Windows 7 systems, serveral Server 2008 boxes, Cisco router, --nothing out of the ordinary as far as the network.
I appreciate some direction here. I know it's not a lot of information, but a starting point would be nice.
It seems likely that your systems are only allowing approved applications to connect to the Internet. Neither the Adobe Download Assistant or the Akamai Download Manager use any unique ports so it is likely the very fact that they are applications which is preventing the downloads to be successful.
Thanks Jeff for the quick response. This may be the case. I'll hunt down our IT guy and investigate. However, the Adobe Application Manager works just fine when downloading updates. And I've been playing with Muse which downloads updates and requires an adobe login from within the application--which works fine. However, you may be on to something. Is there anyting...even the smallest detail...that is different between the way the Adobe Download Manger communicates with Adobe's servers and the way Adobe Update Manager communicates with Adobe's servers?
One other point, this isn't a server configuration issue as it relates to permissions through Active Directory or user permissions on the Windows Server side. We have an open-to-the-public wifi because of the needs of interactive displays in our Museum. So my laptop isn't part of the internal network when it's connected to wifi. It has to be something at the router/firewall level--at least I think...but that's why I'm asking for insight
Europe, Middle East and Africa