> I wonder, if the next time this happens, if you viewed the > services file, (c:\winnt\system32\drivers\etc\services) if > it would tell you what is hooked on that port. if it does, > then you know what app is the culprit.
The services file doesn't reflect what's actually listening; it just lists standard ports used by services. There are apps which can determine what's listening at a specific port, and netstat in XP does this, which is kind of neat. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
