-
mmm.. a new clue... checking back the DNS of those connections that are waiting for time out (many connections on ports from 1428 to 1582 right now, remote port:80) I see that it is from:
antionline.com and from ADS.antionline.com
while surfing around the site the number of connections (waiting for timeout) from this address is increasing.. after a while the ports may turn to listening status. It takes alot of time for a connection to timeout... is this something?
another notice is that I don't have this problem when I surf around sites which have no ads... could this be some kind of cookie problem?
By the way, I have ad-aware version 5, it shows that I'm clean of spyware right now..
-
Quote:
Originally posted here by KoRR
The port scan on blackcode.com just finished.. all the ports where closed..
SCAN RESULTS:
Your system is secured. No open ports were found.
fport says that it supports Windows NT4, Windows 2000 and Windows XP
my OS is Windows ME.. so...
Just to be safe with blackcode's port scan, proceed to phase 2, to make sure you have no trojan horses running, even though you have an antivirus, some trojans are stealth.
-
Dude, I'll say again, try Fport from Foundstone. (see my earlier post for url). At least with it you'll know what app is opening the ports.
Ammo
-
Oups, sorry didn'T see your post bout winME... Might still want to try it.. might work..
Ammo
-
its pretty normal for ports to listen for a while when a connection is no longer established, but it sounds like this goes far beyond that, plus your not being able to resolve a name. you might want to try uninstalling then re-installinf tcp/ip.
how do you connect, some dial up isps software, like netzero and aol can really mess up network settings.
i installed aol 7 on a machine at home and i couldn't get dns to work worth a ****. i tried everything until i finnaly disabled dns client in services, its worked great ever since...go figure.
-
Your suggestion seems to be working Tedob1 !! I uninstalled the TCP/IP, rebooted (got some blue screen there, probably because ZoneAlarm or Norton AV couldn't find the protocol needed), then re-installed TCP/IP for my Dial-up Adapter.
Things seem to be working fine now.. it's under test and I haven't faced the same problem since this re-installation. Crazy things.. the settings in TCP/IP are the same as before.. is there some hidden stuff that I can't see? Bad thing is I can't tell since WHEN I've been having this problem so I could find what caused it, and I've never seen this problem in another PC before. I keep telling that 'imagination is more important than knowledge and experience for a good troubleshooter'.. But this was beyond my imagination :D
In case it happens again I'll post again in this thread, but hopefully I won't need to! Thanks alot for your help! ;)
-
ironically... just after I posted my previous msg ... I saw some images couldn't load (squares with a red X appeared instead).. which is a bad omen... refreshing the page resulted on the infamous message of internet explorer.. so.. I rebooted and came back to report :(
