Re: Error in debug mode?

Well, I was able to fix the bind errors...that seemed to be merely a
configuration fault ;)

However, I now get "Negotiation Failed" or "Negotiation Timed Out"
errors....Here's a new snippet of the log from debug:

[Jul 06 07:38:04 2004] IRC READ -> :blackhawk.irc.neoturbine.net NOTICE
ProxyMon :*** Client -- Client connecting: SteveB|laptop
([email protected]) [63.81.122.87] {users}
[Jul 06 07:38:04 2004] IRC REGEX -> Regular expression caught connection
notice. Parsing.
[Jul 06 07:38:04 2004] IRC REGEX -> Parsed
SteveB|[email protected] [63.81.122.87] from connection notice.
[Jul 06 07:38:04 2004] DNSBL -> Passed '87.122.81.63.opm.blitzed.org' to
resolver
[Jul 06 07:38:04 2004] SCAN -> Passing SteveB|[email protected] to
scanner [default]
[Jul 06 07:38:04 2004] DNSBL -> Lookup result for
SteveB|[email protected] (87.122.81.63.opm.blitzed.org) 0.0.0.0
(error: 3)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:8080 (HTTP)
[default] (0 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:3128 (HTTP)
[default] (0 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:6588 (HTTP)
[default] (0 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:1080 (SOCKS4)
[default] (0 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:1080 (SOCKS5)
[default] (0 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:80 (HTTP)
[default] (642 bytes read)
[Jul 06 07:38:04 2004] SCAN -> Negotiation failed 63.81.122.87:80 (HTTPPOST)
[default] (642 bytes read)
[Jul 06 07:38:34 2004] SCAN -> Negotiation timed out 63.81.122.87:23
(ROUTER) [default] (0 bytes read)
[Jul 06 07:38:34 2004] SCAN -> Negotiation timed out 63.81.122.87:23
(WINGATE) [default] (0 bytes read)
[Jul 06 07:38:34 2004] SCAN -> Scan 63.81.122.87 [default] completed
[Jul 06 07:38:34 2004] SCAN -> All tests on
SteveB|[email protected] complete.

The Proxy Monitor has granted me access to my network even though it's
obvious i was connecting behind an HTTP Proxy.  It's also pretty obvious
that it failed to probe me while connecting.  What's going on?  Is it
possible that my router is causing these problems?

Thanks,
Steve Bularca