OK now I was able to reproduce it...
Here is one log entry:
11/14/05 08:01:40 192.168.0.55 olaf.krause 0000004298 Created:
11/14/05 08:01:40 192.168.0.55 olaf.krause 0000004298 Requested:
http://cgi4.ebay.de/ws/eBayISAPI.dll
11/14/05 08:01:40 192.168.0.55 olaf.krause 0000004298 Debug: [cgi4.ebay.de/ws/eBayISAPI.dll] Copy to use: SERVER
11/14/05 08:01:40 192.168.0.55 olaf.krause 0000004298 Debug: WWW Session sending server request in thread 10bc
11/14/05 08:02:01 192.168.0.55 olaf.krause 0000004298 Traffic 314 2219 0 0 21s
11/14/05 08:02:01 192.168.0.55 olaf.krause 0000004298 Terminated exit code 2
11/14/05 08:05:24 192.168.0.55 olaf.krause 0000004314 Requested:
http://cgi4.ebay.de/ws/eBayISAPI.dll
11/14/05 08:05:24 192.168.0.55 olaf.krause 0000004314 Debug: [cgi4.ebay.de/ws/eBayISAPI.dll] Copy to use: SERVER
11/14/05 08:05:24 192.168.0.55 olaf.krause 0000004314 Debug: WWW Session sending server request in thread 171c
11/14/05 08:05:45 192.168.0.55 olaf.krause 0000004314 Traffic 314 2219 0 0 23s
11/14/05 08:05:45 192.168.0.55 olaf.krause 0000004314 Terminated exit code 2
After that I went to use NAT and it works so seems to be a wingate problem and not a ebay server one. The response time of the ebay server is <10s if I use NAT or socks...
The timout seetings for the WWW-Service is set to 120s.