Richard,
Just a qiuck idea, have you tried creating the share? Unlike IIS w/FPSE,
Apache won't create the share or set the permissions on it.
I had this problem too, and that fixed it for me, even on a remote
Windows/Apache install. It's been a while since I did it, but I'll verify
the configuratio
Chris
I'm coming in late to this, but have you tried appending the port number to
the url?
If you haven't already found it, take a look at here:
http://www.thrrrust.com/~pclark/blog/2005/03/fun-with-windows-xp-and-webdav.
html
It helped me with this problem.
Regards,
Todd
-Original Message--
Bill,
Is it possible to get the last development build?
Regards,
Todd Hicks
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 25 July, 2006 7:00 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Retirement of mod_aspdotnet
Graeme Walker
Sage,
Another solution, if you don't want/need to disable IIS entirely, is to
disable socket pooling in IIS following these instructions:
http://support.microsoft.com/kb/238131/
I did this on my setup and it allows both IIS and Apache to listen on the
same port (non-ssl) as long as you have host h
Dewey,
I know that this doesn't exactly answer the mail, but...
my solution to this problem was rather than using a network share, I used an
iscsi solution.
Using the microsoft iSCSI initiator on the host and an iscsi enterprise
target on FC4. If your remote storage needs to be a windows host, then
