View Full Version : Enterprise Edition Client Update
squarepegs
March 18th, 2005, 02:09 AM
My problem is with client update in a SOHO W2K3 Domain, XP Pro SP2. RAC is installed on server, standard edition on XP machines.
I have set NOD32 on XP to update from my server but am unable to get it working with access denied errors. The update on clients is set to use my NOD32 username and password. I have also tried the Sytem account and Domain Admin account with no progress.
What configuration/update setup do I need to get this working?
dwood
March 18th, 2005, 03:59 AM
I had this problem when setting up NOD. I had to give the Everyone group read rights to the directory being shared, even if the updates were being shared by HTTP.
Dan
squarepegs
March 18th, 2005, 05:43 AM
thanks for the suggestion. Adding the everyone group with these permissions didn't work so, for now, I've set the clients to update for NOD32 server so I can stay current. I'll keep trying and searching to see what I can come up with.
LedZep
March 18th, 2005, 06:20 AM
on the server setup a new user i.e. nod32update or similar and setup the directory with access right for the new user (not everyone group).
On your clients configure them to use your server and specify that user account and password.
Works great on locked down systems, i.e. with the everyone full access default from MS removed ;)
anotherjack
March 18th, 2005, 01:37 PM
-{ Quote: "My problem is with client update in a SOHO W2K3 Domain, XP Pro SP2. RAC is installed on server, standard edition on XP machines.
I have set NOD32 on XP to update from my server but am unable to get it working with access denied errors. The update on clients is set to use my NOD32 username and password. I have also tried the Sytem account and Domain Admin account with no progress.
What configuration/update setup do I need to get this working?" }-
Bypass all of that and forget the shared drive stuff:
1. Set your mirror up properly (I assume you've done so)
2. Set it to offer updates via HTTP: on port 8081 (the default)
3. On your clients, define a new server of http://yourserver:8081
4. Point the clients to get their updates from there
5. All done.
Jack
alglove
March 18th, 2005, 06:37 PM
I agree with anotherjack. Using the HTTP method makes file sharing permissions totally unnecessary.
squarepegs
March 18th, 2005, 07:23 PM
thanks - using http method has worked
vBulletin® Copyright ©2000-2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums