Re: [hylafax-users] Hylafax server <--> client interactions with Windows clients

[Tadeusz Andrzej Kadłubowski <tkadlubo@xxxxxxxxxxxxxxxxx>]

Thus wrote Darren Nickerson:
> Depending upon the client software you're using and how they implement the 
> HylaFAX client/server protocol, you may be running into a firewall issue 
> here. In particular, if it's running in passive mode, it's exactly like 
> passive FTP - the control connection runs just fine on port 4559, but as 
> soon as the data connection tries to transfer a file, the dynamic and 
> random port that was negotiated for that transfer (not port 4559) is 
> blocked by your firewall, or not recognized as belonging to an established 
> connection by your NAT device.
> 
> Is there a firewall running on the linux server, or is there a NAT 
> appliance of firewall anywhere between you and your HylaFAX server? I think 
> SuSE 10 will by default use a firewall unless you turn it off in Yast2. Try 
> removing it and see what happens.

Ok. My guess just came to my mind: /tmp filesystem full hence temporary job
file is 0 bytes? Check just in case.

Good luck,
-- 
tadeusz

____________________ 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*