Windows 10/Backburner 2019 - Could not broadcast Find_Servers request

[miketruly]

Windows 10 (latest updates) / Backburner 2019

When the Backburner Manager opens, there are repeated warnings in the window:

Could not broadcast Find_Servers request on lo: etc.

Could not broadcast Discover_Servers request on lo: etc.

over time, these errors will repeat again and again.  Others have had this problem and I found this thread about the issue:

https://forums.autodesk.com/t5/3ds-max-forum/backburner-2016-manager-issue/m-p/7283523#M142858

I have tried the supposed solution in that thread (which is basically disable IPv6, disable your NICs, put settings into Manager/Server, re-enable your NICs, etc.) and it doesn't work.  If it does work immediately after the voodoo, it won't work after the next reboot.

Just wondering if there are any other things to try to stop these warning messages?

Thanks!

[darawork]

Pulze Render Manager?

I'd also try to check Autodesk Acess app. There might be an update missing? Sometimes the push notification on accounts pages don't update. Hotfix might be there. It's a complex situation. Render Engine could be at fault.
Is there any dmp?

Regards,

[Diffus3d]

I have had this problem when I had 2 network connections and it was looking on the wrong one.  I disabled the 2nd one and it resolved, but I don't know if that will work in your case.  Some motherboards have a built in wifi and a wired network adapter and that was my problem, I didn't need the built in wifi as it was slower anyways.  I disabled it in the bios and that did the trick.  For me.  

Best Regards,

[miketruly]

Thanks very much for the ideas!  I will look into this further.

My workstation is a multi-boot system which can boot into either Windows 7 or Windows 10.  On the Windows 7 side, I have multiple versions of MAX and am running Backburner 2014 which works with MAX2012-2020.  The Windows 10 side is using Backburner 2019 which has this error message problem but works with MAX2020-2024.  (wondering if BB2014 would work with MAX2024?).

I checked in the BIOS and there is no WIFI on the motherboard but there are 2 LAN adapters.  Only one is enabled in Win10 but I went ahead and disabled the other in the BIOS too but this makes no difference.  IPv6 is also disabled in the registry.

Will keep trying!

[Diffus3d]

Dang!   Well it was worth a shot.   Is it possible that the windows firewall (or 3rd party firewall) is blocking connections?  

[miketruly]

Thanks again for the ideas.

In the 'Allow an app through Windows Firewall' section, there were two entries for Backburner Manager Application (possibly because of installing BB a couple of times?).  One with a check on Private and one with a check on Public.  Removed the second entry completely.  Tried also checking Public on the first entry... made no difference.

Tried running Manager as Administrator... made no difference (I am the Administrator).

Right-clicked the Manager.exe file and went to Properties>Security and Admins have Full Control and regular Users have Read/Execute and Read.  Again, I'm the Admin so I should have full control.

Sigh...

Thanks again.

[Diffus3d]

Is backburner running as a service in the Win10 installation?  Or as an app?  If it's a service, often times that uses the "system" user which doesn't have full admin control.   Might be worth a look.  This particular issue has been a problem for me in the past and it wasn't easy to fix.  Backburner is such a pain sometimes.  

Best Regards,

[Diffus3d]

I had a thought, since it's working on the Win7 install, maybe you can look at the backburner logs and see if it's using the same settings as the Win10 version.  If not, perhaps you can copy/paste the settings from the win 7 into the win 10 version.   Am I making sense?

Best Regards,

[miketruly]

Thanks again for the ideas!

Manager.exe is run as an app from the Startup folder in my User folder (and I'm the Admin).  At one point, I also closed Manager and did a 'Run as Administrator' on it but the warnings still happen.

For grins... I wanted to try running Manager as a service but can't remember the method to get it going as a service.  In the Backburner folder. there is managersvc.exe.  When I double-click that EXE or Run as Administrator, I can see a command prompt executing something but when I go look in Services... I can't find Manager listed.

I will try to compare the older Backburner 2014 setup vs the newer Backburner 2019 setup and see if anything jumps out at me.

Thanks again.

[Diffus3d]

You are super thorough Mr. Truly.   Maybe you can post the backburner log files for both, I'm happy to look at them and maybe together we can find the difference between them.  

Best Regards,

[miketruly]

The only significant difference between the 2014 and 2019 Backburner log files is the IP address shown just prior to the 'Wiretap connected' line.

The BB 2014 log shows the IP address of the Manager computer and the BB 2019 log shows the (localhost?) IP address.  BB Manager has NO setting where you specify an IP address for anything.  BB Server does have settings where you set the name or IP address but Server hasn't been started yet... so I wonder where Manager is getting these IP addresses from?

Not sure if that localhost IP address is what's triggering the warnings or not.  I'm inclined to think that the warnings could be either internal coding changes in later versions of Backburner or the wacky security world of recent versions of Windows or both.

Right now Backburner is working for me but these warnings are annoying at the least.

Thanks again.

[miketruly]

Oh and I should also mention, all the other stuff in the BB 2014 log is BB complaining about old versions of MAX (2010/2012) that it doesn't want to load, etc.  So nothing related to the warnings.

[Diffus3d]

127.0.0.1 is generally known as 'localhost', which means a server on the local machine.  It could be that it's the service version of backburner running on your local machine after the previous test.  I know you said you don't see it, but it should be there somewhere.  Make sure you're looking in services.msc  instead of the one in task manager.  (Just search for services.msc check the list under backburner and autodesk.)  

Actually, before you try that maybe we should try pinging that machine manually.  Here's how you do it:

1) Type 'cmd' in a windows search bar, it should bring up  a search with cmd.exe on the top.   Click that.  

2) Type ping -a <the ip address from 2014>.  Does it work?   If not, a firewall is blocking it without a doubt.  If so, 

3) Take the IP address from the 2014 and replace that in the other one (after making a backup) and save.   Hopefully that does it.

Please note I am not 100% sure what the problem is that these steps are meant to help narrow things down.  Thanks for your patience.

Best Regards,

[miketruly]

Both the workstation IP address and the localhost IP address are pingable... tried that earlier.  (All computers on my network use static IP addresses except my wife's laptop which is DHCP).

When I was earlier trying to install Manager as a service as a test... I was fumbling it from memory and didn't get it installed (have since found the instructions which say it must be done from the Command Prompt).  I re-checked Services and it doesn't appear that Manager is there... no Backburner and the two Autodesk entries are for licensing, etc.

Those log files reflect ONLY Manager running.  And there is NO setting within Manager where you specify an IP address.  So it's a bit of a mystery as to where that New Client is coming from and why BB2014 displays the correct workstation IP address but BB2019 displays the localhost IP address.  If I later start Queue Monitor, then another 'New Client' line with the proper workstation IP address is displayed.  If I later start Server, then a 'Successful registration' line with the proper workstation name is displayed.

Anyway, it may not be related to the warnings but it's the only visible difference between the two version log files.

Regarding the firewall, Backburner is allowed on the Private Network.

Thanks again!

[Diffus3d]

Wow.  You are thorough, no doubt about it.  I'm starting to run out of ideas.  Any chance there's a 3rd party firewall in effect? 

Ok so the facts are: pinging works, so the connection is going out.  Network discovery is possibly having trouble on the Windows 10 machine (it seems), but is working on the Windows 7 machine.   I remember something about changes to how homegroups work....  let me see if I can find the article.     Found it!   Have you seen this article? 

Let me be clear that I am guessing about a lot of things here and I apologize if it's going on too long.  

Best Regards,

[miketruly]

Thanks again for the ideas.

No other firewall in use.  I have that article bookmarked and have tried those settings changes with no effect.  That article seems to relate to servers not connecting and Backburner not rendering jobs.  (There's even a line in there about the warnings continuing even after the servers connecting problem has been resolved with those settings changes).

Backburner 2019  is functioning OK at the moment, aside from those warnings continuing.  So that's most important to me.  I will keep trying for a solution and report back if I ever find one.

Thanks again.

[Diffus3d]

Sorry things didn't work out.  It's a strange issue.  

Best Regards,