How hard can it be?

[googlegroups]

We have just built a new webserver for development and would like to
run an asp.net site on it. The files that make up the site are on a
different server.
Both servers are windows 2003 servers and both have been fully patched.

When we try to setup the website in IIS6 we have to use a UNC to locate
the home directory. We use a domain account (domain\iisdev) to access
the files accross the network. If we try to map a drive and use the
ampping, then when we navigate there, the OK button is greyed out and
we can't select it.

We can see the folders file in the right panel in IIS6, but when we
come to view the site in our browser, we get all sorts of errors.

Can anyone give us a step by step process for configuring this kind of
setup with two fresh windows 2003 servers?

Both servers have been made application and fileservers. The webserver
has also been giving mail server role.

If I've missed anything out that you need to know, just ask.

Thanks everyone

[googlegroups]

Ive granted the domain user IISDev permissions to the
c:\windows\microsoft.net\framework folder and to the location of the
files on the fileserver. Ive also edited the machine.config on the
webserver so that the processmodel username and password relate to this
user.

Now I get and error telling me to include customerrors mode =off in my
web.config for the application, but it's already there.

Pleading for help now as this is driving me nuts!

[Michael]

Have you tried to use a share or the server IP for access?
\\1.12.12.123\mywebfiles|

"go**********@tlbsolutions.com" wrote:

We have just built a new webserver for development and would like to
run an asp.net site on it. The files that make up the site are on a
different server.
Both servers are windows 2003 servers and both have been fully patched.

When we try to setup the website in IIS6 we have to use a UNC to locate
the home directory. We use a domain account (domain\iisdev) to access
the files accross the network. If we try to map a drive and use the
ampping, then when we navigate there, the OK button is greyed out and
we can't select it.

We can see the folders file in the right panel in IIS6, but when we
come to view the site in our browser, we get all sorts of errors.

Can anyone give us a step by step process for configuring this kind of
setup with two fresh windows 2003 servers?

Both servers have been made application and fileservers. The webserver
has also been giving mail server role.

If I've missed anything out that you need to know, just ask.

Thanks everyone

[Patrice]

What kind of errors exactly ? Use a UNC name instead of a mapped drive. Aslo
if I remember the console uses the current account while the website uses
the credentials you entered when configuring the virtual path...

Also I'm not sure it's that great (not sure what you want but my personal
preference would be likely to mirror the files just sharing the possible
read/write content).

--
Patrice

<go**********@tlbsolutions.com> a écrit dans le message de
news:11**********************@g14g2000cwa.googlegr oups.com...

We have just built a new webserver for development and would like to
run an asp.net site on it. The files that make up the site are on a
different server.
Both servers are windows 2003 servers and both have been fully patched.

When we try to setup the website in IIS6 we have to use a UNC to locate
the home directory. We use a domain account (domain\iisdev) to access
the files accross the network. If we try to map a drive and use the
ampping, then when we navigate there, the OK button is greyed out and
we can't select it.

We can see the folders file in the right panel in IIS6, but when we
come to view the site in our browser, we get all sorts of errors.

Can anyone give us a step by step process for configuring this kind of
setup with two fresh windows 2003 servers?

Both servers have been made application and fileservers. The webserver
has also been giving mail server role.

If I've missed anything out that you need to know, just ask.

Thanks everyone

[Karl]

We are using a unc to the files in the website properties on IIS (home
directory points to \\OurFileServer\OurSiteFiles and the Connect As has
been configured to use a domain account with full permissions to the
files location.

At the moment we get a screen telling us to add a CustomErrors line to
the web.config file with the Mode set to 'Off', but this is already
there!

Thanks for your help guys.
Is there a set of proceedures I could follow for this type of
configuration anywhere?

[Karl]

FIxed it!

http://support.microsoft.com/default...b;en-us;320268

Thanks for your help guys

[Patrice]

What if you try with the local browser on the IIS server ?

Also with this kind of configuration I'm not sure ASP.NET is able to enable
file system watching so that it restarts automatically when a file is
changed...You may want to try to restart ASP.NET just in case... Also the
error might be written in the log file.

You could try just an HTML file. It could perhaps help to see if it's a
configuration problem on the IIS side or if it's related to ASP.NET.

Could be http://support.microsoft.com/default...b;en-us;320268 but
it would be likely much better to first solve the problem that prevents to
actually see the exact error.

--

Good luck.
"Karl" <go**********@tlbsolutions.com> a écrit dans le message de
news:11**********************@g14g2000cwa.googlegr oups.com...

We are using a unc to the files in the website properties on IIS (home
directory points to \\OurFileServer\OurSiteFiles and the Connect As has
been configured to use a domain account with full permissions to the
files location.

At the moment we get a screen telling us to add a CustomErrors line to
the web.config file with the Mode set to 'Off', but this is already
there!

Thanks for your help guys.
Is there a set of proceedures I could follow for this type of
configuration anywhere?