markcash
Tue Jun 27 14:46:58 CDT 2006
Thanks for the reply.
The first option that I had tried with the Virtual Directory was using
the "A share located on another computer". And yes, this was pointing
to the folder on the IIS6 machine where the ASP.NET pages are located.
Trying it this way was where I was just getting the HTML portion of the
.ASPX page, but none of the additonal information that should have been
returned by the .ASPX page. It appeared that the .ASPX page wasn't
actually being executed. It makes sense now why this method does not
work. The IIS5 machine does not have the .NET Framework installed
therefore it doesn't know what to do.
Looks I need to look into some of the solutions that you recommended.
Thanks again for your advice.
Mark
Kristofer Gafvert wrote:
> Hello,
>
> I am not sure I understand. What do you mean by this?
>
> "I have created a Virtual Directory and tried pointing it to the shared
> folder, but all this does is bring back the HTML portion of the page, it
> doesn't seem to run the application."
>
> What "shared folder" do you mean? And I thought that you wanted HTML to be
> returned to the client, as that is the only thing the client understands.
> So what exactly is happening?
>
> What I *think* you mean is that you have pointed the virtual directory to
> a folder on the IIS 6 machine, and this folder has the ASP.NET pages. When
> you do this, IIS will treat the file as if it was stored on the local hard
> drive. This means that IIS 6 is not even involved, hence it cannot be able
> to process the ASP.NET code. To my understanding the IIS 5 machine cannot
> execute ASP.NET, hence the ASP.NET code will be returned to the client
> (depending on your configuration).
>
> " Also I have tried setting the virtual directory to redirect to this
> other web server, but this doesn't seem to work either."
>
> It most likely works, but probably not in the way you think. A redirect is
> what it says it is - a redirect. It redirects the client to make a new
> request for the new location of the resource. This means that if your IIS
> 6 machine is not publicy available, and you redirect using a local host
> name, the client outside your network will not find the server. Or to
> explain it in short, if you redirect, the client must be able to make a
> direct connection to the redirected resource. To my understanding, this is
> not possible in your situation, hence a redirect is not the solution of
> your problem.
>
> As i see it, you have a few solutions.
>
> 1) You can make the IIS 6 machine available so the client can connect to
> it, and by doing this redirects work.
>
> 2) You can use a reverse proxy software, an ISAPI filter such as ISAPI
> Rewrite will probably work.
>
> 3) You can move your ASP code to IIS 6 (and run in IIS 5.0 compatible mode
> if you cannot use worker process mode).
>
> 4) You can install ASP.NET on the IIS 5 server
>
> I would do option #3, unless the website is very complex and it would take
> much time and not be worth it considering that you are migrating to ASP.NET.
>
> --
> Regards,
> Kristofer Gafvert
>
http://www.gafvert.info/iis/ - IIS Related Info
>
>
> markcash@Hotmail.com wrote:
>
> >I have kind of a strange situation here. Our public website is running
> >on a IIS 5 server. We have several ASP search pages on this website.
> >I am slowly, as time permits, re-writting these in ASP.NET and placing
> >them on our new web server which is running IIS 6. On the website (on
> >the IIS 5 server) I need to create a link that points to the IIS 6
> >server. I have created a Virtual Directory and tried pointing it to
> >the shared folder, but all this does is bring back the HTML portion of
> >the page, it doesn't seem to run the application. Also I have tried
> >setting the virtual directory to redirect to this other web server, but
> >this doesn't seem to work either. It seems like the problem is that
> >the IIS 5 box being my "Publicly Accessible" server, it doesn't know
> >that the IIS 6 box exists.
> >
> >Does anyone have any ideas on how to get around this issue? The
> >obvious would be to go ahead and move the web server to the IIS 6 box
> >but I really don't want to do that. I wanted to migrate the site as I
> >rewrote it in ASP.NET.
> >
> >Any help would be greatly appreciated.
> >
> >Mark