Accessing an asp page 2

[sweetleaf]

My company has a website hosted remotely by an isp.
I would like to put several links on the "contact us" page of the site which when clicked open up customer support html/asp forms for users to fill out. These forms are to be stored on a machine on site here at the head office . Furthermore, these forms will insert and update an access database here at head office as well.

1)Assuming the isp updates the hyperlinks on the "contact us" page to "point" to the machine here at my head office,
which contains both the html/asp forms and the MS access database, is it possible for users to be able to see and use these html/asp forms?
2)if so what steps need to be implemented?

any help would be greeeeatly appreciated - thanks

 

[link9]

Yes, that will be no problem...

As long as those forms have an address that is accessible by anyone on the Internet, then you should have no problems whatsoever. Just test the pages, make the link point to the pages, and you're in business.

If you're asking how to make those pages available, then you'll first need a static IP to the box where they reside. Then, you assign that IP address to the IIS console, turn on your website, and away you go.

Simplistic explanation of how to turn on a website, but I'm not sure that's what you were asking. If so, and you need more info, then just post back.


paul

 

[sweetleaf]

Thanks link9! that was extremely helpful..

 

[sweetleaf]

So, users on the outside world on the internet will be able to be redirected to my web pages here at head office (on a peer to peer machine with a static IP /and NO domain) and consequently be able to insert into and update the MS Access database on this machine? cool!
The machine will have IIS but no Interdev on it.
I'm thinking all i have to do is
-put the htm's and asp's into a folder in inetpub/

http://wwwroot

-open microsoft management console and locate the folder, right click and create a website name
-create a dsn fo the db
-provide the ISP with the machine IP,website name, and document name (ie.

http://xx.x.xxx.xxx.Web1/default.asp)

so they can update the links on the "Contact Us" page.

Are there any security risks. if so what are they?

Thanks link9,
Mark

 

[link9]

Just know that simply giving the website a name in your IIS console won't make that an "Internet Address". Probably wanna stick w/ your IP address as far as that goes.

As far as security risks... the best you can do is only leave port 80 open on the firewall leading to the machine. Be sure that all FTP access is turned off. Then, the site is ONLY administerable from inside your office. People can access it via HTTP, but cannot get to it any other way.

You won't be completely safe, but are we ever? ;-)

Your network folks will know of more things to do to make it more secure if you're still concerned.


paul

 

[programsecrets]

Although the method described above is probably preferred because all information is on-line locally, if you want (or need) to minimize your security risk by not exposing your local machine on the internet at all, you could still have those forms/pages on the remote ISP's machine together with a small Access DB there. Then, view the db info through internally used web pages and/or download the Access db on a regular basis.

That's just another option, depending upon the security risks your company may or may not be willing to take.

 

[sweetleaf]

Hi Link9,

Actually thinking back a few steps what did you mean when you said "Then, you assign that IP address to the IIS console.."? sorry, i just didn't get that part could you explain that part?

Thanks

 

[link9]

When you open up your Microsoft Management Console (AKA the IIS console), right click on your "Default Web Site", or whatever it might be named (the one in question), and ask for "Properties"

The first window you see should have a box for IP address. By default, it will read "All Unassigned". Plug the IP for your machine in there. That will assign your website to that IP, so that when an HTTP request comes in for the IP, IIS will know what site the request wants.


paul