Since last post: 4298 days Last activity: 4298 days
#1 Posted on 20.3.04 1828.36 Reposted on: 20.3.11 1829.01
Whenever I close Internet Explorer, it doesn't really close. In the Task Manager, an "iexplore.exe" process is still running. So everytime I open/close Internet Explorer, another process lingers there.
Any idea what's going on? I checked for Spyware and Viruses already and it's still happening. I'm running Windows XP, BTW.
I've tried searching on Google for help but no dice. :(
#4 Posted on 21.3.04 0037.07 Reposted on: 21.3.11 0040.14
Everybody wants to have these "interesting" system problems when I'm away from my big, current machines! Jeez.
1) Let me clarify: So, if you open/close IE 5 times, you're left with 5 lingering iexplore.exe processes. Is that right? (I can see where one or even 2 would make sense, but more than that, I agree is odd.) Do they happen to time out & go away in ... say... 20 minutes?
2) Is it just opening/closing an IE window that causes a lingering process? Or do you have to ask it to actually bring up a web page for it to dangle?
3)When you have some of those lingering processes, get thee to a DOS prompt & do a "netstat -a". (This is a "read only" command -- will not hurt or change anything.) What's that say? Your IE processes may have some outstanding open pipes (for any variety of reasons) that are waiting to time out. If everything looks "reasonable" it may not have anything to do with your side. If, on the other hand, you see site names in there that you didn't expect, that'd be "interesting" (read: possibly problematic).
#6 Posted on 21.3.04 1401.18 Reposted on: 21.3.11 1403.15
TCP connections CLOSE_WAIT aren't necessarily, particularly a problem. Right now on my machine, I'm seeing some outstanding connections to crz.net & one to status-m.icq.com -- neither of those makes me particularly suspicious. I would be concerned if they were connections to unknown or untrusted sites, that you didn't have an understanding of.
If all of that looks cool, I'd be more inclined to think that it's just an IE weirdness. (Rather than something truly nasty.) Maybe somebody else with IE on an XP machine in front of them can report what they see.
ALL ORIGINAL POSTS IN THIS THREAD ARE NOW AVAILABLE