A question for you @Home users.

[Russ]

Just got done cleaning up an infested system a guy brought in. After that, I installed Zone Alarm for him. When I rebooted, alert popped up letting me know that a couple of servers were loading.

So, I check system configuration and both command lines go to the @Home directory. One had "adserver" in the line, so it was pretty obvious what it's function was. Both of these had the "/nosystray" switch, so it was clear that the @Home setup wanted them hidden from the user.

So, my question is: Is there ANY reason @Home should be installing something that allows the outside world to connect to the users system?

BTW, I nuked them both.

Russ, NCNE

 

[GL]

I never install @Home software. You just don't need it. I've heard their latest software allows @Home Tech Support people to "take control" of certain aspects of your PC so they can fix it. That might be what you're finding. But truthfully, I think it's a security risk and I'd remove it. You only need a 13 year old with too much time on their hands to compromise the system

 

[GL]

Check out this website Residential Broadband Users' Association. These guys know what they're talking about when it comes to @Home and/or DSL. You can probably confirm what the problem is over there.

 

[RossGr]

After the @home guy left the system he installed on began locking up, it continued to run pooryly until I went in and removed the @home junk. Has been fine since.

 

[yobarman]

speaking of your ISP shafting it's users... I'm using Verizon DSl
and there's this program called "History Uploader" running in the background, since it's unlocked in my Zone Alarm settings.

Should I not let this program through my firewall anymore? I dunno what it does. Yelp!

 

[Farbio]

when @home came and set up our connection he simply fixed a few ip and dns settings, and that was it. we had to configure it to work on our network in the house, but they didn't put anything that was @home software on it, have no clue why they would need to.

 

[Russ]

<< but they didn't put anything that was @home software on it, have no clue why they would need to. >>



Exactly what I was thinking, which is why I nuked it. But, since I'm not really familiar with their system, I figured I'd get some confirmation from you guys.

This user just set it up with their install CD, so apparently that's where it came from. Whatever it's purpose, that kind of crap just seems damned invasive to me.

Russ, NCNE

 

[SpongeBob]

I've had @Home installed 3 times, and every time I tell them not to install any software, just enter the network settings. I don't want anything to do with that stuff.

 

[Tominator]

I'm running behind a firewall now, but I did use Zonealarm before I got one. I think they monitor their customers so as to prevent or curtail a business from getting a residential rate. It IS invasive though...

Btw, I DO NOT use ANY @home software!

 

[Siva]

The @home software is invasive crap. I never install it, it really causes a lot of problems, especially with my router.

 

[Hamburgerpimp]

The only thing worse than @home software is any prog written by AOL.

 

[Presence]

Never install the @home software as many people already said it is not needed.

 

[Michael]

Another person with @Home and none of their software. Just the network id stuff.

Michael

 

[Looney]

Hm, up here in Ontario, Canada, they don't install the software... infact, if you want the software you have to buy that seperately at a retail store. And they definitely don't install it for you.

 

[AAjax]

When @home came to install my modem the guy asked &quot;you look familiar, do I know you?&quot; I answered &quot;yup, you applied for a tech position with me, and I turned you down&quot; I imedieately had him step away from my pc and I installed it myself while he watched

 

[Talon]

@home uses Tioga e-support software (read-Trojan) so customer's can &quot;repair&quot; their @home setup or allow the isp's techs to log on and &quot;do repairs&quot;. It usually shows up at the firewall as tgcmd.exe and tgfix.exe, although there may be a couple of other files with it. Just nuke it.

http://www.support.com/news/pressroom/pr_excite.asp

 

[Russ]

Talon,

Yep, tgcmd.exe was one of them.

Russ, NCNE