Jim,
Perhaps I am guilty of seeking an instant fix.
I am sorry.  I have dumped "homer" based on previous
comments.
Homer can not connect and play with what is already in play.
I can deal with that. Tough as that may be.
The message you got is prezactly what I got too.
Put me off.  But I have moved beyond this.  NO homer.
4Now.
NO, homer was never running in taskmanager.  It just quit
on the server.  Not a huge problem. I think I have some
understanding now.............. :)
Basically I have given up...............
Best,
Duncan
 20:10 07/25/2007 -0400, you wrote:

Duncan,

Did you fire up Taskmanager and check if 'homer' is already running?

I had homer running and tried to start another instance of homer. I got the
"Something is already listening to 127.0.0.1 ..." message from the 2nd
instance, but the 2nd instance didn't know homer (1st instance) was the
listening proggy.

On my machine (WIN2K) with no browsers running and homer running, netstat -a
returns:

C:\Documents and Settings\jr>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    jr0:epmap              jr0:0                  LISTENING
  TCP    jr0:microsoft-ds       jr0:0                  LISTENING
  TCP    jr0:1025               jr0:0                  LISTENING
  TCP    jr0:http               jr0:0                  LISTENING
  TCP    jr0:netbios-ssn        jr0:0                  LISTENING
  UDP    jr0:microsoft-ds       *:*
  UDP    jr0:1032               *:*
  UDP    jr0:3015               *:*
  UDP    jr0:netbios-ns         *:*
  UDP    jr0:netbios-dgm        *:*
  UDP    jr0:isakmp             *:*
  UDP    jr0:4500               *:*

and without homer running and ...

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    jr0:epmap              jr0:0                  LISTENING
  TCP    jr0:microsoft-ds       jr0:0                  LISTENING
  TCP    jr0:1025               jr0:0                  LISTENING
  TCP    jr0:netbios-ssn        jr0:0                  LISTENING
  UDP    jr0:microsoft-ds       *:*
  UDP    jr0:1032               *:*
  UDP    jr0:3015               *:*
  UDP    jr0:netbios-ns         *:*
  UDP    jr0:netbios-dgm        *:*
  UDP    jr0:isakmp             *:*
  UDP    jr0:4500               *:*

... so, at least on this machine, homer is the only app LISTENING on
jr0:http.

Periodically, netstat -a might show transient things like the following:

 TCP    jr0:3100               mail.tstonramp.com:pop3  TIME_WAIT

hth,

_jim


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of DHSinclair
Sent: Monday, July 23, 2007 1:15 PM
To: Hardware Group
Subject: [H] IP stuff?


Is there any way for me to query a given machine to find out
"who" is camped out "listening to" 127.0.0.1?

I am playing with "homer."  (http://www.funkytoad.com/content/view/14/32/)
It will not start because somebody else beats homer to 127.0.0.1 for
"listening."

Yes, this is another progy advised from "mvps.org" that gives out the
"hosts" files.  I am playing ATM.
Thanks,
Duncan


This email scanned for Viruses and Spam by ZCloud.net



__________ NOD32 2420 (20070725) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


This email scanned for Viruses and Spam by ZCloud.net

Reply via email to