Author Topic: maybe antivirus a good thing to run w/ AH? (Read 931 times)

Skuzzy · « **Reply #15 on:** January 28, 2007, 11:42:34 AM »

Which means your computer opened up port 80 on the remote IP address you listed and it was attempting to connect back to port 5xxx on your computer. Typical browser type connection.

Wes14 · « **Reply #16 on:** January 28, 2007, 12:32:39 PM »

so that means my pc acually "told" the ther one to attempt to send a virus:confused:

Brenjen · « **Reply #17 on:** January 28, 2007, 01:14:34 PM »

I ran the Symantec security scanner & passed all but the ones that required active X control. It couldn't test those with my current configuration in Explorer or Firefox

I tried the "netstat -an" that Skuzzy said to do to look for listening ports but the command prompt will only pop-up for a millisecond, it doesn't stay up long enough for me to look at what it says. I'm sure it's because of some setting somewhere.

I like informative posts like that because I am an average user & I don't know anything about internet protocol or networking or ports or any of that crap. I just know my AV & AS progs work, I don't use the Windows firewall & I have never had a problem. I'm sure if some "script kiddy" (lol) wanted to do me in I'd be easy prey.

It's funny because my first P/C was a Tandy TRS-80 & I wrote 30 pages of code one time to make a u.f.o. descend from the top of the screen to the bottom with a little rumble sound; it lasted all of two seconds & took me two hours to type in the code. Here I am with modern P/C's & I feel like an idiot because of all the tech that passed me by in the late 80's & early 90's when I had a life.

MrRiplEy[H] · « **Reply #18 on:** January 28, 2007, 01:44:51 PM »

Quote

Originally posted by Brenjen
I ran the Symantec security scanner & passed all but the ones that required active X control. It couldn't test those with my current configuration in Explorer or Firefox

I tried the "netstat -an" that Skuzzy said to do to look for listening ports but the command prompt will only pop-up for a millisecond, it doesn't stay up long enough for me to look at what it says. I'm sure it's because of some setting somewhere.

I like informative posts like that because I am an average user & I don't know anything about internet protocol or networking or ports or any of that crap. I just know my AV & AS progs work, I don't use the Windows firewall & I have never had a problem. I'm sure if some "script kiddy" (lol) wanted to do me in I'd be easy prey. It's funny because my first P/C was a Tandy TRS-80 & I wrote 30 pages of code one time to make a u.f.o. descend from the top of the screen to the bottom with a little rumble sound; it lasted all of two seconds & took me two hours to type in the code. Here I am with modern P/C's & I feel like an idiot because of all the tech that passed me by in the late 80's & early 90's when I had a life.

First type 'cmd' without quotes and enter. THEN type 'netstat -an' and it won't close on it's own.

Skuzzy: The problem with your logic is that the average Joe will surely not have a dedicated firewall. If there needs to be a choice between no firewall and a personal firewall, which would you recommend?

JCLerch · « **Reply #19 on:** January 28, 2007, 01:45:28 PM »

Start / Run / "cmd" enter

netstat -anb (the b option lists the executable responsible for the connection)

Skuzzy · « **Reply #20 on:** January 28, 2007, 05:26:45 PM »

Quote

Originally posted by MrRiplEy[H]
First type 'cmd' without quotes and enter. THEN type 'netstat -an' and it won't close on it's own.

Skuzzy: The problem with your logic is that the average Joe will surely not have a dedicated firewall. If there needs to be a choice between no firewall and a personal firewall, which would you recommend?

I would not make a recommendation.

And the reason being is I would have to preface it with, "if you are going to install a personal firewall, please learn how to use it, for the lub of all that is good, please learn how to configure it properly and understand how it works."

Brenjen · « **Reply #21 on:** January 28, 2007, 06:28:45 PM »

Ah, thanks. I got the ports to show up typing in CMD first (DOH!)

Wes14 · « **Reply #22 on:** January 28, 2007, 07:24:08 PM »

checked the ports in the cmd prompt
all of them have legit reasons to be runnign and port 5117 isnt on the list

Quote

so if it can work for a idiot like me

Almost bet $5 that u know about pc's then me
Roscoroo

Edit:found out that norton has blocked the site/server that the pc was on from that Port

Vulcan · « **Reply #23 on:** January 28, 2007, 09:25:57 PM »

Quote

Originally posted by MrRiplEy[H]
This is where I do not agree with Skuzzy at all. A personal firewall is the only means for a general user to maintain any control over the network activity of the computer.

I agree with Skuzzy. Personal Firewall software these days is pretty much snake oil.

First of all most if not all PF's are 'leaky' and it is possible for malware to drill through them. So all the PF holds back is legit programs.

Second of all most good AV software protects you from the common attacks PF's used to cover (ie buffer overflow exploits).

Google "personal firewall leak test" and you'll find some nasty reading.

Maybe if you have a direct net connection and are not behind a router/firewall with even basic NAT - then perhaps I'd consider using one.

Wes14 · « **Reply #24 on:** January 28, 2007, 10:00:08 PM »

"Google "personal firewall leak test" and you'll find some nasty reading.

Maybe if you have a direct net connection and are not behind a router/firewall with even basic NAT - then perhaps I'd consider using one."

im on cable modem broadband..the sucky thing is that my router thingy doesnt have a built in Firewall,and that Personal Firewall leak test went right thru my firewall (UDP wise) so i fixed that up a lil bit

ill amost say that my AV and FW r amost rock solid TCP wise not sure on UDP ports yet

thanks for pointing out the Firewall leak test Vulcan:aok

Vulcan · « **Reply #25 on:** January 28, 2007, 10:21:46 PM »

Quote

Originally posted by Wes14
"Google "personal firewall leak test" and you'll find some nasty reading.

Maybe if you have a direct net connection and are not behind a router/firewall with even basic NAT - then perhaps I'd consider using one."

im on cable modem broadband..the sucky thing is that my router thingy doesnt have a built in Firewall,and that Personal Firewall leak test went right thru my firewall (UDP wise) so i fixed that up a lil bit

ill amost say that my AV and FW r amost rock solid TCP wise not sure on UDP ports yet

thanks for pointing out the Firewall leak test Vulcan:aok

A cheap cable firewall/router will cost you less than $50 with Stateful Packet Inspection.

Meatwad · « **Reply #26 on:** January 28, 2007, 10:32:50 PM »

I never had to disable anything to play AH. My guess is that there is a setting not set correctly if it prevents you to play AH.

Wes14 · « **Reply #27 on:** January 28, 2007, 10:44:26 PM »

the way it currently set up normally locks the internet browsers from using the internet more then AH

now if a rare occasion where AV/Firewall mistakes something on AH as a virus (about once a month) then im SOL for 24 hours to a few days from AH cause it will lock the ports that AH is needed to run on:furious

OOZ662 · « **Reply #28 on:** January 28, 2007, 10:47:15 PM »

Wes14 · « **Reply #29 on:** January 28, 2007, 11:12:51 PM »

Quote

Originally posted by OOZ662
Eh.

O.o that is some fancy lil piece of equipment:noid