web deployment issues / runtime errors

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

This si a repost, I apologize but perhaps my original inquiry got
buried under all the usenet spam...

I am having some problems deploying .NET content. My first guess is
that I am probably not using the correct approach to something here.
Hopefuly someone will be kind enough to get me back on track. :)

I'm hosting content on my own equipment. I have two machines - One
Win2K server acting as a PDC running DNS, IIS, and SQL Server 2000.
I have one other Win2K Professional machine that I use to serve up the
files for the web content. This is partly because this second machine
has a HUGE hard drive and is also my desktop PC, so it makes editing
conent easy and straightforward. The sites I host are very low
traffic for the moment, so there are no load-balancing or bandwidth /
performance issues as this time, and we'll deal with those once we get
the technical aspects of deployment worked out. Ah, the joys of
working on a budget! Anyway... the problem....

All this equipment is inside our private network, with a router
providng the inbound connection from the T1. So, my two machines are
server.office.local and workstation.office.local in the DNS. On my
workstation (ie fileserver) PC, I created C:\webs\MyWeb and made it a
share (\\workstation\MyWeb) for holding all the site content. Back on
the server, I created a new web site in IIS, set its host header and
all that, and then set it's home directory to \\workstation\MyWeb.
When I do this, I get warnings from the FrontPage server extensions
telling me that anyone can edit my site, and that I should use an NTFS
drive... bla, bla, bla... but that share IS on an NTFS drive. All of
my partitions on all machines are NTFS partitions.

Moreover, when I attempt to browse to the site, I get security
warnings from .NET. The pages I've put up so far are very simple web
forms that do stuff like put up a data grid of some stuff out of the
pubs database.... So I don't know what the big deal is. If I enable
IIS on \\workstation, and then browse to localhost\MyWeb, it works
just fine. However, if I try to go through the IIS server on
\\server, it won't work. If I move all of the web content off of the
file server, and put it into C:\inetpubs\wwwroot (or some other
subfolder) on \\server, then it runs fine. What's going on here?
Surely that can't be a limitation of the server and IIS... I know
almost no commercial shop that physically hosts everything on one
machine. Once again, it's probably something small I'm overlooking
here, but the darn error messages are so cryptic and usually have
NOTHING to do with what's "really" the problem. Any advice would be
greatly appreciated. :) Thanks!

JIM
 
I don't have time this morning to go into detail, but:

Don't use shares. I bet you haven't seen anyone else using shares for
ASP.NET.
 
John,

Are you suggesting then that all of the web files must physically
reside on the same box as the www server? Not to debate you, because
clearly I'm the one who is having trouble here, but that kind of seems
out of the spirit of the whole "N-Tier architecture" thing that .NET
is (supposed to?) support.... Or is there another way to accomplish
the smae task that I am overlooking?
 
Jim said:
John,

Are you suggesting then that all of the web files must physically
reside on the same box as the www server? Not to debate you, because
clearly I'm the one who is having trouble here, but that kind of seems
out of the spirit of the whole "N-Tier architecture" thing that .NET
is (supposed to?) support.... Or is there another way to accomplish
the smae task that I am overlooking?
Click to expand...

Putting web files on some other machine doesn't add a "tier", just problems.

You want to look into code access security to understand why you're having
problems, or better still, you should look into why you think it's a good
idea to put the files on a different machine.
 
Back
Top