Thank you very much.
At first?I was thinking cmmon it cant be the
ports, so it must?be the firewall.?I started out with this hideously
long log/email showing how the ports are open. then I thought that I should
include the option files as well just so I could show you.
While pasting that into my email I realized that on
both machines the ports were configured... um... incorrectly.
on both machines the option files had port 6789 as
me and 6543 as peer. But?one of those should have been
(Same problem as using straight through cable
# my UDP address. Note: if you set port 0 here, the
system will pick# one and tell it to you via the ip-up script. Same holds
126.96.36.199:6789# ...and the UDP address we connect to. Of course no
Anyway, I switched the ports on one of the machine
and it is now working beautifully. Again thank you for the tip !!!
----- Original Message -----
From: "Karl Kleinpaste" <<A
Sent: Wednesday, September 05, 2001 3:36
Subject: Re: "kxchg: recv: Connection refused"
size=2>> "Connection refused" is an indication that there is no CIPE
daemon> responding on the expected port.? Check your options
file's> specification of the port.? If you have the daemon running
at both> ends, but this error occurs, then you have specified the wrong
ports.> > Otherwise -- dim possibility -- you have a firewall in
your way.> > --> Message sent by the <A
size=2>cipe-l,AT,inka,DOT,de mailing list.>
Unsubscribe: mail <FONT face=Arial
cipe-l" in body> Other commands available with "help" in body to the same
address.> CIPE info and list archive: <<A