0

It suggests I use a different one. My first question is, which different one do I specify? I'm afraid of screwing something up by just arbitrarily specifying '8889' or something.

My second question is: I'm a little unnerved by the fact I was using Fiddler successfully just last week but this week something new that I don't know about is now "listening" (quote/unquote) on port 8888, according to NETSTAT -A. How can I find out what this other thing that's now listening in on port 8888 is?

Thanks for any help.

1 Answer 1

2

The netstat command is your friend. Check the documentation for more information. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netstat.mspx?mfr=true

EDIT: It seems that you have edited your original post to include the netstat command. If it doesn't appear in the netstat command then you may have a rootkit that is using port 8888. But this is unlikely.

6
  • Thank you for replying to my question. 8888 does appear in NETSTAT -A as line item: TCP 127.0.0.1:8888 Admin-THINK:0 LISTENING
    – user33666
    Jan 22, 2011 at 8:02
  • Okay, it was an Intel Service Manager daemon using port 8888. I stopped that process, and now Fiddler loads fine. Thanks again.
    – user33666
    Jan 22, 2011 at 8:12
  • No problem. Just so you know, you will not mess anything up by using another port. But you will have to redirect anything attempting to connect to your service to the new port. Jan 22, 2011 at 8:16
  • Thanks. I'm just vaguely aware that there is a standard usage for ports, that some ranges are reserved for some things and others for others. And some are set aside for whatever. Are there a few that you know about that could safely be said are free to use for this purpose if I need to down the line?
    – user33666
    Jan 22, 2011 at 8:22
  • Anything above 1024 is free to use for any reason. Jan 22, 2011 at 8:32

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .