Problems after NOD32 Network installation

Discussion in 'NOD32 version 2 Forum' started by aonderwater, Oct 4, 2007.

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

    aonderwater Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    2
    Hi all,

    I have a problem with a client after installing NOD32 from remote admin console. In this case i have more clients they dont have problems. I also think it's not because of the network push.

    The problem: after installation and a reboot i cannot get past the CTRL - ALT - DELETE screen...? And yes my mouse en keyboard are functioning ok. Never had this problem before. Also, rebooting in safe mode with network functionality has the same problem. When rebooting in safe mode without network i can get past the ctrl-alt-delete screen. Then uninstalling NOD32 with reboot solves the problemo_O So the problem lies with NOD installation presumably...

    Is this a known problem? Does someone know a solution?

    Thanks in advance!!

    Martijn
     
  2. aonderwater

    aonderwater Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    2
    It's a little bit different now.

    When the ctrl-alt-del screen pops up. I have to wait for maybe 5 minutes before i'm able to log in... (read: before i can get past ctr-alt-del screen). After that everything seems to work fine. But it takes ages. Has this something to do that the pc is in the network?? Because safe mode without network does the trick?

    I'm really stuck on this one, hopefully someone can help me or point me in the right direction.
     
  3. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    I would suggest repairing Winsock

    ALTERNATIVELY you can do the following:

    For Windows XP:

    Click on Start
    Click on Run
    Type in cmd
    Click on OK
    Type in netsh winsock reset
    (Please note there are spaces between the netsh and winsock and reset)

    Press ENTER
    Restart your computer.


    Then repair IMON; see post number 55 HERE

    Let us know how you go...

    Cheers :D
     
Thread Status:
Not open for further replies.