Bitdefender blocks DishAnywhere remote TV access


I use Bitdefender Total Security 2019 on Windows 10 (x64 Pro latest updates)and Windows 7 (x64 Pro latest updates) platforms. I subscribe to Dish Network for TV programming, and have use their Slingplayer-based DishAnywhere for watching TV on my PCs. This has worked flawlessly for several years, but just in the past week, I have gotten error messages that DishAnywherePlayer.exe was unable to connect to my Dish Hopper, its central internet-connected, wi-fi enabled receiver box. As with Slingplayer, this is an over-the-internet connection allowing access to TV from anywhere.


I have determined that the connection is being blocked by Bitdefender as follows:


 


1. Both Windows 10 and separate Windows 7 platforms, both running BD, fail to connect, running either Firefox or Chrome, both of which are supported. At the same time, my Mac computers, iPhone and iPad on the same home network connect properly, so there is not a configuration problem with the Dish Hopper or my router.


2. When I uninstalled BD completely, using BD Uninstall Tool, the player connects on both Windows platforms, on both browsers.


 


While running Bitdefender, I noted that Bitdefender Firewall had a rule allowing all access for DishAnywherePlayer.exe. In addition, I added DishAnywherePlayer.exe as an exception for all of the Protection modules, but was still unable to connect. On one occasion, I got a BD message that DishAnywherePlayer had exhibited Ransomware-like behavior, but adding it as an exception to Ransomware Remediation, or turning of Ransomware Remediation altogether, still did not allow connection.


 DishAnywherePlayer DevTools gave the following error message:  "XMLHttpRequest cannot load http://esra.slingbox.com/asyncevent/rest/v1/receiverid/dish1903348343/timestamp/0?_=1540867535698. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.dishanywhere.com' is therefore not allowed access. The response had HTTP status code 405."


On advice of one website addressing slingplayer issues, I ran the command " netstat -ano | findstr "[.*].*[.*].*50001" " in Windows Powershell to identify the resource occupying port 50001 used by DishAnywherePlayer - the process ID identified the source as "ProductServiceAgent.exe", a component of BD.


When rebooting after uninstalling Bitdefender, I got a message from Windows Firewall noting that "some features of DishAnywherePlayer.exe had been blocked", and I clicked to allow access. The player then connected properly.


I have been working with Dish support, so they will be aware of the compatibility issue. Bitdefender appears to be blocking a component of DishAnywherePlayer.exe or an associated process without providing any display of a way to turn blocking off.



Anyone else have this issue, and/or found a solution?



Thanks, JW


 

error 17.jpg

Tagged:

Comments


  • Hello, 



    Can you try excluding the 2 URLs you mentioned?



    http://esra.slingbox.com/asyncevent/rest/v1/receiverid/dish1903348343/timestamp/0?_=1540867535698


    http://www.dishanywhere.com



    The URLs should be excluded under Protection > Online Threat Prevention > Exceptions .


     


  • Thanks for reply.



    Adding the two domains as exceptions under Online Threat Prevention did not change anything - same error when trying to connect to my Dish DVR.


    Turning off ALL Bitdefender modules that can be turned off, including all Online Threat Prevention modules, also did not help, same error.



    When I turn off BD Firewall, Windows Firewall takes over. It gave me the same message (some features blocked, do you want to allow?) and I said to allow. When BD was completely uninstalled, this allowed successful connection, but with BD present, even with everything turned off, no success.


    I have a 2 year BD subscription for unlimited devices - I am not about to uninstall! It was expensive.



    The second url you referred to contains a time stamp, which will be different every time I try to access the DVR. However, when I copy the full url as an exception, only the domain gets added ( http://esra.slingbox.com/ ). As I said this did not fix the problem.


    Any more ideas? Thanks, JW


  • Hello /index.php?/profile/209278-josephwit/&do=hovercard" data-mentionid="209278" href="<___base_url___>/index.php?/profile/209278-josephwit/" rel="">@josephwit , 



    As we would need several logs to further investigate, could you send us an email at [email protected], so that we can handle the issue through our support platform? 



    Once you've sent the email, you can post here, and I will take over the case. 



    Thank you. 


  • email sent.


  • Sergiu, what happens now?



  • On 11/2/2018 at 4:13 PM, josephwit said:



    Sergiu, what happens now?



    Hi, 



    Sorry for the delay. As we've discussed in the support ticket, currently the case has been sent to our development team for further investigation, as it seems the app is still blocked even after setting exclusions. 


  • Hi,



    Any progress on fixing this? Dish Network forums reveal numerous users having same problem with BD blocking DishAnywhere Player. I have passed on your workaround, but it is somewhat cumbersome, since BD is so good at aggressively updating itself and replacing the renamed httproxy.dll despite my manually cancelling all update requests.


    Thanks!



    Joe


  • NEW ERROR!  See attachments.


    Now, DishAnywhere site is blocked from "getting my login credentials". BitDefender blocks connection to "crvlvk.com" because of expired certificate. This happens every time I attempt to open DishAnywhere. I can log into other parts of my Dish account with the same credentials without problem.




    This is with the previous workaround in  place - httpproxy.dll renamed (confirmed).



    Please help!

    BD blocked connection.jpg

    Dish login error.jpg


  • Any progress in resolving this issue?


    Thx.


    Aloke



  • On 1/19/2019 at 2:50 PM, alokep said:



    Any progress in resolving this issue?


    Thx.


    Aloke



    Hello,


    The issue is still under investigation by our development team. In case you want to be notified by our team when the fix is released, please send us an email at [email protected]


  • Thanks for the update.


    Please post here as well, so that others can know of the fixes.


    Aloke.

This discussion has been closed.