Backburner - Error sending on UDP....

[Superla-Envoke]

Hello,

I have an issue with a rendernode Server.

When I start Server I get the error

Error sending on UDP to 192.168.0.38: A socket operation was appempted to an unreachable network. (0x2743).

The node has just been formatted with a re-install of Windows 10 Pro, Max 2021.

Before the format, the server was working fine.

The other nodes and machines are all working fine.

The server is able to see, read and write to the networked drives too.

I have tried a few things that I've Googled, but nothing is working. Any suggestions?

Thanks,
Dean

[Superla-Envoke]

after a lot of cocking around, it appears it was a firewall issue. I deleted the server name, restarted the server, and then the firewall pop up appeared, asking for access. Clicked Allow, and it's all fine now.

#nevereasy

[jon.bell]

Hi Dean,

Thanks for your question and update on this. An "unreachable network" issue is usually a Windows 10 networking problem (often seen after an update), but since Backburner is admittedly a legacy 32-bit application, it doesn't have a robust error-checking system for these types of issues.

For future reference, here's a quick checklist of problems/solutions if you want to continue using Backburner:

Backburner requires numerous factors to be in alignment to function properly. Check the Backburner logs and try any of the following that apply:

• Reset preferences by using Reset Backburner user settings to default.

• Refusing its own connection:

• Temporarily disable the firewall to see if it is causing conflicts.
• If yes, then please allow firewall exceptions - 3ds Max: Firewall and Antivirus configuration for Backburner

• The pipe has been ended: 109

Plug-in check

•  An existing connection was forcibly closed by the remote host (0x2746).

Permissions and Firewalls

• Servers aren't connecting to Manager.

Identical versions and Workgroups

• Backburner Error Code (0x2741).

Change the server name

• An address incompatible with the requested protocol was used. (0x273f)

Prefer IPv4 over IPv6

• Adapter returned unexpected code -2 pipe has ended

Perform a Clean Uninstall - Download & Install

• An operation was attempted on something that is not a socket. (0x2736)

Guidance for configuring IPv6 in Windows for advanced users -- download and run the Prefer IPv4 over IPv6 in Prefix Policies fix

Finally, if you want to investigate 3rd-party replacements for Backburner, please see this list.

Let us know if this helps!

[pierschapman]

Ok here's what I had to do recently for some clean reinstall systems. With windows10 you can set ipv4 to a higher priority than ipv6 this appears better than disabling ipv6 altogether which may impact some other things adversely.

Hit start - type CMD to open an administrator level command prompt window -then follow steps below:

(taken from https://kb.firedaemon.com/support/solutions/articles/4000160803-prioritising-ipv4-over-ipv6-on-windo... )

In your elevated command prompt type:

netsh interface ipv6 show prefixpolicies

You should see the following output:

Precedence  Label  Prefix
----------  -----  --------------------------------
        50      0  ::1/128
        40      1  ::/0
        35      4  ::ffff:0:0/96
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

The first line with a precedence of 50 is the IPv6 loopback adapter. The second line with a precedence of 40 is the IPv6 default gateway. The third with a precedence of 35 is all IPv4 compatible addresses. To change the precedence, type the following:

netsh interface ipv6 set prefixpolicy ::ffff:0:0/96 46 4

The value 46 is the new precedence. Windows uses this value order prefix lists based on destination. The lower the value, the less preferred that destination is. The value of 4 is the label. Windows uses this value to order the source preference based on the destination prefix. Then type:

netsh interface ipv6 show prefixpolicies

You will now see the priority has changed as follows:

Precedence  Label  Prefix
----------  -----  --------------------------------
        50      0  ::1/128
        46      4  ::ffff:0:0/96
        40      1  ::/0
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

 I hope that helps some people.

Feedback for Autodesk staff: (@jon.bell )  Autodesk are selling an animation product - but your code teams no longer feel like you have to update or support parts of the product that are essential to making animation production possible e.g. network rendering dialogues inside max are broken and revert to default settings as appeared in Max2019 wasn't patched, still broken in Max2020 and still broken in Max2021. Backburner gets more and more broken each year, requiring more and more specialised work arounds (especially with the prefer ipv4 over ipv6 stuff). Getting server to automatically start up at boot gets more and more annoying each year. Even non-critical stuff stuff like Monitor for example can't even tell how many CPUs modern computers have (can't count above 32cpu cores)  appears symptomatic of just not caring about a significant segment of customers. List goes on and on. Why isn't there a proper 64Bit update to backburner systems installed as default?

What's the end goal, losing your animation customers? An animation product that doesn't properly support rendering large numbers of frames in realistic timeframes is not a very viable animation product.

[jon.bell]

Hi @pierschapman,

Thank you for your help on this and your comments about Backburner. I've passed them along to the product development team and upper management, and for the record, I completely understand your frustration about this.

If you have any other questions or comments about this, please let me know.

[Anonymous]

100% what @pierschapman said