How to move default web page on SBS 2003

Forums › Microsoft Windows › How to move default web page on SBS 2003

lyonrouge

1990 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

Topic # 11270 13-Jan-2007 10:17

The default page is very useful, so I do not want to remove it, however, it is not what I want presented to the public. How do I move it to a lower directory or even a different port, i.e. http://url/default/ or http://url:xxx?

PaulofByzantine

10 posts

Wannabe Geek

Reply # 58314 19-Jan-2007 00:29

i dont know much about SBS, but what i think that SBS could be using IIS in the background to setup your webistes virtual directories or what ever, so you might need to configure your default page manually from IIS console

chiefie

I iz your trusted friend
5811 posts

Uber Geek
+1 received by user: 140

Mod Emeritus

Trusted

Lifetime subscriber

Reply # 58324 19-Jan-2007 08:53

you sure there is a /default folder? And this is currently viewable from the public side?

If i think I know what you're refering to, it must be the initial "how to" set up your IIS for your website etc right?

PM me directly and I can help you with it.

Internet is my backyard...

«Geekzone blog: Tech 'n Chips Takeaway» «Personal blog: And then...»

Please read the Geekzone's FUG

geekiegeek

2121 posts

Uber Geek
+1 received by user: 369

Trusted

Subscriber

Reply # 58325 19-Jan-2007 09:02

It does use IIS.

Just right click the website and select properties. Change to port to something else (not 80) say 81 or 82 - set up your new site on port 80. all done.

When you live your life on Twitter and Facebook, and are only friends with like minded people on Twitter and Facebook, you are not living in the real world. You are living in a narcissistic echo chamber.

My thoughts are my own and are in no way representative of my employer.

chiefie

I iz your trusted friend
5811 posts

Uber Geek
+1 received by user: 140

Mod Emeritus

Trusted

Lifetime subscriber

Reply # 58326 19-Jan-2007 09:08

geekiegeek: It does use IIS.

Just right click the website and select properties. Change to port to something else (not 80) say 81 or 82 - set up your new site on port 80. all done.

Yeah it's easy as that, however it may affect the existing SBS IIS folders for like OMA, Exchange, Remote, TSWeb etc, as all those hook onto Default Web Site.

The easiest configuration is to use the Wizard again, to tell it that you don't want an Internet set up. This way, it will create a Default Web Site but it is not accessible from public.

Then go on to the IIS MMC, and add a new web site. (I trust that you know as much from then onward? If not pm me).

Internet is my backyard...

«Geekzone blog: Tech 'n Chips Takeaway» «Personal blog: And then...»

Please read the Geekzone's FUG

geekiegeek

2121 posts

Uber Geek
+1 received by user: 369

Trusted

Subscriber

Reply # 58327 19-Jan-2007 09:20

You are correct young Chiefie - to early in the morning to remember stuff like OWA.

My thoughts are my own and are in no way representative of my employer.

lyonrouge

1990 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

Reply # 58343 19-Jan-2007 14:15

I like the default site that SBS has created and wish to leave it running for internal purposes and I'm reluctant to change it as my ActiveSync will probably stop working.

I'm considering adding a new virtual server to host my public ontent, with a non standard port, i.e. 6666 and change my router to forward 80 requests to this port. Does anyone know if ActiveSync with SSL only uses HTTPS port (443) or does it use both HTTP and HTTPS?

geekiegeek

2121 posts

Uber Geek
+1 received by user: 369

Trusted

Subscriber

Reply # 58347 19-Jan-2007 15:04

99% sure its just 443 so as long as you use SSL you shouldnt have a problem - you could then set up another website on port 81 and nat 80 to 81 on your router.

My thoughts are my own and are in no way representative of my employer.

chiefie

I iz your trusted friend
5811 posts

Uber Geek
+1 received by user: 140

Mod Emeritus

Trusted

Lifetime subscriber

Reply # 58351 19-Jan-2007 15:19

It probably won't be too bad if you use SSL connection as it will connect at 443.

Few things that I have tried:

1) Denied Access to all IP Address except: (Default setup wizard setting when "Internet Web Site" is not checked")

My advice is, go to your IIS control panel, look at Default Web Site's properties and in the Directory Security > click the Edit in the IP Address and Domain Name Restrictions. Make sure you have selected "Denied Access" and put in 127.0.0.1 and the domain server's IP. So this limit the access to only IPs.

That way, you effectively telling everyone not to access your site from outside world.

2) Secret Host Name to Default Web Site

With this, you can add a host name to your default web site. Go to the properties, Web Site > click on Advanced in the Web Site Identification. Edit "Default:80" with Host Header Value say "secret.domainname.com", for example if you have DynDNS of "mysbs.mydns.com", then your Host Header Value can be "secret.mysbs.mydns.com". So when in the browser, if you type in "http://secret.mysbs.mydns.com" it will points to this website.

Then create a new website, point its directory to the folder where the content will be available to the public. So then it will answer all request to "http://mysbs.mydns.com".

3) New web site with Host Header Value

Instead of changing any default settings, create a new web site, point it to a folder that you want the public to see from the URL "http://www.mysbs.mydns.com" or "http://mysbs.mydns.com". In the Web Site Idenfication, add the Host Header Value for those URLs that you want the virtual website to answer to.

So then when someone typed in the URL that match either of the Host Header Value, they will see the content from that virtual website.

Combo:

My advice is, do the Option 1, and Option 2. That way, you can access the website from internal network, and also from the secret URL.

OR doing combo of Option 1 and Option 3, isn't bad too.

Whatever combo you do, MAKE SURE all your WM5 devices and Outlook RPC over HTTP are using SSL connection. So then all request are made through port 443, this way whoever is trying to view at port 80 can either get the Option 2, or Option 3 public website and won't hinder or cause and problem on all Exchange/OMA request at port 443.

Hope this help.

p/s: If in doubt, try view my website http://www.chiefie.geek.nz/ as you will then receive a message saying that you will not be able to access the site due to denied IP address.

Internet is my backyard...

«Geekzone blog: Tech 'n Chips Takeaway» «Personal blog: And then...»

Please read the Geekzone's FUG