On 26 Jan 2006 at 20:09, Jim Dykes wrote: > When I opened the message, I found that Bernie Cosell had written: > > > No, but for me, I found it was possible to get PopFile hung up (in my > > case, a flaky dialup line would nail it if I lost my connection at a > > touchy place in the POP3 exchange). Easily fixed: ctrl-alt-del and kill > > the process from the task manager and restart it. > > Problem is I can't acces the PopFile interface to see what's there > and if the messages are being classified correctly.
When it isn't answering its UI, it isn't running. Just kill it and restart it. > I get "connection refused". Well, the connection is my own > computer. So it must be an "inside job" <smile>. Correct -- it is running a mini-web-server listening on a local socket and if it gets hung/confused, it stops listening and at that point your browser can't connect. > Any ideas about why I can't even access "local host"? You can -- what you're not understanding is that with TPC you don't access a 'host' but always a "host/port" pair. In order to be able to connect, the particular host must have a server listening on the specific port you're trying to connect to. In my case, for example, I moved popfile to port 9000, so I connect to "localhost:9000". You probably connect to "localhost:8080". In either case, the error message isn't telling you that the *HOST* has a problem, but only that you can't connect the particular _port_ you're trying to connect to. /Bernie\ -- Bernie Cosell Fantasy Farm Fibers mailto:[EMAIL PROTECTED] Pearisburg, VA --> Too many people, too few sheep <-- -- ---------------------------------------- To unsubscribe, mailto: [EMAIL PROTECTED] Is your picture included in the Official Win-Home List Members Profiles Page? http://www.besteffort.com/winhome/Profiles.html If not, write to: [EMAIL PROTECTED]
