Discussion in 'NOD32 version 2 Forum' started by Benvan45, Jul 21, 2006.
Probably not the first time asked, but is this normal and what to do about this?
Yup, that's normal. What is happening is that the u8.eset.com server is either down or really busy, so you cannot connect to it. When this happens, NOD32 will connect to a different server, choosing from the list found at Update --> Setup --> Location. There are several servers to choose from, so even if you cannot connect to several different servers (as happened at 20-7-2006 15:22), NOD32 will eventually find one.
If there is an update available, you will see a message stating that the virus signature database was updated.
If an update is not available, then there will be no message (since there was no update). This is often a source of confusion, because people see the "Error connecting" message, but they do not see the "successful connection, but no update available" that happens 10 seconds later (when NOD32 goes to the next update server).
Ok, thanks for the info and I understand that updating goes on all right.
Separate names with a comma.