How do I make a web page on 2nd server viewable through the remote web workplace?

I have a SBS 2003 server with remote web workplace enabled as \\server1\remote and I need make a web site running on a 2nd server, \\server2\webapp1, accessible via the remote web workplace on server1.  The web site on server2 needs to be accessible without a VPN connection.

I have tried adding \\server2\webapp1 as a virtual directory on server1's IIS6 as a URL redirection which works inside the firewall or with a VPN connection as http://server1/webapp1, but it does not work unless you use the VPN or are inside the firewall.

How can I make the path in IIS6 on server1 to server2\webapp1 work for users connecting via the remote web workplace?  I know how to add a link to the remote web page that gets displayed after login, but not how to set a path that works.
mec_tvilleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You don't need to do a redirect.  Just create your virtual directory and then set the home folder as the UNC path to \\server2\webapp1.

Then, just use  a link that will resolve externally... ie, the external FQDN... http://server.domain.com/webapp1

Make sure that the permissions on your \\server2 share are compatible with IIS.  (look at the default permissions of C:\Inetpub\wwwroot for an example)

Jeff
TechSoEasy
0
mec_tvilleAuthor Commented:
I deleted my virtual redirect and re-ran the new virtual directory wizard which finds the share on server2.  I restarted IIS and now I get "The Page Cannot Be Displayed", http 500 errors.  I tried to connect to http://localhost/webapp1 on the local server which gave me the 500 error.  Shouldn't I be able to view the server2/webapp1 page on server1 using localhost/webapp1 which would make it accessible via the FQDN address?  I can navigate to the webapp1 shared folder which indicates the share is setup correctly.  
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
mec_tville,

>>  Shouldn't I be able to view the server2/webapp1 page on server1 using localhost/webapp1 which would make it accessible via the FQDN address?  
Well, not if permissions are wrong... and also it depends on what this webapp is running.  Can you provide a bit more info about that?  ie, is it ASP .NET?  if so, which version of .Net?

Jeff
TechSoEasy
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

mec_tvilleAuthor Commented:
My knowledge of IIS is limited, but here goes.  I set the share permissions on \\server2\webapp1 to be domain users with change and read permissions and I set the NTFS security for domain users to be read, list folders and read and execute.  The web app on server2 was created by a time entry application called BigTime and is accessible locally on server2; it uses ASP files and is not .NET.

The virtual directory on server1 IIS is set to not allow anonymous access and use integrated Windows authentication.  When I try to connect to http://server1/webapp1 from a local PC, I am getting a login window, but it will not accept my credentials which happens to be domain user as well as domain admin.
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It doesn't sound as though you matched the permissions that are set for C:\Inetpub\wwwroot as I had suggested.  Please go back and do that.

For the Sharing Permissions, set it to EVERYONE Full Control.  (NTFS will prevail).

Jeff
TechSoEasy
0
mec_tvilleAuthor Commented:
Sorry for the delay, I have been swamped.

I'm still having trouble getting to http://server1/webapp1, so I tried playing on a 3rd server's IIS and I got better results.  I have setup IIS on server3 to pull up webapp1 from server2.  On server3 I can type in http://localhost/webapp1 and I get the correct web page; however if I try to go to http://server3/webapp1 from desktop1 I get asked for credentials and it will not take them.  At least this is progress so I went back to server1 IIS and followed the same procedure but I get an http 500 error instead of the web page.

So I have 2 issues.  One, how can I get desktop1 to connect to http://server3/wwebapp1 since it is not accepting my Windows credentials?  Two, how come I cannot even display webapp1 on server1 as I do on server3, server1 is SBS 2003 while server2 & 3 are both W2K3 Std servers?
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'd take a guess that the reason you can't display webapp1 on server1 may be due to the ISAPI filters or FrontPage Extensions that are in place on the default web site of server1.

Understand that by creating a virtual directory on Server1 and then just pointing to a folder on Server2 as we've done, the app is really running on Server1.  So, it may be in conflict with the Application Pools on the SBS.

A redirect, which is what you were initially wanting to do, would make the app run on Server2.

But first, change IE on the SBS to disable "Friendly Error Messages" so you can get the exact error that's occuring and post that back.

Jeff
TechSoEasy
0
mec_tvilleAuthor Commented:
I'm back to where I started, I do want the app to run on server2 not server1.  I've got the URL redirect virtual directory set up again and I can type in http://server1/webapp1 and get to the app on server2, when I am inside the firewall.  From outside, I type in http://www.intranet.com/remote to login in and then click on a link that goes to the redirect server, http://www.intranet.com/webapp1 which bring up a page not found error.  Even though server1 can find server2, the path of the URL redirect, http://server2/webapp1, cannot be found outside the firewall.  There is no outside address to server2, so I need a way to make the link on our remote page point to an address that can be resolved from outrside the firewall?
0
mec_tvilleAuthor Commented:
Thread closed, sounds like I need to consider a reverse proxy server such as MS ISA.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.