Re: [hylafax-users] Hylafax Client - Server problem

["support" <support@xxxxxxxxxxxx>]

Hi,

What do you mean by ftp connection tracking? Do you mean that my router
should allow port 4559 to have the same capability as FTP port 21? Is there
any router model that could provide this capability? If yes, can you suggest
an example, as I am really frustrated...

From you reply message, it seems that my problem is due to the router but
not hylafax software, doesn't it? This problem isn't related to NAT, isn't
it?

Thank you.

Thomas


----- Original Message ----- 
From: "Kimble Young" <kimble@xxxxxxxxxxxxxxx>
To: "support" <support@xxxxxxxxxxxx>
Cc: "Matthias Reich" <rei@xxxxxxxx>; <hylafax-users@xxxxxxxxxxx>
Sent: Saturday, November 20, 2004 2:19 AM
Subject: Re: [hylafax-users] Hylafax Client - Server problem


> Thomas
>
> The problem is that your router is not doing the ftp connection tracking
>   on port 4559. In linux it is easy as making sure that ip_conntrack_ftp
> is running with 4559 specified as one of the ports.
>
> eg
>
> insmod ip_conntrack_ftp ports=21,4559
>
>
> What was happening to me was the client was connecting but not able to
> transfer the postscript file and was hanging at this point.
>
> support wrote:
> > Hi,
> >
> > I have port 4559 forwarded on NAT. My host.faxd is correct. Will it be
my
> > NAT problem or hylafax does not support NAT address translation?
> >
> > Thomas
> >
> > ----- Original Message ----- 
> > From: "Matthias Reich" <rei@xxxxxxxx>
> > To: "support" <support@xxxxxxxxxxxx>
> > Cc: <hylafax-users@xxxxxxxxxxx>
> > Sent: Friday, November 19, 2004 2:21 PM
> > Subject: Re: [hylafax-users] Hylafax Client - Server problem
> >
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Am Freitag, 19. November 2004 04:26 schrieb support:
> >
> >>Hi everyone,
> >>
> >>
> >>I have set up a fax server using hylafax version 4.20 on fedora core 2
> >>recently. It works fine.
> >>
> >>If I put the fax server behind an NAT, (i.e. fax server has an internal
IP
> >>192.168.1.xx), some problem occurs when I try to use print-to-fax fax
> >>client to sent a fax from windows to fax server. For example, if I use
> >
> > WHFC
> >
> >>to send a fax from windows to hylafax using default port 4559, where
> >>hylafax server is behind NAT, the data connection seems hanging up. The
> >>document could not be sent to fax server.
> >>
> >>
> >>However, if I remove the NAT and set the hylafax server IP to a public
IP
> >>220.246.21.xx, the document can be sent successfully from windows
through
> >>port 4559.
> >>
> >>
> >>Is there a solution solving this kind of problem? Thank you.
> >>
> >>
> >>
> >>Thomas Tam
> >>
> >>------------------------------------
> >>support@xxxxxxxxxxxx
> >
> >
> > Hi Thkmas,
> >
> > did you check your rules of the NAT is port 4559 forwarded ?
> > check your hosts.hfaxd file if you are permitted to connect
> > (see man hosts.hfaxd)
> >
> >
> > HIH
> > - -m
> >
> > - -- 
> > HAGOS eG                 phone: +49 711 7880592
> > Matthias Reich             fax: +49 711 7880535
> > Industriestr. 62           web: http://www.hagos.de
> > D-70565 Stuttgart         mail: rei@xxxxxxxx
> > Germany
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (GNU/Linux)
> >
> > iD8DBQFBnZDkcjMVLPQ5oUkRAsAjAJ0ckrCA2e0Wwjh2XbpzzbGNk5HtIgCfahb6
> > hV8i8bQsvUrqGQPY/Yg2+9c=
> > =uNAY
> > -----END PGP SIGNATURE-----
> >
> >
> >
> > ____________________ HylaFAX(tm) Users Mailing List
_______________________
> >   To subscribe/unsubscribe, click
http://lists.hylafax.org/cgi-bin/lsg2.cgi
> >  On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx <
/dev/null
> >   *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
> >
> >
> >
>
>


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*