Kindly be advised we cannot cancel subscriptions or issue refunds on the forum.
You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/

Thank you for your understanding.

Bitdefender & Warcraft 3 Don't Play Nice

Options
tokool
tokool
in General talk

Currently, I can connect to battle.net but I cannot actually host a game. The reason I suspect is this message:


2008/06/20 12:45:54.671 [bDFTDIF][ADDRESS] Closing TCP port. (addr = 0.0.0.0, port = 6112)


2008/06/20 13:43:18.359 [bDFTDIF] Connection attempt to 63.240.202.138:6112 succeeded. (0x0)


2008/06/20 13:43:18.390 [bDFTDIF][FILTER] Packet received for closed port.


2008/06/20 13:43:18.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.138, src port = 6112, dst addr = 192.168.1.100, dst port = 6112)


2008/06/20 13:43:18.390 [bDFTDIF][FILTER] Packet received for closed port.


2008/06/20 13:43:18.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.138, src port = 6112, dst addr = 192.168.1.100, dst port = 6112)


Why is BitDefender blocking UDP packets when I have set the WC3 program to Allow? Does anyone know how I can give access to the UDP packets from Blizzards servers? Ok, thanks. ^_^

Comments

  • alexcrist
    alexcrist ✭
    Options

    Read this: Faq - Bd Firewall Blocks An Application From Connecting

  • tokool
    tokool
    Options
    Read this: Faq - Bd Firewall Blocks An Application From Connecting


    I attempted this and it did not stop blocking the ports. I tried reinstalling Bitdefender (after asking BD tech support) and I still cannot host a game. It was easy with Mcafee I just opened a port and it worked does BD have any port opening function? Ok, thanks for your input.

  • alexcrist
    alexcrist ✭
    edited June 2008
    Options

    It's not the firewall's job to open ports. Only applications open ports.


    The firewall's job is only to allow/block specific applications to open specific ports. If you followed the above rules, the application will have the liberty of opening any ports is needs, whenever it needs them.


    Also, you could try disabling Stealth Mode, from the Advanced tab, in the Firewall section.


    Cris.

  • tokool
    tokool
    edited July 2008
    Options
    It's not the firewall's job to open ports. Only applications open ports.


    The firewall's job is only to allow/block specific applications to open specific ports. If you followed the above rules, the application will have the liberty of opening any ports is needs, whenever it needs them.


    Also, you could try disabling Stealth Mode, from the Advanced tab, in the Firewall section.


    Cris.


    I followed the instructions and it did not work so I am not to sure what else I can do?


    This is with stealth mode off. Why is it still denying packets isn't turning stealth mode of kind of like shutting the firewall down? I am confused? Alright, any input would be helpful.


    2008/07/10 22:44:05.359 [bDFTDIF] Connection attempt to 63.240.202.128:6112 succeeded. (0x0)


    2008/07/10 22:44:05.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:44:05.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:44:31.750 [bDFTDIF] Connection attempt to 63.240.202.128:6112 succeeded. (0x0)


    2008/07/10 22:44:31.781 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:44:31.781 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:45:01.265 [bDFTDIF] Connection attempt to 63.240.202.128:6112 succeeded. (0x0)


    2008/07/10 22:45:01.296 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:45:01.296 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.128, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:46:56.609 [bDFTDIF] Connection attempt to 63.240.202.127:6112 succeeded. (0x0)


    2008/07/10 22:46:56.625 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.127, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:46:56.625 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.127, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/10 22:46:56.875 [bDFTDIF] Connection attempt to 63.240.202.127:6112 succeeded. (0x0)


    Here are some pics of my firewall if it helps any.


    firewallpicszj2.png


    firewallpic2xg3.png

  • Chesda
    Chesda
    Options

    To host a game you need to open your ports, you might want to check this site out: http://portforward.com/routers.htm


    Port Forwarding helps you to open up a port in your router or firewall so that you can host online games.

  • tokool
    tokool
    Options
    To host a game you need to open your ports, you might want to check this site out: http://portforward.com/routers.htm


    Port Forwarding helps you to open up a port in your router or firewall so that you can host online games.


    Yup, I already forwarded my ports.


    portsbe4.png


    The thing is it worked fine with McAfee's firewall and then I installed Bit defenders FW and I cannot host games anymore. So it has to be some conflict with this firewall software I installed(or somehow I am a total goober). Any other idea's of the possible cause of that strange bit defender message and why I cannot connect? Thanks for your input so far guys.

  • tokool
    tokool
    Options

    Even more strangeness! I am now having trouble occasionally when I try to log onto the game server itself as well as really sluggish connections to the internet. What is going on with BD? Does anyone have any insight into what these messages mean? Mind you I already reinstalled BD (with the uninstall tool) after the tech team told me to.


    Here are the firewall logs.


    2008/07/13 16:56:31.468 [bDFTDIF] Connection attempt to 63.240.202.138:6112 failed. (0xC0000120)


    2008/07/13 16:56:31.468 [bDFTDIF] Connection attempt to 63.240.202.128:6112 failed. (0xC0000120)


    2008/07/13 16:56:31.468 [bDFTDIF] Connection attempt to 63.240.202.129:6112 failed. (0xC0000120)


    2008/07/13 16:56:31.468 [bDFTDIF] Connection attempt to 63.240.202.130:6112 failed. (0xC0000120)


    2008/07/13 16:56:31.468 [bDFTDIF] Connection attempt to 63.240.202.139:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.120:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.121:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.122:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.126:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.139:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.127:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.134:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.129:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.128:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.131:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.130:6112 failed. (0xC0000120)


    2008/07/13 16:56:37.250 [bDFTDIF] Connection attempt to 63.240.202.138:6112 failed. (0xC0000120)


    2008/07/13 16:56:47.562 [bDFTDIF][RULE] End set rules


    2008/07/13 16:56:47.609 [bDFDRVI] Cannot determine the ICS public adapter, 16389


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.139:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.138:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.120:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.122:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.130:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.129:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.126:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.127:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.131:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.128:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.134:6112 failed. (0xC0000120)


    2008/07/13 16:56:51.843 [bDFTDIF] Connection attempt to 63.240.202.121:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.120:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.121:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.122:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.126:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.127:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.128:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.138:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.130:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.129:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.131:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.134:6112 failed. (0xC0000120)


    2008/07/13 16:56:57.703 [bDFTDIF] Connection attempt to 63.240.202.139:6112 failed. (0xC0000120)


    2008/07/13 16:56:58.140 [bDFTDIF][ADDRESS] Opening UDP port. (addr = 0.0.0.0, port = 6112)


    2008/07/13 16:56:58.140 [bDFTDIF][ADDRESS] Opening UDP port. (addr = 0.0.0.0, port = 6112)


    2008/07/13 16:57:01.828 [bDFTDIF][ADDRESS] Closing UDP port. (addr = 0.0.0.0, port = 6112)


    2008/07/13 16:57:02.593 [bDFTDIF] Connection attempt to 63.240.202.121:6112 failed. (0xC00000B5)


    2008/07/13 16:57:24.625 [bDFTDIF] Connection attempt to 63.240.202.130:6112 failed. (0xC00000B5)


    2008/07/13 16:57:25.015 [bDFTDIF] Connection attempt to 63.240.202.128:6112 failed. (0xC00000B5)


    2008/07/13 16:57:25.531 [bDFTDIF] Connection attempt to 63.240.202.127:6112 failed. (0xC00000B5)


    2008/07/13 16:57:25.828 [bDFTDIF] Connection attempt to 63.240.202.139:6112 failed. (0xC00000B5)


    2008/07/13 16:57:26.328 [bDFTDIF] Connection attempt to 63.240.202.138:6112 failed. (0xC00000B5)


    2008/07/13 16:57:26.625 [bDFTDIF] Connection attempt to 63.240.202.131:6112 failed. (0xC00000B5)


    2008/07/13 16:57:27.234 [bDFTDIF] Connection attempt to 63.240.202.129:6112 failed. (0xC00000B5)


    2008/07/13 16:57:27.531 [bDFTDIF] Connection attempt to 63.240.202.134:6112 failed. (0xC00000B5)


    2008/07/13 16:57:27.843 [bDFTDIF] Connection attempt to 63.240.202.126:6112 failed. (0xC00000B5)


    2008/07/13 16:57:28.234 [bDFTDIF] Connection attempt to 63.240.202.122:6112 failed. (0xC00000B5)


    2008/07/13 16:57:45.750 [bDFTDIF] Connection attempt to 63.240.202.121:6112 failed. (0xC00000B5)


    2008/07/13 16:57:46.140 [bDFTDIF] Connection attempt to 63.240.202.120:6112 failed. (0xC00000B5)


    2008/07/13 16:57:55.359 [bDFTDIF] Connection attempt to 63.240.202.134:6112 succeeded. (0x0)


    2008/07/13 16:57:55.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.134, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/13 16:57:55.390 [bDFNDISF][FILTER] Denied UDP packet. (dir = INBOUND, src addr = 63.240.202.134, src port = 6112, dst addr = 192.168.1.101, dst port = 6112)


    2008/07/13 16:58:22.015 [bDFTDIF][ADDRESS] Opening UDP port. (addr = 0.0.0.0, port = 52484)


    2008/07/13 16:58:22.187 [bDFTDIF][ADDRESS] Closing UDP port. (addr = 0.0.0.0, port = 52484)


    Thank you for your time and help!

  • tokool
    tokool
    Options

    Still have not found a resolution to my problem any new ideas will certainly help and be appreciated.

  • alexcrist
    alexcrist ✭
    edited July 2008
    Options

    Hello Tokool,


    Maybe that not the application that's actually making the connections?


    Anyway, if all the time the same port 6112 is used, and that port doesn't vary, create a special rule for it, like this:


    - press Add rule


    - select the checkbox Any application


    - select Allow as the action


    - select Both as Direction


    - select Any IP both for local and remote addresses


    - select All as Protocol (or you could select just UDP)


    (I'm using now BDv12 BETA, which has a different "New rule" dialog, so if I missed something and you don't know how to set it, ask)


    After creating the rule, you won't see it in the normal Traffic list, because there, the rules that are defined for all application are not shown. But the rule can be seen and edited in the Edit profile dialog.


    Also, after creating the rule, move it to th top (as you did before).


    Now try to see if this works.


    Why is it still denying packets isn't turning stealth mode of kind of like shutting the firewall down?


    No. Stealth Mode only denies ICMP traffic and port scans. Once it's disabled, your computer becomes visible in your network, but the rest of the firewall (traffic rules) still works.


    Cris.

  • tokool
    tokool
    edited July 2008
    Options
    Hello Tokool,


    Maybe that not the application that's actually making the connections?


    Anyway, if all the time the same port 6112 is used, and that port doesn't vary, create a special rule for it, like this:


    - press Add rule


    - select the checkbox Any application


    - select Allow as the action


    - select Both as Direction


    - select Any IP both for local and remote addresses


    - select All as Protocol (or you could select just UDP)


    (I'm using now BDv12 BETA, which has a different "New rule" dialog, so if I missed something and you don't know how to set it, ask)


    After creating the rule, you won't see it in the normal Traffic list, because there, the rules that are defined for all application are not shown. But the rule can be seen and edited in the Edit profile dialog.


    Also, after creating the rule, move it to th top (as you did before).


    Now try to see if this works.


    No. Stealth Mode only denies ICMP traffic and port scans. Once it's disabled, your computer becomes visible in your network, but the rest of the firewall (traffic rules) still works.


    Cris.


    Hello Cris I tried to set a rule for bit defender and that did not fix the issue. It still fails to allow the ports to be accessed. I am not to sure what could be causing this issue but it is getting a tad frustrating. I don't have the beta but I do have the most up to date bd there is that is not a beta. Any other plausible ideas on how to fix this issue? Do you think there could be some odd conflict with BD and my router? Alright, well thanks for your help thus far. Hopefully we will find the answer to this situation.


    Ps. Thanks for the info on stealth mode.

  • alexcrist
    alexcrist ✭
    Options

    If you have Enable Internet Connection Sharing enabled in BitDefender (Firewall -> Advanced) and you don't need it, try to disable it. There were some other topics on the forum saying that this option somehow blocks some connections (I don't know why).


    Cris.

  • tokool
    tokool
    Options
    If you have Enable Internet Connection Sharing enabled in BitDefender (Firewall -> Advanced) and you don't need it, try to disable it. There were some other topics on the forum saying that this option somehow blocks some connections (I don't know why).


    Cris.


    Thanks again for trying Cris this did not work though. I attempted to uncheck everything including the disable firewall icon and nothing changed. I have decided that bit defenders firewall is not worth my time anymore. I will stay with the virus scanner but I will be going with zone alarms firewall. I came to this decision after noticing that the firewall was not just blocking warcraft 3 but also everquest 2. Again, I believe you guys make a quality product when it comes to your anti virus but for a gamer your firewall needs some tweaking before I decide to ever use it. Thanks for all your help and good luck to fixing some of the current issues with your software.

All Time Leaders

Categories

Defenders of the month