Solved Delay ethernet starting?

[Scottyboy99]

Sorry i have posted similar before. If I don't boot my laptop for 24 hours with ethernet attached I always see a slight login delay of about 10-15 secs stuck on 'welcome to windows' . It is pretty annoying. Subsequent boots within 24 hours are always then instant. But as soon as 1 day has elapsed since last shutdown it is back! And under wifi only i never get this problem. I can only think that every 24 hours after last shutdown there is some kind of scan / timeout related to the network that causes the delay scheduled at start up. I guess wifi does not get affected as the drivers don't load in as early as ethernet so whatever scans/times out does not get a chance to start/run, if that makes sense. Anyway I have tried so much to fix this without joy. The only thing I can hope is to somehow delay the ethernet adapter to become active later in the start up. Is this possible at all? I know I can just disconnect the cable and plug in after boot but I want the process to be a bit more automated as it should be.

Cheers
Wayne

 

[PeaB4YouGo]

I wondered, about a week ago, if this was still an issue for you. Still can't think of a way to delay the initialization of the ethernet card, but I'm nearly convinced that it has something to do with the router side of the network you're on. Anyhow, good luck and all. Just had to pipe in.

For those who are new to the issue, here's a link to the original conversation; Wired adapter issue

 

[Scottyboy99]

You might be right on the router. But I just wonder why wifi only is perfect. I would if thought both would exhibit same delay. Am obviously doing my best not to have to buy a new router due to the fact of cost and this one (netgear 3700) is reasonably high end. Of course I'd hate to lay out for a new router only to find the issue is still there. I wish I had another laptop I could try to see if same happens to one of them. It's not that we don't have another one, in fact we have two but they are mechanical hard drive only and such slow booters anyway it is impossible to tell. The fact that this machine boots using a cache SSD makes the delay after 24 hours very noticeable.

I do apologise, maybe I shouldn't of started a new thread but added to the original. I just thought maybe a new one to see if ethernet initialisation could be delayed. I do appreciate your taking time to reply. I hope someone has a suggestion. At the moment I'm stuck and am struggling to contemplate a new router. If I knew it was a guaranteed fix I'd take the plunge!

Cheers
Wayne

 

[Persons Can Wai]

I am really wondering, is there any program that documents the startup process? You could try to have this inject itself at the beginning of boot time for logging purposes. It may be able to show you what is loading and how long it takes, then you can narrow down where the problem lies. There's got to be something like this but I have no idea on what they are.

Is your NetGear router up to do date with the latest firmware? How much are you willing to experiment? You could try putting it back to the factory firmware (downgrade), and test to see if the issue exists. Try for some time, then upgrade it, test again. If it supports third party firmware (Open WRT, tomato, etc), you could try loading one of those on and seeing if the issue persists with that too. If it happens with only the official ones, well you know that something in them is causing it. Don't you also have different Ethernet ports on the back of your router? Have you tried plugging it into different slots and seeing if that helps? Maybe one is damaged.

Do you also have a warranty for the router? If all else fails maybe you can get a free replacement/upgrade, and maybe that one will not be affected.

 

[PeaB4YouGo]

You might try giving NetGear a buzz (email, tech support call, etc).

They may have an explanation, at least, if not a solution.

 

[Scottyboy99]

Sorry for long gap in updating this thread. This bizarre issue continues with ethernet only after 24 hours. What I do know now is it is definetely nothing to do with the router. I swapped out the router with two different models. I made sure my laptop was the only device connected and had the exact same issue. So it's something to do with windows 7. Verbose boot revealed nothing. It just says 'preparing desktop' at the offending point. I am baffled beyond belief. Something after 24 hours exact is causing this. Drivers updated, IP changed between static and dhcp. Not sure what else to try. I hope someone has some pearls of wisdom. I could ignore wired and use wifi instead but I feel this is a frustrating issue.


Cheers guys

 

[PeaB4YouGo]

Here's on for ya!

Do you have any icons on the desktop that are actually shortcuts to files on another drive on the network?

 

[Scottyboy99]

Good suggestion. Unfortunately not, I even checked recent documents in start menu but no joy. I am thinking nothing short of a complete OS reinstall will solve this. But that is a pretty unpalatable thought. So much stuff, so many patches etc for games. I have everything critical backed up and an OS image but I think the image will contain this flaw, at the time I was booting every day and as such unaware of the issue.

 

[Scottyboy99]

Well I think I am close to sorting this out. I have tried so many things and its slow going as anything I do I then have to wait over 24 hours to test. Anyway I honestly thought I tried a clean boot by disabling all non ms services before. Turns out amid all my checks I overlooked this as I tried it again and to my pleasant surprise no delay 24 hours later. I am now slowly re enabling services to find the offending item a few at a time. So it may take me a few days to narrow it down. Rest assured I will immediately post back on here what the service causing the issue is. So hopefully no other poor souls spend weeks clutching at straws like me, should this happen to them.

Cheers
Wayne

 

[Scottyboy99]

The program causing this oddity is Soluto. Specifically a service called Soluto PC genome. I set this service to automatic - delayed and as a result this issue appears to have gone away