locked
Firewall problems with World of Warcraft RRS feed

  • Question

  • Is there something I am doing wrong when trying to configure the firewall for use with World of Warcraft? Here's what I did:

    1) Allowed the program (the launcher and the main program) ensuring the correct version was specified.

    2) Opened about 10 ports (TCP) that WOW specified.

    No dice. Tracert.exe failed (to the address specified by WOW); WOW failed. Turning off the firewall worked.

    Any ideas? Do I have to respecify these ports in the XP service pack 2 firewall settings (via control panel).

    I spent the better part of the afternoon trying to get this working only to turn the firewall off to enable WOW.

    From my years of working with securty software there's been on constant -- the biggest 'threat' is security software that's hard to configure. Inevitatbly security is compromised when users turn off the software (as I did) or incorrectly configure it. (Okay, off the soapbox.)
    Thursday, December 27, 2007 4:05 AM

Answers

  • The failure of Tracert.exe would be unrelated to allowing or not the exe for World of Warcraft and the posts WOW may need. For Tracert, you may need to simply allow ICMP outbound, though I'm not positive of that. I have that allowed and tracert works fine for me.

    This page, http://us.blizzard.com/support/article.xml?articleId=21015&categoryId=2329&parentCategoryId=2316&pageNumber=1, looks like it contains what you need to configure the firewall for WOW.

    "The Blizzard Downloader requires that ports 3724 and 6112 be open. It can also benefit from having ports 6881 through 6999 open."

    This would lead me to believe that you need to set TCP 3724 Inbound and Outbound, TCO 6112 Inbound and outbound, and TCP 6881-6999 inbound and outbound to allowed.

    I would expect that WOW will either be recognized outright and allowed, or you should be prompted to allow. If it is the latter, each time the exe updates, it will need to be approved again and restarted before it will gain access.

    You can, of course, contact OneCare support for further help with this - 

    How to reach support (FAQ) - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2

    -steve

    Thursday, December 27, 2007 4:57 PM
    Moderator

All replies

  • The failure of Tracert.exe would be unrelated to allowing or not the exe for World of Warcraft and the posts WOW may need. For Tracert, you may need to simply allow ICMP outbound, though I'm not positive of that. I have that allowed and tracert works fine for me.

    This page, http://us.blizzard.com/support/article.xml?articleId=21015&categoryId=2329&parentCategoryId=2316&pageNumber=1, looks like it contains what you need to configure the firewall for WOW.

    "The Blizzard Downloader requires that ports 3724 and 6112 be open. It can also benefit from having ports 6881 through 6999 open."

    This would lead me to believe that you need to set TCP 3724 Inbound and Outbound, TCO 6112 Inbound and outbound, and TCP 6881-6999 inbound and outbound to allowed.

    I would expect that WOW will either be recognized outright and allowed, or you should be prompted to allow. If it is the latter, each time the exe updates, it will need to be approved again and restarted before it will gain access.

    You can, of course, contact OneCare support for further help with this - 

    How to reach support (FAQ) - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2

    -steve

    Thursday, December 27, 2007 4:57 PM
    Moderator
  • As far as the tracert permissions. you must also allow ICMP inbound, since ICMP is connectionless. Otherwise you don't allow the response back in.

     

    Monday, January 28, 2008 10:55 PM