Nod32 lan update server and linksys router

Discussion in 'NOD32 version 2 Forum' started by cism, Aug 10, 2006.

Thread Status:
Not open for further replies.
  1. cism

    cism Registered Member

    Joined:
    Aug 10, 2006
    Posts:
    6
    Hello,
    I am having trouble setting up the nod32 http server at our office.
    I have enabled mirror, set the folder to c:\data\nod32, port 8081 and enabled port forwarding 8081 to our server.

    When other remote offices connect, they just connect and disconnect without giving any error. I have set the username and password but when they connect, a dialog of username password doesn't appear. I have tried system account, current user and specified user but none of them work.

    On the linksys router I have also tried DMZ. The model is a WRV54G with the latest firmware. On the IP address, I have used the dyndns function of the linksys router and made a fully qualified domain name (specifically for vpn and now nod32) and also directly entering the IP address.

    Am I missing something?

    Thanks
     
  2. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    If I correctly understand, you currently have your update mirror accessible from the internet, which is not good.
    IMHO to do this it would be best to use a VPN tunnel, otherwise can you set up a mirror at each location?

    Cheers :)
     
  3. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    Are they able to pull the updates if you don't set a user/pass?

    Much as I like Linksys routers..the wrv54g was known to be a bit buggy with earlier firmware..is the firmware up to date?
     
  4. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Are you having problems only with the remote offices? Does the mirror work OK inside the LAN? For the Update username/password, are you using the ones from NOD32, as opposed to any sort of Windows password?
     
  5. hasit

    hasit Registered Member

    Joined:
    Jul 24, 2006
    Posts:
    44
    can you please try to enable the http access in the mirror's settings and try to open the following and tell me what you see.

    http://192.168.0.1:8081/update.ver OR http://serverip:8081/update.ver
     
  6. cism

    cism Registered Member

    Joined:
    Aug 10, 2006
    Posts:
    6
    I have solved the problem. It seems that there was a problem with the windows firewall even though I have opened a port in zonealarm :rolleyes:
    Anyway is it recomended to have a software firewall even if the workstation is behind the routers nat firewall?

    On the followup question.
    How can I make the nod32 secure by making a username password.
    I see 2 fields that has a user pswd. 1st the access to update files and 2nd is in the advanced button "Specified User". What's the difference between the 2?

    If the main and remote offices are in the same workgroup I would only need to enable current user in "connect to update server as"?
     
  7. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    The first username/password combo is the NOD32 key. This is to make sure that your license is valid and you are entitled to download the updates.

    The second username/password is if your mirror is set up as a Windows file share on the server. That would be the Windows username/password needed to access the share.

    Since your mirror is set up using HTTP:8081, you do not use the second username/password. The clients are accessing the mirror with pure TCP/IP, not with Windows networking. The workgroup, Windows logins, etc., do not matter in this case. The only one that matters is the NOD32 license username/password.
     
  8. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    to add to what algove said - the http method of updates from your local mirror is not login/password protected - also, there is no logging - so if you have an open mirror accessible via the internet, it's open to potential abuse if it's found. Protection and/or logging were something I requested be added to the wishlist over a year ago... I'm not sure if they'll come though.
     
Thread Status:
Not open for further replies.