Menu

WPHF Reload: "read time out"

Daniele T
2012-10-22
2019-12-12
  • Daniele T

    Daniele T - 2012-10-22

    Hi all,
            when i send a fax via WPHF reload after 5 sec i received an error popup with this message:
    "read time out", why?

    Scenario:
    all two clients on network: windows xp sp 3
    winprint hylafax reload version: 0.3.10

    ServerFax: ubuntu desktop 12.04 TLS
    Fax:  AVANTFAX 3.3.3
    Hylavafax: 6.0.5

    thanks in advance,

    Daniele aka DuNdIdU

     
  • Lorenzo Monti

    Lorenzo Monti - 2013-02-16

    I'd suggest that you upgrade to the latest version (currently 0.4.3).
    Many bugs have been fixed since 0.3.10, which is quite old.
    That said, there may be many reasons for a "read timeout" error, ranging from client misconfiguration to network problems along the way to the server to firewalls or so.
    Let's start from the beginning. Is the client correctly configured? Did you specify an IP or a FQDN? Are DNS ok? Can you ping the server? Can you telnet the server on port 4559 (or whatever port you told hylafax to listen on)? Maybe Wireshark can be helpful.

     
  • Michael Herberger

    Hi,

    I have the same problem on just one PC, "read time out". I simple think it is an issue with only that PC. I have added the executable wphfgui.exe to the firewall allowed apps. Frankly I do not know the port or app to allow communication for the fax and suspect it is open on my because of another app. So looking for help on correcting the issue on the Windows 10 PC. Take note of the [RST, ACK] info on the failed Wireshark packet info and the time it takes to [PSH, ACK] on that PC.

    The network consists of 2 windows 10 PC's, a Ubuntu 18.04 LTS Ubuntu Hylafax server, and WIFI mesh router. I am the faxmaster, super user and administrator of the system. I am connected to server by openssh using WinSCP and Putty.

    My PC and laptop(Windows 10) can send faxes but the other PC gets the error message "read time out".

    -Have used my laptop with windows 10 and can send faxes, with all user names and passwords. I can also send faxes from the same location of PC with the fax issue.
    -I can telnet port 4559 from all PC's including the PC unable to send faxes. I am able to run USER and STAT command on the server via telnet for all users. With the PC that has fax issues, OPEN of the IP takes awhile to initialize from the server. Wireshark shows over 15 sec. delay.
    -Servicetrace logs all activity in the Syslog file. I do not see any issues, except the PC unable to fax
    -Telnet for all PC's logs the same and Hylafax logs all INET packets but for the one problem PC it only logs the INET.

    Syslog examples;
    1. Attempt from faxless PC;
    HylaFAX[29462]: HylaFAX INET connection from Eva-Maria.fritz.box [192.168.178.30]..
    ...

    1. From my laptop using telnet, typical of all PC's;
      HylaFAX[28262]: <--- 220 ubuntu12rmh server (HylaFAX (tm) Version 6.0.6) ready.
      HylaFAX[28262]: HylaFAX INET connection from bighead2.fritz.box [192.168.178.21]
      HylaFAX[28262]: command: user michael
      HylaFAX[28262]: USER michael
      HylaFAX[28262]: <--- 230 User michael logged in.
      HylaFAX[28262]: command: stat..
      ..

    2. Atttempt from PC unable to send a fax;
      HylaFAX[27666]: <--- 220 ubuntu12rmh server (HylaFAX (tm) Version 6.0.6) ready.
      HylaFAX[27666]: HylaFAX INET connection from Eva-Maria.fritz.box [192.168.178.30]...
      ....

    Wireshark partials, kopied in cvs format and in following order, No. #, time, sending IP, destination IP, Protocal, length, information ;

    1. Failed fax attempt by faxless PC;
      "319","3.171155","192.168.178.30","192.168.178.20","TCP","66","55813 → 4559 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1"
      "320","3.176748","192.168.178.20","192.168.178.30","TCP","66","4559 → 55813 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 SACK_PERM=1 WS=128"
      "321","3.177054","192.168.178.30","192.168.178.20","TCP","54","55813 → 4559 [ACK] Seq=1 Ack=1 Win=131328 Len=0"

    "344","13.379773","192.168.178.20","192.168.178.30","TCP","60","4559 → 55813 [ACK] Seq=1 Ack=2 Win=64256 Len=0"

    "366","18.200367","192.168.178.20","192.168.178.30","TCP","114","4559 → 55813 [PSH, ACK] Seq=1 Ack=2 Win=64256 Len=60"
    "367","18.200878","192.168.178.30","192.168.178.20","TCP","54","55813 → 4559 [RST, ACK] Seq=2 Ack=61 Win=0 Len=0"
    "368","18.201426","192.168.178.20","192.168.178.30","TCP","60","4559 → 55813 [FIN, ACK] Seq=61 Ack=2 Win=64256 Len=0"

    1. Successful attempts from my PC's;
      fax session
      "266","8.707952","192.168.178.24","192.168.178.20","TCP","66","59691 → 4559 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1"
      "267","8.711226","192.168.178.20","192.168.178.24","TCP","66","4559 → 59691 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 SACK_PERM=1 WS=128"
      "268","8.711477","192.168.178.24","192.168.178.20","TCP","54","59691 → 4559 [ACK] Seq=1 Ack=1 Win=131328 Len=0"
      "269","8.722059","192.168.178.20","192.168.178.24","TCP","114","4559 → 59691 [PSH, ACK] Seq=1 Ack=1 Win=64256 Len=60"

    telnet session
    "34","5.711027","192.168.178.30","192.168.178.20","TCP","66","50085 → 4559 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM=1"
    "35","5.715935","192.168.178.20","192.168.178.30","TCP","66","4559 → 50085 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 SACK_PERM=1 WS=128"
    "36","5.716158","192.168.178.30","192.168.178.20","TCP","54","50085 → 4559 [ACK] Seq=1 Ack=1 Win=131328 Len=0"
    "70","20.739986","192.168.178.20","192.168.178.30","TCP","114","4559 → 50085 [PSH, ACK] Seq=1 Ack=1 Win=64256 Len=60"
    "71","20.779675","192.168.178.30","192.168.178.20","TCP","54","50085 → 4559 [ACK] Seq=1 Ack=61 Win=131328 Len=0"
    "73","22.978504","152.199.19.161","192.168.178.30","TCP","60","443 → 49964 [ACK] Seq=1 Ack=1 Win=290 Len=0"

    If someone can help, I would appreciate it.

    Thanks
    Michael

     

Log in to post a comment.