Anyone have this problem?

Discussion in 'ESET NOD32 Antivirus' started by rugmankc, May 27, 2009.

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

    rugmankc Registered Member

    Joined:
    Jan 11, 2008
    Posts:
    179
    Location:
    Fairborn, Ohio US
    All my specs are below,

    For the last few weeks my internet connection is taken longer to go active. For a long time it was only 5-15 seconds until it connected. Now it is 1-2 minutes. I have done virus/spyware scans and have tried it in areas where there is no connection to eliminate an internet thief.

    Recently, I have found that Comodo was being put on hold while it initialized and NOD32's Antivirus and AntiSpyware was being disabled during the 1-2 minute startup. I never noticed this before, but never looked since the internet connection came up guickly.

    I uninstalled/reinstalled Comodo an NOD32, no change. I have exclusions for each of them for each other.

    Nothing done new to the laptop. Any ideas.




    Ken
     
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    I'm a little confused. How can you test the time it takes for the internet connection to become active when you have no connection? I may have just misunderstood what you meant.
     
  3. twl845

    twl845 Registered Member

    Joined:
    Apr 12, 2005
    Posts:
    4,186
    Location:
    USA
    Have you installed any new anti-spyware apps just prior to having the problem? My Firefox was taking 30 seconds to load cold, and a tip from a forum member led me to uninstall SpywareBlaster. Immediately after, FF load time was cut in half. FF loads slow any way. I hope this was a help. :)
     
  4. philby

    philby Registered Member

    Joined:
    Jan 10, 2008
    Posts:
    940
    In my experience with both EAV/ESS on three different machines, all wirelessly connected, there is a long delay at boot before any internet connectivity is established. I had the same problem of Comodo having to wait for Eset to initialise.

    Both products seem to strangle network and internet connectivity while trying to update at boot-time because of a conflict with the Windows workstation service.

    You can check this by disabling the workstation service via services.msc - you will probably see your box boot in seconds and connectivity established immediately.

    I have never found a way to have the workstation service running (essential for LAN folder sharing) and have Eset (either versions 3 or 4) not delay network/internet connectivity. I live with this on a d/t that I almost never reboot, but I've uninstalled ESS from my laptops...

    EDIT: That was a lie: on my old XP machine, unchecking "automatically detect settings" in Internet Options > Connections > LAN settings miraculously did the trick. Sadly this didn't work with Vista on board...

    Other ideas mooted in previous threads include:

    • make sure signature update is set to 'on discovery of dial-up' (can't remember exact wording) in scheduler;
    • test your system on a wired connection to see if this resolves the slow-to-connect issue - though all this will do is confirm the problem is with Eset and wireless.

    Hope this sheds some light

    philby
     
    Last edited: Jun 2, 2009
  5. rugmankc

    rugmankc Registered Member

    Joined:
    Jan 11, 2008
    Posts:
    179
    Location:
    Fairborn, Ohio US
    I do have a connection just took long to get it.

    May have solved the problem. :doubt:


    I have two "Terminal Services" in my Windows Services. One was set to Auto and one Manual. The manual one was the Terminal Services Configuration Service. It deals with remote desktop configurations and certificates. I am on a laptop connected to a wireless router. I set the service to auto like the other one. I don't know why it affected the start up with CF and NOD32, but it seems it may have. Perhaps it was taking time to activate the service from manual to on.

    Anyway, this may be a solution for others who have had CF and NOD32 initialize longer than normal. I shut down and rebooted three times now and the time from logon to internet connection and having CF and NOD32 up and running is back to five seconds or so.

    Time will tell if this fixed it. But, this the first time it has started this fast in weeks or maybe months.

    I know awhile back I disabled and/or set to manual several things I thought I didn't need. That may have been when things started to slow down, and I never made the connection.




    Thanks for all the inputs,




    Ken
     
    Last edited: Jun 2, 2009
  6. philby

    philby Registered Member

    Joined:
    Jan 10, 2008
    Posts:
    940
    Thank you - re. the Terminal Services tip.

    Will try again with Eset + Vista....:doubt:

    philby
     
  7. miki69

    miki69 Registered Member

    Joined:
    Mar 9, 2009
    Posts:
    133
    Location:
    Vienna, Austria
    Thanks for the tip, I also use NOD32 and Comodo and have noticed exactly what you have described. And yes, comodo is waiting for NOD32 to initialize or something, cause when I had uninstalled NOD32, my internet connection was instant with Comodo on.

    EDIT: I can confirm that setting it to AUTO seem to solve the problem with slow internet initialization. I wonder why ESET is silent about this issue?

    Cheers,
    Miki
     
    Last edited: Jun 2, 2009
  8. rugmankc

    rugmankc Registered Member

    Joined:
    Jan 11, 2008
    Posts:
    179
    Location:
    Fairborn, Ohio US
    You are all Welcome,


    Hope it resolves our issue permanently.




    Ken
     
  9. rugmankc

    rugmankc Registered Member

    Joined:
    Jan 11, 2008
    Posts:
    179
    Location:
    Fairborn, Ohio US
    philby,


    My workstation is auto with both terminal services set to auto also.

    Everything continues to run smooth. :D


    Ken
     
Thread Status:
Not open for further replies.