Apache 1.3 on Windows XP

[Anon]

I am experiencing an interesting problem with Apache 1.3. Recently I have run it under Windows 2000 without any problems. After upgrading to Windows XP, visitors to the site get an error 'Cannot find server or DNS Error', this error appears after the page is partially loaded/viewable. When the page is viewed locally, it works fine.

Here is the interesting part. Some pages work, some don't. What seems to be the trigger is server side includes, not the existence of them, but instead the amount of them.

My SSIs are simple...just text list files (with about 20-50 lines in them), so I doubt it is the content. In addition, I have included a mod that grabs the date of the file and displays it. I have broken down a page (stripped out the SSIs) and rebuilt it...I get to the point where I can include 3 SSIs then when I add the 4th one, it gives the errors.

Here is the SSI code used:

<!--#config timefmt='%m.%d.%Y'--><!--#flastmod virtual='/includes/content/file.clip'-->

<!--#include virtual="/includes/content/file.clip" -->

Any ideas?

[Anon]

I have made the same experience! On other Windows versions Apache worked fine (with the same configuration serving the same files).
Then I tryed to leave SSI out of the files, but with long html-files the problem appeared too.
Even after replacing the SSI-commands with PHP4 the server returns the 'Cannot find server or DNS Error'-message.
MSIE4 and lower clients return a message "Microsoft server-extensions failed" and the apache error log produces hundreds of the following lines:

[Mon Oct 22 17:31:45 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/root.exe
[Mon Oct 22 17:31:45 2001] [error] [client 217.83.132.169] File does not exist: h:/msadc/root.exe
[Mon Oct 22 17:31:46 2001] [error] [client 217.83.132.169] File does not exist: h:/c/winnt/system32/cmd.exe
[Mon Oct 22 17:31:47 2001] [error] [client 217.83.132.169] File does not exist: h:/d/winnt/system32/cmd.exe
[Mon Oct 22 17:31:47 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:31:48 2001] [error] [client 217.83.132.169] File does not exist: h:/vti_bin/..%5c/..%5c/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:31:49 2001] [error] [client 217.83.132.169] File does not exist: h:/mem_bin/..%5c/..%5c/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:31:50 2001] [error] [client 217.83.132.169] Filename is not valid: h:/msadc/..%5c/..%5c/..%5c/..Á/..Á/..Á/winnt/system32/cmd.exe
[Mon Oct 22 17:31:50 2001] [error] [client 217.83.132.169] Filename is not valid: h:/scripts/..Á/winnt/system32/cmd.exe
[Mon Oct 22 17:31:52 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/..À¯/winnt/system32/cmd.exe
[Mon Oct 22 17:31:53 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/..Áœ/winnt/system32/cmd.exe
[Mon Oct 22 17:31:55 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:31:56 2001] [error] [client 217.83.132.169] File does not exist: h:/scripts/..%2f/winnt/system32/cmd.exe
[Mon Oct 22 17:36:57 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/root.exe
[Mon Oct 22 17:36:59 2001] [error] [client 217.83.111.31] File does not exist: h:/msadc/root.exe
[Mon Oct 22 17:37:00 2001] [error] [client 217.83.111.31] File does not exist: h:/c/winnt/system32/cmd.exe
[Mon Oct 22 17:37:02 2001] [error] [client 217.83.111.31] File does not exist: h:/d/winnt/system32/cmd.exe
[Mon Oct 22 17:37:03 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:37:05 2001] [error] [client 217.83.111.31] File does not exist: h:/vti_bin/..%5c/..%5c/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:37:06 2001] [error] [client 217.83.111.31] File does not exist: h:/mem_bin/..%5c/..%5c/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:37:08 2001] [error] [client 217.83.111.31] Filename is not valid: h:/msadc/..%5c/..%5c/..%5c/..Á/..Á/..Á/winnt/system32/cmd.exe
[Mon Oct 22 17:37:09 2001] [error] [client 217.83.111.31] Filename is not valid: h:/scripts/..Á/winnt/system32/cmd.exe
[Mon Oct 22 17:37:12 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/..À¯/winnt/system32/cmd.exe
[Mon Oct 22 17:37:13 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/..Áœ/winnt/system32/cmd.exe
[Mon Oct 22 17:37:18 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/..%5c/winnt/system32/cmd.exe
[Mon Oct 22 17:37:19 2001] [error] [client 217.83.111.31] File does not exist: h:/scripts/..%2f/winnt/system32/cmd.exe

Does anybody have a solution (without changing the server-software)?

Dan Houle wrote:

I am experiencing an interesting problem with Apache 1.3. Recently I have run it under Windows 2000 without any problems. After upgrading to Windows XP, visitors to the site get an error 'Cannot find server or DNS Error', this error appears after the page is partially loaded/viewable. When the page is viewed locally, it works fine.

Here is the interesting part. Some pages work, some don't. What seems to be the trigger is server side includes, not the existence of them, but instead the amount of them.

My SSIs are simple...just text list files (with about 20-50 lines in them), so I doubt it is the content. In addition, I have included a mod that grabs the date of the file and displays it. I have broken down a page (stripped out the SSIs) and rebuilt it...I get to the point where I can include 3 SSIs then when I add the 4th one, it gives the errors.

Here is the SSI code used:

<!--#config timefmt='%m.%d.%Y'--><!--#flastmod virtual='/includes/content/file.clip'-->
....

[Anon]

For what it's worth, all of those errors you see in your logs are just hits from the Nimda/Code Red virus that is still floating around. If you are on a cable or dsl connection, you will especially see a lot of them because of the way the virus propogates. Nothing to worry about though as you are not running IIS 🙂

Brandon Tallent
http://nesp.lowpass.org

[Anon]

It's nice to see I'm not the only one having this problem. I'm having problems with users accessing any pages with images. They can see text-only pages just fine, but as soon as there is an image, the page will time out for the user. I'm still searching for a fix to this problem....

[Anon]

I've found a work around for this problem:

simply set on the option "implicit_flush" in php.ini (c:\windows\php.ini on win_xp):

It should then look like this:

implicit_flush = On

after that, do at the prompt:
c:> net stop apache
c:> net start apache
and you're finished!
On my WinXP Pro box now all is running fine, both locally and remotely calling the server :-)

The problem is somewhere in the buffer used by php to give back finished html to apache: php makes it's work correctly as I verified invoking php.exe at the prompt piping the result to a htm file, that had at the end. Apache doesn't read out the entire data from the buffer but it thinks to do it... it remarks no problem, in the logfile you see: 200 <[to less] #bytes sent>. Maybe php relies on a system funciton that doesn't work as expected?

[Anon]

Seems a nice solution, but it doesn't work for me.
I changed the php.ini, restarted... ; but with Apache the problem is still there.

(The problem even occurs in pages with long html-only (no cgi, ssi, php or any other scripting) pages.......

[Anon]

Just out of curiosity, are we talking XP Home or Pro?

Will Apache run on XP Home?

thanks!

[Anon]

Windows XP Home, Professional, Server and Adv. Server share the same driver, service, network, API, security and kernel architecture, with artificial limitations only like maximum cpu's used.

So IMHO there is no reason for Apache to not run on WinXP Home.

[pinkbike]

I've just upgraded to XP Pro on my laptop from 2000 and now my local website/server is not serving the pages correctly. I know its not the code as this same code runs fine on a freebsd server sending out millions of pages a month and also it ran just fine on my 2000 (apache/php) setup.

As you mentioned it serves out some pages fine until the size of the page hits a certain point. Well I'm seeing the same.
Some article lists on my site are bigger than others and when I view one of these larger ones it just cuts it off or starts adding garbage.
I tried turning on the implicit flush in php.ini and restarting but no work. Someone also said that adding the php call flush(); after certain print/echo statements may work similarly. So I added a flush after every article printed in a list, and, hey IT WORKS! This is lame though, hope some one figures out a real fix for this stuff.
If you have anymore info I'd love to hear it [e-mail]

Thanks

DPh wrote:

Windows XP Home, Professional, Server and Adv. Server share the same driver, service, network, API, security and kernel architecture, with artificial limitations only like maximum cpu's used.

So IMHO there is no reason for Apache to not run on WinXP Home.

[Anon]

I seem to be having a freind with a similar thing. we will try the fix mentioned..
also does XP support and or have CGI built in it?..
Im currently running My personal on a win98 se machine..

im trying to get a freind set up with the XP version we will try the fix for his, and imn stil trying to figure out the cgi pearl issue how to add it where to get etc or if its already in
thanks all!

[Anon]

The errors reported in the original post are hits from the Code red and Nimda worms... look it up.

cheers

[Anon]

Hey Guys...

having the same problem with my Apache under Windows XP Pro...

find out that it must have something to do with a file in the Windows/system32/drivers/
afd.sys...

It's a OFFICIAL Windows Bug!! And Microsoft has a hotfix for that. Just read their article here.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q317949

You will not find any Hotfix there or anything else ON the microsoft page, but I have a FTP where you can download ALL patches, updates and hotfixes. Unfortunatly, everything there is packed as and Password protected by Microsoft :-(

so long...

[Anon]

Code Red, Nimda have nothing to do with this problem.

Krusy K. wrote:

The errors reported in the original post are hits from the Code red and Nimda worms... look it up.

cheers

[Anon]

Grab this fix NOW!

ftp://hotfix.microsoft.com/winnt/Windows_XP/sp1/Q317949/

and bingo no more problems