![]() |
|
#1
|
|||
|
|||
|
Recently when I boot up my Windows XP laptop I get a Server Connection Error immediately from NOD32. It would appear that the program is attempting to look for updates immendiately before I have established a wireless internet connection. I have the updates settings set to a LAN connection in NOD 32. Is there a way to ensure that the program doesn't look for updates until an internet connection is established?
|
|
#2
|
||||
|
||||
|
Try changing the connection to Dialup, in the Nod32 Control Centre> Update> Setup. Advanced.
Let us know how you go... Cheers ![]()
__________________
"Illegitimis non carborundum"
translation: "Don't let the bastards grind you down" U.S. General Joseph W. "Vinegar Joe" Stilwell (1883-1946) Two Photographers |
|
#3
|
||||
|
||||
|
darren,
it's nothing to worry about - either try the dialup change suggested by Blackspear, or ignore this harmless warning - it's not that big a deal, just a little oddity that NOD32 will be up and running before network services have been established... hth Greg
__________________
NOD32 AntiVirus Reseller (North America) |
|
#4
|
|||
|
|||
|
Actually I seemed to have solved it for now by manually initiating an update from NOD32. Once the update was completed I haven't had any further problems. I wonder whether an update may have been in progress previously when the internet connection was stopped and the program was trying to complete the download everytime I booted up. When the dialup update setting is used, does the software wait specifically for a dialup connection or just the establishment of any type of connection (ie. wireless)?
Thanks. |
|
#5
|
||||
|
||||
|
Quote:
Cheers ![]()
__________________
"Illegitimis non carborundum"
translation: "Don't let the bastards grind you down" U.S. General Joseph W. "Vinegar Joe" Stilwell (1883-1946) Two Photographers |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|