Issue
Customer gets a yellow warning message (a warning triangle) on the values presented in the graphic in Vista. The node is blinking for a while and then disappears. If mouse is held over the node when the warning comes they get message "WSAhost_not_found" This behaviour occurs from time to time and the data that are suppose to shown is then zero. After a while the data is updated again and shows the correct value.
Environment
- Vista IV Workstation
- OGC Graphics
Cause
It appears customer is having a local workgroup in the building that runs the application's. There are several computer connected with different OS and known is that several of this computer is using NT. Since this message only occur time to time and only for a brief moment a conclusion be made that it is a network error.
Resolution
Possible solution:
What needs to be tested in the location is what or whom of the computer's that has become the master browser since the master browser is holding the master list of the other computers in the network. NT system's are normally suitable of becoming a Master browser in the network since they are a "server OS" If several of this OS is on the same network a argue can occur between them who should be the master browser and this can be confusing when the clients is sending the network list to the master browser. When the client is sending the list they send it to the "server that responds first. Now when another client asks for information the server that responds first is sending the data, but this time another server can be the one answering first and don’t hold the updated list.
A possible solution to this problem is to narrow down what computer's that is master browser's on the network and choose one that always should act as one "mainly a computer that is turned on all the time" If more master browser is needed after that (most common after 32 computers) the master browser will choose one to act as a "backup Master browser". This information can be read about on Microsoft homepage.
NOTE: This can be the fault in the system, since the "list" talked about above is updated after a while when the Master browser is asking the client's on the network for a update. So when Vista make's another request of the value it works again since now the list is correctly updated.