On Jul 24, 2007, at 6:06 PM, DHSinclair wrote:
Christopher,
Thank you. I do have and have been using TCPView. Yes, you have
correctly got it!
Now.............
I have run TCPView on my server. I see nobody camped out on
"127.0.0.1."
I do see many internal windows components camped out on
"0.0.0.0:xxxx". So I suppose my next question is:
Does 127.0.0.1 equal 0.0.0.0 ?
I will go check the 2d link you gave. Have already been to the 1st
link..... :)
I so apologize for being this dense. I did use to think I had a
grasp of this.
Perhaps not. The new server is forcing new schooling.
Thanks again.
Best,
Duncan
Ok, so 127.0.0.1 is JUST your local computer, accesible only to you--
nobody else can get to that.
0.0.0.0 typically means ANY local address for your computer. So your
computer at the same time has multiple addresses:
1) localhost -- 127.0.0.1
2) network -- 192.168.1.20 (or whatever your other IP address is)
so if a program is listening on 0.0.0.0:25 (port 25), that would mean
it would be listening on 127.0.0.1:25 and 192.168.1.20:25
Looking at the homer program, it tries to listen on port 80--that is
the "www" / HTTP port. The port that you talk to other computers at
when you request webpages.
My guess would be that you're already running something that listens
on port 80, ie, a web server. This would be a program that you
installed or are running. Maybe Apache... Microsoft IIS. Are you
running a webserver?
Scott
