apache alias problem

[TheDude05]

I'm trying to put this directory we used to have as a virtual directory under IIS 3 as an alias in apache. The directory that IIS used was "\\cah_server\SophosEM\CIDRoot". So in the httpd.conf I put this..

Alias /sophos "//cah_server/SophosEM/CIDRoot"

<Directory "//cah_server/SophosEM/CIDRoot">
       Options Indexes MultiViews ExecCGI
       AllowOverride All
       Order allow,deny
       Allow from all
</Directory>

As is, the server wont load... if I change all the "/" to "\" like windows it'll boot but I get a 404. If I change the first part of the UNC to "\\" with the rest still "/" it will also load but again a 404.The folder has permissions for everyone so apache should be able to see it. Any ideas? I've done this numerous times under linux but never windows...


oh yea the server is NT 4 if that makes any difference

 

[Ralman]

Have you tried mounting the share to a drive letter, then use the drive letter and path (if applicable) for the Alias and Directory settings:


Mount the share "//cah_server/SophosEM" to say drive letter X:.
You can even set the drive letter to remount the share on startup.

Alias /sophos "X:/CIDRoot"

<Directory "X:/CIDRoot">
       Options Indexes MultiViews ExecCGI
       AllowOverride All
       Order allow,deny
       Allow from all
</Directory>

 

[MorfiusX]

Mount the share "//cah_server/SophosEM" to say drive letter X:.

LOL. I think you mean map a drive in the Windows world. Mounting is a*NIX thing.

The problem here is that the mapped drive won't be available as a service. Mapped drives are for currently logged in users. It needs to work using a UNC path.

 

[TheDude05]

I got it working. I mapped the directory to a drive letter and it would show up in the url but the user would get a 403 error. Ran the service as Administrative user and it worked.

 

[MorfiusX]

I got it working. I mapped the directory to a drive letter and it would show up in the url but the user would get a 403 error. Ran the service as Administrative user and it worked.

Generally, you don't want to do this. If your site gets attacked, an attacker could gain administrative access to your machine. Most services should be ran as a non-priveledged user for this reason.

 

[TheDude05]

Generally, you don't want to do this. If your site gets attacked, an attacker could gain administrative access to your machine. Most services should be ran as a non-priveledged user for this reason.

Yea I don't have it like that anymore. I made a web user as soon as I got it to work. I was just showing that it was a permissions error and nothing else.