User Avatar Image

Port Forwarding question

posted by Farphignougen on - last edited - Viewed by 1.2K users

This post would've gone in the "download file won't connect" thread, but it was closed. Emily said that the (ARM1054, 12029) problem pertained in part to users behind firewalls, and I've got one in my router. I was wondering what TCP and UDP ports the downloader program uses so I can put them in the router's Port Forwarding table and possibly prevent this problem in the future.

10 Comments - Linear Discussion: Classic Style
  • Interesting question. I don't actually know the answer, though.

    I will be following up with Digital River about this issue next week. I'll try to find out for you.

  • I don't mean to be a pest, but is there still no answer to the question?

  • Thank you for bumping this. I meant to mention it to them in the context of some other downloading issues we were trying to figure out, but I don't think we ever got this specific.

    I'll shoot off an email to DR right now.

  • A quick test shows the downloader only using http for the download:
    [quote=netstat]TCP fry:4628 ESTABLISHED
    TCP fry:4631 ESTABLISHED[/quote]

    It may be that local firewall software doesn't like non-browser software making http connections, but that doesn't explain why your router would object. I think that means we have to wait for DR to answer this issue, unfortunately.

    Edit: You could try making your IP the DMZ host for your router, but that isn't a good long term solution at all, since it opens you up to all undirected traffic aimed at your router.

  • Here's the response I got:

    [quote]Our download manager is implemented using the Microsoft WinInet library calls and therefore we do not know which TCP port is actually used in each download. Also in this case we are the client side, the port number used is not likely going to be fixed. [/quote]

  • Ooh, and then I just got this other response:

    [quote]Per DRM team the downloader program uses port 80. [/quote]

  • Hi!

    I was getting the ARM1054,2 error, too.
    After I read the info about WinInet in this thread, it began to dawn on me that the infamous IE might have something to do with it (I still have 6.0 installed). So I opened it up, switched it to online mode (without opening the firewall for it), and disabled the proxy settings.
    Et voilà, the downloader worked.
    Maybe this helps some people solving their ARM1054,x problems.


  • Thanks for the info! Good to know.

    Digital River is planning to roll out a new version of their download manager soon, that they say will resolve a lot of the internet connection errors people have been experiencing. Anyone who has been having a consistent problem with downloading or activating who would like to test out the new download manager when it's read, please send me a PM.

Add Comment