Removed Coupons.com Adware Internet Now Broken

[Guardian195]

Title is fairly descriptive, don't ask how but coupons.com coupon software was on my computer and I let Spybot S&D remove it.. BAD IDEA! My internet connectivity thing has been showing "Limited or no connectivity" and repair fails at renewing IP address.
I've tried reverting the removal in spybot, system restore, winsockfix, and a few other things which have recently left it saying "Network cable unplugged" when it obviously isn't.

 

[stduc]

Coupons.com is supposedly safe enough - but I wouldn't trust them! That said, seems like it hijacked your network connection somehow. If Spybot is used to remove software that relies on ads, such as coupons.com then it may have unfortunate side effects. 1stly I would remove the coupon printer software from your machine if you can.

Everything you have done should normally have fixed it. However, you could then try re-installing your network card drivers. Or see this link I posted - it might work for you too?

OpenSuse fixed NIC - astonishment!!!!!!!!


Failing that you could try a registry repair tool such as CCleaner. Or go back to an earlier restore point.

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]

 

[Guardian195]

Somehow it's fixed, hopefully for good. Last night right before bed I tried to do everything all at once instead of after different reboots, reinstall NIC drivers, ran winsockfix, turn computer+router+modem off and then turn on router first, then modem, then computer, last night it didn't work so I posted this.. This morning when I turned my computer on to do more troubleshooting, it worked! Hopefully it stays this way, cheers for the help.

 

[stduc]

You're welcome. I guess NIC needed a re-set - which, I imagine OpenSuse did for me and a power off did for you!
I would still look for that Coupon Printer & remove it if I were you - unless you find it useful of course?

Funny thing is I had tried a power cycle before I thought of OpenSuse. But heyho we both got the problem solved.

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]

 

[cmeagan656]

...then turn on router first, then modem, then computer

I always power down from the inside out - computer, router, modem - and then power up in the reverse order - modem, router, computer.

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
Canadian members check out Tek-Tips in Canada for socializing, networking, and anything non-technical.

 

[stduc]

Generally speaking the order is irrelevant. At least in my experience. No doubt someone will put me straight.

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]

 

[MasterRacker]

Order is important. The modem needs to come up first to get connected to your ISP and configure itself appropriately. The router then can get an external IP, configure itself for routing and start it's DHCP server to give internal IP addresses to your PCs and other devices. Power down order will be irrelevant if you power down everything. Power up order is very important.

Normally on the PC you could get by with a ipconfig release/renew after the other devices have been power cycled, but as mentioned, sometimes the hardware itself needs to be reset.

When you're troubleshooting something funky, make no assumptions, shut it all down, restart methodically.

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[stduc]

To be accurate - it depends on the exact equipment you have. It certainly doesn't hurt to do it the way mentioned above. You also have to be methodical. That said - if you have, shall we say a "proper" modem/router then it really shouldn't matter as the PC if booted first should wait for the router. When the router is powered up it should go from "cable unplugged" to "acquiring network address" and then connect. If you have one of those cheap giveaways from your ISP then it probably does matter. The thing I find hardest to remember is that these days shutting down is not the same as turning off. To achieve a truly cold boot you must remove the power for a few seconds.

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]

 

[burtsbees]

Order INDEED is important, and it really should be the same standard process across the board no matter what---standardization is absolutely KEY in the IT world. I mean, what if there is a switch involved that does STP (like a Cisco switch), and the vlan access ports do not have spantree portfast configured---the dhcp process times out well before the 50 seconds it takes for STP to go from blocking to forwarding, and you'll get an APIPA. Standardization, my friend---adopt one process that will do the deed no matter WHAT your topology is! It is about as important as synching your time across the board, mainly for logging purposes. Tell me you do that, PLEASE!lol

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[stduc]

Time synch - what's that? - LOL

So you would call 50 users, say, and tell them they have to reboot? Well that should fly like a lead ballon.

I thought we were talking domestic here. Workwise - if you are in control then configure things so it is order independant if possible.

Please don't get the wrong idea here - I am not arguing with you, really I am not. As for standards - what a lovely dream! ROFL

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]