[Crossle86]

An update on this issue. Yesterday during testing I observed a case where the DS and development PC were both connected to the RR and operating normally. There had been several successful code downloads. Then on the next code download, the development PC could not find the RR IP address via mDNS (as reported by the build script). A ping from devPC did ping the known ip address of the RR. The DS remained connected during all of this. Then as I was contemplating what I had just seen with my devPC, the DS connection to the RR was dropped for no apparent reason. The DS would not then reconnect. Ping from DS to RR was successful. Both the devPC and DS had to have the wireless connection to the router disconnected and reconnected to get them both to find and connect to the RR. Then the rest of the test session there were no problem.

My gut feeling is that mDNS either on the PCs or the RR is failing to respond and report the RR ip address. I am assuming the build scripts and DS do not cache the ip address though mDNS doc suggests that the mDNS service caches. So its not clear if mDNS is failing of if there is a connection issue once the PCs have an ip address either from mDNS response or cache.

If I had more time I would set up network monitoring and try to catch this issue and be able to narrow it down, but our team just does not have time for this kind of thing as we are late getting the machine done. We are planning a major test session tomorrow on a full field so I will collect what information I can if we see this problem then.