[fixed in 20.0.21.1191] Firewall Causes 0x8007003b File Transfer Error

I am also confirming this issue on my end when transferring large files from PC to NAS drives. Disabling Bitdefender firewall fixes it right up.

However, what I do notice is that if you open up the Firewall Module, go to the Adapters tab and monitor this window whilst transferring a large file, you should see an adapter called "Teredo Tunnelling Pseudo-Interface". As soon as this adapter disappears from this list, the transfer will fail and Windows gives you the Network/File Transfer Error.

I am on Windows 10 with Bitdefender Internet Security 2016. My NAS drives are connected to the router running DD-WRT.

I fixed the issue by disabling the Teredo adapter in Windows Device Manager. It's hidden so you have to click View and Show hidden device. I don't utilize IPv6 so not having Teredo is fine by me. However, it is enabled by default and other Bitdefender users might also have the same issue so Bitdefender developers might still want to look into this.

THIS fixed the issue. Tried with TS2015 & TS2016 on Win8.1. Had the same problem. Its definetly a Firewall related problem with the Bitdefender Firewall

THIS fixed the issue. Tried with TS2015 & TS2016 on Win8.1. Had the same problem. Its definetly a Firewall related problem with the Bitdefender Firewall

This works for me, however, each time I reboot the Teredo Tunneling adapter is enabled again so I have to manually disable each time. Any suggestions anyone?

Thanks for pointing that out.

If you enter "netsh interface teredo set state disabled" into Command Prompt (Admin) it appears to permanently disable the adapter even after a reboot.

Thanks sierratango but I tried that too and the Teredo still is enabled again after reboot?

That's strange. I've done it on both of my PCs and it stays disabled after rebooting. In fact it doesn't even appear in Device Manager anymore.

Make sure when you input that line into Command Prompt, you receive an "Ok." output.

I'll have another go and get back.

to disable the Teredo without Device Manager:

open Command Prompt with Admin-Rights and type the following:

netsh interface teredo set state disable (Teredo will be disappear in the Device Manager also)

If you want to reenable it again:

netsh interface teredo set state type=default

Hi all,

If the issue reproduces on other computers, please follow the steps below and send the logs requested in order to have the issue investigated by our development team:

1. Download the attachment from this message, corresponding with the product installed on the device(FW IS for Bitdefender Internet Security; FW TS for Bitdefender Internet Security).

2. Rename the file from FW IS.txt or FW TS.txt to FW IS.reg or FW TS.reg

3. Restart the system in Safe Mode.

4. Open the Registry Editor and copy the .reg file to the following location: HKEY_CURRENT_USER\SOFTWARE\Bitdefender\Bitdefender Internet Security 2016 or HKEY_CURRENT_USER\SOFTWARE\Bitdefender\Bitdefender Total Security 2016.

5. Restart the PC normally.

6. Open Bitdefender> Modules> Protection> Firewall> Settings> Turn: Enable logging to ON.

7. Reproduce the error encountered by:

-Applying the correct settings for the respective network adapter in Bitdefender> Modules> Protection> Firewall> Adapters(Network Type: Home/Office; Stealth Mode: Off; Generic: On)

-Restart the PC and check if the settings are not being saved.

8. If the settings are not saved, we would need a support tool log and the following files from C:\Program Files\Common Files\Bitdefender\Bitdefender Firewall: bdfirewall.txt, ignis_log.txt, ignis_traffic_log.txt, ignis_internal_log.txt, ignis_internal_log.txt.

[how to generate a SUPPORT TOOL log]

http://www.bitdefender.com/support/-1168.html

Thank you Paul-Robert for the contribution. But I don't see how this helps resolve the underlying original issue with file transfers failing. The issue appears to be with the Teredo adapter/drivers or it's OS interaction. Disabling the interface is an acceptable workaround or patch, but it's not a fix. Can you give us something closer to the root of the issue to work on?

Hi NetGeek, the steps provided by Paul are not a workaround but a way of generating Bitdefender firewall logs which can help us debug the reported issue.

Please post back the required data when you have it.

Thank you for your understanding.

My Apologies - I made some incorrect assumptions and didn't take the time to read-through the details provided by Paul-Robert. I'll gather together the logs this weekend, time permitting. Thank you for setting me straight.

Hello,

The issue was fixed today in the latest Bitdefender build version 20.0.21.1191.

Please bring up Bitdefender and click Update. Wait until the update process completes, then click the top right menu and select Events in the drop-down menu. Locate in the list of Update events the event asking to reboot the computer. Click on it and then click Restart Now button in the displayed details.

After the computer reboots, make sure you have the latest build: right click on the Bitdefender icon from the system tray, choose About and look at the Product Information number. It should be 20.0.21.1191.

Everything should be back to normal afterwards.