When loading a .bam file containing a hierarchy of 2 GeomNodes, where the child GeomNode has a TextureAttrib that turns off specific texture stages used by the parent GeomNode, it can happen (randomly, it seems) that one of the stages is set to "on" for the child - at least in the net render state, even though in the local render state it is correctly turned off.

So if the texture stages used for the parent GeomNode are called "stage1" and "stage2", then the expected results for the child GeomNode would be:

child texture stages off: ["stage1", "stage2"]
child texture stages on: []

And while that is indeed always the case for the local render state, it can happen that for the net render state I get this:

child texture stages off: []
child texture stages on: ["stage2"] # this should be empty

Related topic containing more info and sample code can be found here.

As mentioned before, it can take a few runs of the code to see different results.