NOD32 help .... LAN mirror set-up

  • Thread starter Thread starter Tx2
  • Start date Start date
T

Tx2

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, named PC1) has internet access (via dial-up AOL)

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

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

PC1 seems to update the mirror folder when updating the
signature files off the internet.

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

On the client machines, i have added the update server as
\\PC1\mirror\ which i believe to be the correct path
to PC1 across the network

(please advise if i have set this incorrectly)

I have also ticked to enable access via HTTP on the PC1 mirror set-up.

When i go to update the client, it appears to be connecting, but then 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 PC1 accesses the
internet update server with) or the username and password used in the
mirror set-up, of which none are actually completed, it's just blank
fields?

Or is it XP Home trying to authenticate the request, although the
request box looks nothing like the usual XP network authentication?

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

There are no problems with shares on the machines, and each machine can
access shares on the others. I can access the c:\mirror folder in
Network Places by simply clicking on it.

Surely i don't have to set a user account on PC1 for all the other
clients? That would be madness in a larger network!


Help!!
 
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, named PC1) has internet access (via dial-up AOL)

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

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

PC1 seems to update the mirror folder when updating the
signature files off the internet.

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

On the client machines, i have added the update server as
\\PC1\mirror\ which i believe to be the correct path
to PC1 across the network

(please advise if i have set this incorrectly)

I have also ticked to enable access via HTTP on the PC1 mirror set-up.

When i go to update the client, it appears to be connecting, but then 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 PC1 accesses the
internet update server with) or the username and password used in the
mirror set-up, of which none are actually completed, it's just blank
fields?
Click to expand...

It wants the Eset user-id and PSW.
Or is it XP Home trying to authenticate the request, although the
request box looks nothing like the usual XP network authentication?

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

To access NT based O/S machines on a network, the user-id and PSW on all
machines must be the same as the machine being accessed, to avoid user-id
and psw authentication. Otherwise, the Account Authentication Process by
the machine being accessed is going to ask for the user-id and psw.

What you could do is set up a special account on the main machine like
user-id = eset and psw = eset1 and create the account on all machines.

Then if it's an eset.(exe) on the other machines that is accessing the
mirror file, you can right click eset.exe and go to Properties and select
*Run AS* and select the eset user account which should have the
privileges to access the mirror file.

That's if NTFS is being used. You can also set the Authenticated Users
account on the directory where the mirror file is located.

The link for XP shows and explains the use of Authenticated Users account
on shares.

http://www.uksecurityonline.com/index5.php
There are no problems with shares on the machines, and each machine can
access shares on the others. I can access the c:\mirror folder in
Network Places by simply clicking on it.

Surely i don't have to set a user account on PC1 for all the other
clients? That would be madness in a larger network!
Click to expand...

Why not? <g>

Duane :)
 
[...]

It wants the Eset user-id and PSW.
Click to expand...


Yes, i suspect you are right, i was just hoping it was not going to be
the case as it will mean setting up all users on the host system, a pain
in the a*se if ever there was one!

I am waiting to hear from UK support on Monday morning over the matter,
and will post back thereafter, but thanks for the input.
 
[...]

Surely i don't have to set a user account on PC1 for all the other
clients?
Click to expand...


No, i didn't .... it was simply a configuration setting i had missed
involving connecting via the LAN as the currently logged on user!

No need to set up accounts on the admin machine or concern myself with
authentication issues ....

TA
 
Back
Top