0

BrightAuthor 2.3.0.57 Bug report



After launching Brightauthor all Brightsigns on the loacal network are discovered through Bonjour. Brightsigns can be updated and written to. The Bug; Click on the edit tab, edit a playlist,....... go back to "publish" "Local Network"......Very often, the discovered Brighsigns are gone. No amount of elapsed time or clicking of the refresh button has any effect. Close down and then Re-launch BrightAuthor to re discover the Brightsigns. Only then can the edited program be uploaded.

10 comments

  • 0
    Avatar
    Brian2


    More on the discovery Bug !

    At one particular client, the brightsign units will rarely although they do very occasionally get discovered.
    The work around is to reboot no SD card on one of the units, note the IP address and then after rebooting again normally, enter the IP address manually.
    This is the strange part, not only does one see the particular unit entered in manually, the rest of the other system Brightsigns are also then discovered.
  • 0
    Avatar
    Pan Pacific Perth IT


    Hmm, I just tried rebooting a unit and adding it via its IP.  None of the other units were detected unfortunately.
  • 0
    Avatar
    RokuLyndon



    There's a utility you can download, http://www.nirsoft.net/utils/socket_sniffer.html">http://www.nirsoft.net/utils/socket_sniffer.html, that you can use to monitor communication from the BrightAuthor software. I'd be curious to an html report from it watching brightauthor as you try to discover or publish to the brightsign.

    If bonjour is used for discovery, bonjour works normally on udp port 5354. At least, that's the port it uses on my system. BrightAuthor connects to port 8080 on the BrightSign.

  • 0
    Avatar
    Pan Pacific Perth IT


    Ok, I've run Brightauthor with the packet sniffer running.

    Amazingly, when Brightauthor first started up, it actually detected a bunch of units.  When I hit 'refresh', they all disappeared.

    Shall I just email the report to support?  Looking at the results from the sniffer, it seems like Brightauthor is getting a response from all the units on the network, it's just not displaying them.
  • 0
    Avatar
    Brian2


    Yep, I am getting the same.
    No problems on my simple test rig at our office, ( router and 4 Brightsigns )  but the moment I go back to the clients large LAN structure, discovery once again very unstable.
    Sometimes OK when Brightauthor first launched, nothing after re-fresh.
  • 0
    Avatar
    RokuLyndon



    And, it's not possible to manually assign the IPs on the client's network? Some networks block broadcast traffic like upnp and bonjour. THere's a utility I found on since called socket sniffer.

    http://www.nirsoft.net/utils/socket_sniffer.html

    I would be curious to see the results if you ran it on the client system, and told it to monitor BrightAuthor.  It should show discovery packets on port 5354 udp, and then brightauthor trying to communicate with the IP address of the brightsign on port 8080 on the unit.

  • 0
    Avatar
    Brian2


    More on the Bug.
    In an effort to update the Brightsigns, three units rebooted without SD cards to ascertain assigned ip address.
    Rebooted again with SD card back,  was going to manually enter ip address in Brightautor hoping it had been assigned an address close to the ones previously noted.

    BUT after launching brightauthor,  brightauthor discovered the re booted brightsigns plus all the other missing ones.

    Hope that helps with the diagnosis. I will run the packet sniffers when it happens again.   All the brightsigns were at the time displaying correctly.
  • 0
    Avatar
    Pan Pacific Perth IT

     

    "brianshirley" wrote:

    Yep, I am getting the same.
    No problems on my simple test rig at our office, ( router and 4 Brightsigns )  but the moment I go back to the clients large LAN structure, discovery once again very unstable.
    Sometimes OK when Brightauthor first launched, nothing after re-fresh.



    My network is a bunch of Cisco 3560s but nothing complex aside from a bunch of VLANs.  At the moment I've just assigned reservations on the DHCP server, but could probably give them static IPs if need be.

    The autodetection would be nice to have working though.:) 

  • 0
    Avatar
    RokuLyndon


    Can you also try the socketsniffer utility so I can see if there's anything different about the communication? On my system, wh en I had that utility running, every time I go into publish, I see communication over port 5354, and then to port 8080 on the unit.
  • 0
    Avatar
    Brian2


    OK socketSniffer files submitted to help desk.
    Request #4886
Please sign in to leave a comment.