Hosting their own website with NT

[Jim A]

Hi All:  What steps are required in order to host a public website on the company server?  Right now, our NT apps are limited to our own people.  The next step is to expose parts of the data to the public.  My questions are:

1. Do we need to use port 80 for that?

2. What is the best way to set up the ip address with the company's url?

3. Are there restrictions that we should know about?

4. Any other gotchas.

Many thanks,

Jim

[kevin plummer]

1. Do we need to use port 80 for that?

> is it a static site or a DB app for your clients to use. Does it need to be secure?

2. What is the best way to set up the ip address with the company's url?

> when you register the URL most companies allow you to set the IP address via their DNS options.

[Jim A]

Hi Kevin: Thanks for your response.

> is it a static site or a DB app for your clients to use. Does it need to be secure?

It is not a static site. It is fed and driven by the data.  Everything is View only, though. Not a a web app.  It does not need to be SSL -- if that's what you mean by secure.

Thanks.

[kevin plummer]

In that case I would stick to port 80

[Jim A]

Thanks Kevin.

[bijan]

Hi Jim,

Port 80 is safer.
If they have a dynamic IP address, their ISP may change their IP at any time.
In my home, I have noticed that the IP address pretty much stays the same until I change a router or a modem.
You can use a service like no-ip.com  to deal with the dynamic IP issue.


 My questions are:

1. Do we need to use port 80 for that?

2. What is the best way to set up the ip address with the company's url?

3. Are there restrictions that we should know about?

4. Any other gotchas.

Many thanks,

Jim
[/quote]

[Jim A]

Thanks for the help.