• February 23, 2025, 11:59:10 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: P2P setting page problem  (Read 6019 times)

areios755

  • Level 1 Member
  • *
  • Posts: 3
P2P setting page problem
« on: October 29, 2009, 09:59:28 AM »
I can't configure in P2P setting page of the P2P tool:

in port setting,
the "Incoming connections port" is always fixed as the string: "&163870503984999</b><br><p>CGI generated no output</p></body></html>"

and following error also appear on the setting page:

Path:    Access Error: Data follows
Torrent save path:    
when trying to obtain /cgi-bin/p2p.cgi?&218419801449392
CGI generated no output
« Last Edit: October 30, 2009, 02:56:29 AM by areios755 »
Logged

areios755

  • Level 1 Member
  • *
  • Posts: 3
Re: P2P setting page problem
« Reply #1 on: October 30, 2009, 02:49:12 AM »
Quote from: areios755 on October 29, 2009, 09:59:28 AM
I can't configure in P2P setting page of the P2P tool:

in port setting,
the "Incoming connections port" is always fixed as the string: "&163870503984999</b><br><p>CGI generated no output</p></body></html>"

and following error also appear on the setting page:

Path:    Access Error: Data follows
Torrent save path:    
when trying to obtain /cgi-bin/p2p.cgi?&218419801449392
CGI generated no output

So far, I can't make P2P download...

I found it may caused by Goahead webserver on DNS-321.
The same issue reported and announced to have been fixed on Goahed website:
If Dlink update the Goahead server , the issue may be fixed.
hope this clue helpful.

http://data.goahead.com/Software/Webserver/2.1.4/release.htm

Intermittent Access Error for CGI Scripts (BUG01937)Summary:
Pages were occasionally replaced with the message, "Access Error: Data follows when trying to obtain CGI generated no output".

Fix:
On multiple CPU systems, it is possible for a CGI application to exit before its output is flushed to disk. The change for this release locates the code that collects the output from the CGI application in a separate routine. In addition to calling that routine from within the CGI application processing loop, it is also called in a brief loop after the CGI application has exited. This extra loop runs for only up to one second while the collected output remains empty. If, after 1 second, the output remains empty, the original course of action is followed ("Access Error" is reported).
Logged