I don't recall reading it in the EULA, but I now understand, after reading many of the NOD32 FAQ's here, that the copy of NOD32 which I paid for and DL'd is just like Windows XP, i.e., one copy per home computer. If one has two home computers, whether connected on a LAN or not, one must pay for, download, and install a second copy of NOD32. Caveat emptor, right, or "read the small print stupid." Swell. Now I understand why the Eset rep in Coronado, CA (where I once lived and worked as a young, bachelor naval aviator stationed at NAS North Island in the '60's) was less interested in answering my question than he was in giving me a hard time when he discovered (I had told him in my email request for help--it was no secret and I wasn't trying to pull a fast one on Eset!) that I had burned a copy on a CD and installed it on our second networked computer. I was never able to get NOD32 updates on the client computer, but for some time it wasn't necessary as the NOD32 control center on the server (master) computer showed the shared drives on the client computer along with those on the server and allowed me to include drives on both computers when scanning. Therefore, the updated NOD32 files on the server sufficed. For some reason, the client computer's shared drives stop being shown about the time I DLd and installed Windows XP SP1. The FAQ article on updating (or even connecting for that matter) a second networked computer with new virus definitions appears to be will written and takes one through the necessary steps in a logical progression. However, I can't find any of the options that address the step calling for a "mirror." Any clarification from anyone using a LAN with a second client computer who is able to scan server files and shared client files with NOD32 would really be appreciated. My thanks to any respondent.