Connecting Tech Pros Worldwide Forums | Help | Site Map

Create folder at remote site

Tony WONG
Guest
 
Posts: n/a
#1: Aug 18 '08
there is an asp page at IIS server for creating folder at remote site via
virtual folder

it is tested at Windows 2003 server.

the asp is ok if
http://localhost/test.asp

however it is not ok (error http 500) after the path of localhost is changed
to server name
http://servername/test.asp

i've opened all the security permission (file & iis), but still not ok.

tony



=?Utf-8?B?T2xkIFBlZGFudA==?=
Guest
 
Posts: n/a
#2: Aug 20 '08

re: Create folder at remote site


"Tony WONG" wrote:
Quote:
the asp is ok if
http://localhost/test.asp
>
however it is not ok (error http 500) after the path of localhost is changed
to server name
http://servername/test.asp
This is for an inTRAnet site? Not for inTERnet?

First thing to do is to find the *actual* error you are getting. Fix your
browser:

-- Click on TOOLS menu
-- Click on INTERNET OPTIONS menu item
-- Click on ADVANCED tab
-- *UN*check "Show friendly HTTP error messages"
-- OK

Now see what the actual and full error message is. And show us the actual
line of code that gets the error.


Tony WONG
Guest
 
Posts: n/a
#3: Aug 21 '08

re: Create folder at remote site


it is an intranet site within a domain

it shows it does not have sufficient rights

however, if i change the authenication from integrated to basic.

it is ok now.

is it about rights delegation?


"Old Pedant" <OldPedant@discussions.microsoft.com¼¶¼g©ó¶l¥ó·s»D :6BB06F10-2577-492D-8538-5033DF43FFF6@microsoft.com...
Quote:
"Tony WONG" wrote:
>
Quote:
>the asp is ok if
>http://localhost/test.asp
>>
>however it is not ok (error http 500) after the path of localhost is
>changed
>to server name
>http://servername/test.asp
>
This is for an inTRAnet site? Not for inTERnet?
>
First thing to do is to find the *actual* error you are getting. Fix your
browser:
>
-- Click on TOOLS menu
-- Click on INTERNET OPTIONS menu item
-- Click on ADVANCED tab
-- *UN*check "Show friendly HTTP error messages"
-- OK
>
Now see what the actual and full error message is. And show us the actual
line of code that gets the error.
>
>

Closed Thread