Results 1 to 10 of 10

Thread: Connection problem

  1. 08-20-2003, 04:16 PM #1
    Marcelloz
    Marcelloz is offline
    Origami Suits You Too Marcelloz's Avatar
    Join Date
    Jul 2003
    Location
    The Netherlands
    Posts
    51

    Connection problem

    First of all, sorry for the large post.
    I'm having problems connecting to the DF server. The error.log shows the following message:

    ========================[ Aug 20, 2003 8:03 PM ]========================
    ERROR: [000.000] {foldtrajlite2.c, line 2101} Wed Aug 20 20:03:37 2003
    Unable to check server status
    ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 8192
    ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 8192
    ERROR: [000.000] {ncbi_http_connector.c, line 244} [HTTP] Error writing body at offset 8192
    ERROR: [000.000] {ncbi_http_connector.c, line 101} [HTTP] Too many failed attempts, giving up
    ERROR: [000.000] {foldtrajlite2.c, line 4616} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

    This has been going on for the last 2 days. I'm having no trouble connecting to the internet from this machine and from other machines in my network. The firewall doesn't show any DROP statements from your IP-address.

    The machine is a Windows 2000 machine, P2-400 and has already a lot of wu's buffered. When I stop and start the service the following lines appear in my firewall:

    I cut some off because of the messag length. I don't really know what to do. Browsing the internet from this machine is not a problem. Anybody a suggestion??

    Thanx in advance!

    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:48, ip/port:10.0.0.3:3388 -> 38.112.100.76:80, flags: SYN , seq:1617599058 ack:0, win:16384, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:48, ip/port:38.112.100.76:80 -> 10.0.0.3:3388, flags: SYN ACK , seq:3176433406 ack:1617599059, win:64240, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3388 -> 38.112.100.76:80, flags: ACK , seq:1617599059 ack:3176433407, win:17520, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:44, ip/port:10.0.0.3:3388 -> 38.112.100.76:80, flags: ACK PSH , seq:1617599059 ack:3176433407, win:17520, tcplen:4
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3388, flags: ACK , seq:3176433407 ack:1617599063, win:64236, tcplen:0
    .. cut ...
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:45, ip/port:10.0.0.3:3390 -> 38.112.100.76:80, flags: ACK PSH , seq:1617845631 ack:3176664995, win:17520, tcplen:5
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3390, flags: ACK , seq:3176664995 ack:1617845636, win:64235, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:133, ip/port:10.0.0.3:3390 -> 38.112.100.76:80, flags: ACK PSH , seq:1617845636 ack:3176664995, win:17520, tcplen:93
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:185, ip/port:38.112.100.76:80 -> 10.0.0.3:3390, flags: ACK PSH , seq:3176664995 ack:1617845729, win:64142, tcplen:145
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3390, flags: FIN ACK , seq:3176665140 ack:1617845729, win:64142, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3390 -> 38.112.100.76:80, flags: ACK , seq:1617845729 ack:3176665141, win:17375, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3390 -> 38.112.100.76:80, flags: FIN ACK , seq:1617845729 ack:3176665141, win:17375, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3390, flags: ACK , seq:3176665141 ack:1617845730, win:64142, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:48, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: SYN , seq:1617911700 ack:0, win:16384, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:48, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: SYN ACK , seq:3176748261 ack:1617911701, win:64240, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK , seq:1617911701 ack:3176748262, win:17520, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:45, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK PSH , seq:1617911701 ack:3176748262, win:17520, tcplen:5
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:1500, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK PSH , seq:1617911706 ack:3176748262, win:17520, tcplen:1460
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: ACK , seq:3176748262 ack:1617913166, win:64240, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:185, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: ACK PSH , seq:3176748262 ack:1617913166, win:64240, tcplen:145
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: RST , seq:3176748407 ack:1617913166, win:0, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:1500, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK , seq:1617913166 ack:3176748262, win:17520, tcplen:1460
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: RST , seq:3176748262 ack:3176748262, win:0, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:1500, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK PSH , seq:1617914626 ack:3176748262, win:17520, tcplen:1460
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: RST , seq:3176748262 ack:3176748262, win:0, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:1500, ip/port:10.0.0.3:3391 -> 38.112.100.76:80, flags: ACK , seq:1617916086 ack:3176748262, win:17520, tcplen:1460
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3391, flags: RST , seq:3176748262 ack:3176748262, win:0, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:48, ip/port:10.0.0.3:3392 -> 38.112.100.76:80, flags: SYN , seq:1617974408 ack:0, win:16384, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet to Internal, proto:TCP, len:48, ip/port:38.112.100.76:80 -> 10.0.0.3:3392, flags: SYN ACK , seq:3176797623 ack:1617974409, win:64240, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3392 -> 38.112.100.76:80, flags: ACK , seq:1617974409 ack:3176797624, win:17520, tcplen:0
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:45, ip/port:10.0.0.3:3392 -> 38.112.100.76:80, flags: ACK PSH , seq:1617974409 ack:3176797624, win:17520, tcplen:5
    [20/Aug/2003 20:05:34] PERMIT "DF OUT" packet from Internal, proto:TCP, len:1500, ip/port:10.0.0.3:3392 -> 38.112.100.76:80, flags: ACK PSH , seq:1617974414 ack:3176797624, win:17520, tcplen:1460
    ... cut ...
    [20/Aug/2003 20:05:38] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3396, flags: FIN ACK , seq:3177575061 ack:1618883669, win:64132, tcplen:0
    [20/Aug/2003 20:05:38] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3396 -> 38.112.100.76:80, flags: ACK , seq:1618883669 ack:3177575062, win:17375, tcplen:0
    [20/Aug/2003 20:05:38] PERMIT "DF OUT" packet from Internal, proto:TCP, len:40, ip/port:10.0.0.3:3396 -> 38.112.100.76:80, flags: FIN ACK , seq:1618883669 ack:3177575062, win:17375, tcplen:0
    [20/Aug/2003 20:05:38] PERMIT "DF OUT" packet to Internal, proto:TCP, len:40, ip/port:38.112.100.76:80 -> 10.0.0.3:3396, flags: ACK , seq:3177575062 ack:1618883670, win:64132, tcplen:0
    Last edited by Marcelloz; 08-21-2003 at 01:37 PM.
    Reply With Quote Reply With Quote
  2. 08-21-2003, 06:11 AM #2
    Geta
    Geta is offline
    Junior Member
    Join Date
    Aug 2003
    Posts
    4
    I've got exactly the same problem. I'm running DF over a NAT router (Kerio) and it seems the client doesn't try to connect (no entry in the http log).
    Sometimes the error.log says your first errors and sometimes just: ERROR: [000.000] {foldtrajlite2.c, line 4616} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER

    Even connection over my proxy or a public proxy won't work. Uploading from another machine nor the router directly won't work either.
    Reply With Quote Reply With Quote
  3. 08-21-2003, 06:14 AM #3
    Marcelloz
    Marcelloz is offline
    Origami Suits You Too Marcelloz's Avatar
    Join Date
    Jul 2003
    Location
    The Netherlands
    Posts
    51
    I'm also using the Kerio Winroute Firewall software with NAT enabled. I also tried the things the previous poster mentioned with no luck...
    Reply With Quote Reply With Quote
  4. 08-21-2003, 07:35 AM #4
    Terminator
    Terminator is offline
    Team Ninja Terminator's Avatar
    Join Date
    Mar 2002
    Location
    UK
    Posts
    42
    Me too, can't connect from home (64K ISDN) just times out, loads of work backed up but can upload from work (2MB Leased Line)

    Is this smaller protien overloading the server, as happened once before ?

    Because if it continues much longer I'll have to swap the machines at home to another project because it will take too long to upload the work :sigh:
    Reply With Quote Reply With Quote
  5. 08-21-2003, 01:37 PM #5
    Marcelloz
    Marcelloz is offline
    Origami Suits You Too Marcelloz's Avatar
    Join Date
    Jul 2003
    Location
    The Netherlands
    Posts
    51
    I solved the problem

    The firewall also has a build-in proxy server. When using that proxy server the problem was gone! Very very strange but a workable solution.

    Reply With Quote Reply With Quote
  6. 08-21-2003, 01:54 PM #6
    Geta
    Geta is offline
    Junior Member
    Join Date
    Aug 2003
    Posts
    4
    It doesn't work with proxy or public proxy for me.
    Reply With Quote Reply With Quote
  7. 08-21-2003, 02:54 PM #7
    Brian the Fist
    Brian the Fist is offline
    Moderator Brian the Fist's Avatar
    Join Date
    Mar 2002
    Location
    Toronto, Canada
    Posts
    1,558
    It would help us if you mention what countries you are in when you are having network problems...
    Howard Feldman
    Reply With Quote Reply With Quote
  8. 08-21-2003, 04:51 PM #8
    Marcelloz
    Marcelloz is offline
    Origami Suits You Too Marcelloz's Avatar
    Join Date
    Jul 2003
    Location
    The Netherlands
    Posts
    51
    I'm from The Netherlands and using Wanadoo Cable Premium.
    GMT+1 timezone
    handle:9r9k????

    [in reply to bwkaz]
    thanx for the suggestion. why? -> with the handle available the technical people can search more easily for our packages in their log files. But i guess half my handle should be sufficient
    Last edited by Marcelloz; 08-23-2003 at 07:14 AM.
    Reply With Quote Reply With Quote
  9. 08-22-2003, 03:38 AM #9
    Geta
    Geta is offline
    Junior Member
    Join Date
    Aug 2003
    Posts
    4
    I'm from Germany using T-DSL.
    Last edited by Geta; 08-23-2003 at 04:42 AM.
    Reply With Quote Reply With Quote
  10. 08-22-2003, 06:17 PM #10
    bwkaz
    bwkaz is offline
    Senior Member
    Join Date
    Mar 2002
    Location
    MI, U.S.
    Posts
    697
    Umm... you people might want to edit your posts and remove your handles. As of yet, I don't know of any way to do anything that would hinder your production if I just know your handle, but the possibility is there. You don't want people finding out how to do that on you!

    I would should never post my handle in public, personally. I would do it in an email to either Howard or Elena, or in a PM to one of them, but nowhere else...

    Plus, issues like this one shouldn't even be affected by your handle...
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules