Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> From: cvsnt-bounces at cvsnt.org
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Mike Jacobs
> Sent: Thursday, 02 February, 2006 08:33
>
> >We can disregard the AV program, if it's actually an AV program and
not
> >some sort of hybrid that includes firewalling features as well.
>
> It's a suite of functions from my ISP but appears to supplied by
F-Secure
> (one of the anti-virus makers). It does include traffic
monitoring/blocking,
> web filtering, and a firewall. I cannot tell if it is a hybrid or
not.
That's what I meant - does it include IDS ("traffic
monitoring/blocking") or firewall features. It does, so it could be the
problem. (Note that with some of these products it can be difficult to
actually disable them.)
> >Normally, I'd ask whether you've checked that the servers are running
> >and have you check netstat ...
> The results of netstat include a local and foreign address. The local
> address includes a port, while the foreign has a port of 0 (most of
> the listening sockets appear that way). Is this significant?
That's normal. A listening socket is not bound to any remote address,
so the Windows netstat program shows it with a remote port of 0.
> For example (many others removed):
> Proto Local Address Foreign Address State
> TCP homeoffice:2401 homeoffice:0 LISTENING
It's mildly odd that netstat is showing the host portions of those
addresses as "homeoffice" - apparently you have an entry in your hosts
file that maps the name "homeoffice" to the address 0.0.0.0. But that
shouldn't hurt anything. (By the way, this is one reason why it's good
to use the -n flag when using netstat for debugging; the translation of
numerical addresses and ports into symbolic names can be deceptive.)
Something else to try: open a command window and type "telnet localhost
2401". You should get a blank screen, indicating that you've connected
to the CVSNT server. Hit enter and you should get an error message from
the server, followed by the connection closing. If telnet fails to
connect or the conversation closes before you hit enter, that confirms
that there's a problem communicating with the server.
--
Michael Wojcik
Principal Software Systems Developer, Micro Focus