NOD32 Updates on Win2K PC

NOD32 installation was run from the network using a config file for all machines at site. Most of the clients are Windows 9x and everything worked perfectly with these. Absolutely seamless and the config file method of installation is nothing short of a dream.

However, problems arose trying to run the updater from a Windows 2000 client connecting to the mirror on an NT4.0 server (SP6a). The mirror share is completely open with no access restrictions at all. The Windows 2000 machine continually requested a username and password to connect to the mirror share on the server. I tried absolutely everything under the sun - Every combination of domain, username and password that I could think of and they all failed. No way could I get it to update. I've even tried creating a specific user with access to the mirror. I also tried mapping drives to the mirror and got exactly the same result.

 

There are two common pitfalls when updating NOD32 over a LAN.

Here's a quick walkthrough I made earlier:

[hr]
On mirror-machine: (computer name: THESERVER)

- Download from NOD32-server using the username and password received at purchase.

- In the mirror setup, choose which versions to create mirrors for.

- Enter a path to an existing directory where the mirror files should be stored. (for example: C:\Program Files\ESET\NOD32UPD)

- Share that folder, giving read access to an account on the mirror-machine. (For example, create the account "noduser") Share the folder as "NOD32UPD".

- No username/password should be entered in the mirror setup.
------

On client machine:

- Open NOD32 Control Center.

- Click the "Servers..." button.

- COMMON PITFALL 1: Add the server: file://THESERVER/NOD32UPD

- COMMON PITFALL 2: Enter the username and password to access the updates. The username in this example should be: THESERVER\noduser
The password should be the password of the user "noduser" on the computer with the mirrors (THESERVER)
[hr]

Best regards,
Anders
EuroSecure

 

The setup is as you describe - all standard stuff. Pitfall 1 is kinda
obvious... can't find the share without specifying the box that it is on
and Pitfall 2 is an NT thingy requiring identification of the security
provider.

Only difference is that because of the network, I used a silent install
with a config script. It worked absolutely 110% with all the machines
except the W2K one. All the others boxes are Win 9x. I do believe that
this issue relates back to UNC path access authentication within NT (and
subsequently W2K) and I seem to recall spotting a document covering this
problem somewhere on the TechNet in the dark past.

Mapped drives aren't causing any problems at all. It's just the UNC access
from NOD32.

richard

 

This sounds very familiar - when I first bought NOD32, I tried to get a mirror to work.......... in the end I gave up & got the client PCs to update direct from the web.

The symptoms I came up against were exactly the same as Richard's.

 

Hey Richard,

have you seen our FAQ at:

http://www.nod32.com/support/ans/4m.htm ?

Hope it helps. If not, write again.

regards,

jan