Mirror LAN updates .... username and password required?

I have just set up NOD32 on a 6 user licence.

The network consists of 6 WinXP Home machines, only 1 of which (the admin machine) has internet access (via dial-up AOL)

Each of the other 5 LAN clients has been setup with the standard NOD32.
The internet enabled machine has the admin version on it.

I have set up the signature mirror in a folder on the admin machine, the local path being c:\mirror, and have enabled sharing.

The admin machine seems to update the mirror folder without issue when updating the signature files off the internet.

There are no username or password parameters set in the mirror set up

On the client machine, i have added the update server as \\<admin machine name>\mirror\ (i actually used forward slashes, but NOD changes them to backslashes) which i believe to be the correct path to the admin machine across the network (please advise if i have set this incorrectly)

When i go to update the client, it always asks me for a username and password, but i don't know which username and password it wants - the licence username and password that ESET provide when you buy the product (and the one the admin machine access the internet update server with) or the username and password used in the mirror set-up, of which none are?

I am tearing my hair out here as i believe each machine can see the update mirror, but why each one needs a user and pass to access it i don't know!

Or should i have installed the admin version on each machine? (i think not)

There are no problems with shares on the machines, and each machine can access shares on the others.

Help !!

 

Hi,

I ran into the same problem while testing when NOT using the http server. If you put in the user accounts for each machine into your users, then it will d/l properly.

Example. Machine one, user name windowsxp1
password ............
add this to your server users in the control panel.

NOTE: Use gpedit.msc to prevent all the user accounts from showing up on your log in screen.

Add this to your users on the server machine and NOD should update no problem. This is how I got around it.

 

So this is a windows XP thing, in that because the machine trying to access the update files isn't a user on the host machine, XP wants to authenticate the request with a username and password?

I know how to set up users on XP machines, and this is not a big problem for the 6 machine network i am managing, but if i had 60 machines, i'd be pretty fed up having to do this!

I have the HTTP option set, maybe i will try without?

Surely ESET have a work around of sorts? Maybe i have made a big mistake becoming a reseller ........ ?

Of course, it might just be me

 

Well lets put it this way. With 60 users you wouldn't be using peer to peer now would you?? You'd be using a domain controller or active directory to admin all the users. You can still use the http option which has been discussed here many times. I just prefer to use this method. If you search the forum you'll see a number of posts using the http method and it is also outlined in the help files and the latest stuff from Kirk had this method of install outlined as well.

Take Care

 

This may help.

Each user can see the share, but NOD32 does not pass each user's credentials. NOD32 must be supplied with the credentials.

In the nod32.xml (or whatever you named the file) file under update, you supply the username/password to access the share through NOD32.

username/password could be (make this user on the update box)
updateboxname\nod32
password=nod32

 

There is a manual for network administrators available on our website, which deals with that. Generally, you have 3 options:
1. access update files through HTTP (no user/pass is required)
2. in advanced update setup, set the option to connect to the update server to currently logged user (no user/pass will be required to enter, NOD32 will get that info from the system)
3. put domain(workgroup)\computer_name into the username field in update setup, even if no password is set

 

You'll be sorry to learn i couldn't get any of them working Marcos.

The PC that has the mirror on it has internet access, the one that gets the update from the mirror doesn't. I have no idea which option to set for my scenario. The manual doesn't go into enough detail about this.

 

I'm not using an .xml file .... do i explicity have to? If this is the case, then Aspect Systems in the UK (the UK supplier of NOD32) have been telling me the incorrect information about NOD32, as i have been told (in an email which i still have) that i simply needed to input the mirror location as \\server\path\ and that would be it. Clearly this is not the case....

 

I always suggest to use the http-option.

What happens if you do the following:

1. Tell the mirroring computer to have HTTP enabled ("Enable access to files via HTTP protocol")
2. Click "Advanced" in the mirror-setup to see which port is used (8081)
3. Check what local IP the computer has (for example 10.0.0.15)
4. On the computer with only LAN-access, add the following server:
http://10.0.0.15:8081
5. Make sure you have the added server selected as update server, and that the username and password fields are emtpy.
6. Click "Update now".

What happens? If it doesn't work, what error do you get on the client? (check the NOD32 log in the NOD32 Control Center)

Best regards,
Anders

 

OK, but on this occasion i haven't used HTTP, nor had to set any accounts up on the admin machine for the other machines on the network, or had to configure an XML file.

It was as simple as ticking a box in the LAN config on the client machnie, a box which isn't detailed anywhere in the manuals i could see.

Thanks goes to Aspect Systems in the UK for their help, and others who made the suggestions they did.

 

And to finish the story......

What box would that be?

 

Bump?

And to finish the story......

What box would that be?