Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Port 135 & ICMP Ping open on Mcafee Firewall 6

  • Please log in to reply




  • Member
  • PipPip
  • 20 posts
I'm using XP Home, Service Pack 2, no multiple users, IE browser version: 6.0.2900.2180.xpsp_sp2_rtm.040803-2158

I have McAfee Personal Firewall Plus, version 6.0.6014.

Even though I have the program configured to NOT accept ICMP ping requests and to block port 135, when I go to Symantec's online Security Check, or to the online ShieldsUp check, the results occasionally show that my ICMP Ping port and port 135 are open. The only way to fix it at that point is to reboot. After rebooting, the online checks show both ports are blocked. However, the fix doesn't last long, because at any random point later in the day, the ports open again.

McAfee Chat support told me to run their Setup Assistant and reboot, which I did. The ports were then successfully blocked....until they suddenly became unblocked again later for no apparent reason!

Is there a fix for this?

I use WinXP Home SP2 with all the latest security updates. I also have McAfee SecurityCenter and McAfee VirusScan 9.0.10

Many thanks!
  • 0


Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP