Now I'm going to hurt somebody! Exchange & Sharepoint!

Butters

Butters

Butters

Permabanned
Joined
22 Apr 2007
Posts
1,805
I've installed Sharepoint 2003 now (exchange was running before sharepoint install fine)

Exchange is still ok but OWA (Outlook Web Access) no longer works.

I've checked IIS and see that OWA and Sharepoint are both fighting for the same port!

I'm not bothered but I really need OWA and sharepoint will probably only be used as an intranet site for employees.

How do I resolve this? I've checked documentation and microsoft seem aware of the issue and tell you to HTTPS Exchange but I need a certificate to do this and I dont want to have to buy one.

Is there an better, easier alternative?

Ta
 
in iis, you can have multiple websites running on the same server. look at setting up host headers. i'm afraid i don't know much about iis but that should give you something to look at... :p
 
In IIS you can set a different a web site to use a different port. So what you could do is change sharepoint to use port 81.

Either that or you could set sharepoint to be https only. You would need an SSL cert but if your running an AD environment you can setup an internal cert server. This would mean that you create your own certificate to assign to the sharepoint server and your internal domain members would automatically accept it and not moan about it not being signed properly.
 
TheKnat said:
In IIS you can set a different a web site to use a different port. So what you could do is change sharepoint to use port 81.
Click to expand...

why would you want to do that? iis supports multiple websites on port 80 using host headers as i mentioned above. :)
 
Different options for different circumstances. Might prefer to change the port rather than do it using headers.

One option is never best hence why he has asked here for help. Best to give out all the various options so the OP can make an informed choice.

Butters said:
ok, so if I set Sharepoint to be internal on port 81 all users would have do to is type in http://myserver:81 ?
Click to expand...

In answer to that question, Yes. If you plan to make this your internal intranet server you could make your life a bit easier by setting it as they're default home page in IIS as well. Thats what we have done for our Intranet site to make sure people don't forget the URL, because no matter how simple you make it the users will forget.
 
Last edited:
like i said, i'm not really familiar with iis, but i found this on google... :p

http://www.microsoft.com/technet/pr...544-3f70-4d46-a6df-bbadbd1fe7de.mspx?mfr=true

To assign multiple host header names to a single Web site

1.

In IIS Manager, expand the local computer, click the Web Sites folder, right-click the Web site for which you want to assign a host header name, and then click Properties.

2.

Click the Web Site tab.

3.

In the IP Addresslist, select the IP address that you want assigned to this Web site.

4.

Click Advanced.

5.

Under Multiple identities for this Web Site, select the IP address, and then click Edit.

6.

In the Host Header Value box, type the host header name (for example, www.contoso.com).

7.

Click OK twice.
Click to expand...

edit: that's a bit unclear with regards to your needs. but i'm sure you can work it out. you want one dns name per website, rather than multiple names on one website....
 
Last edited:
Instead of multiple ports why not use multiple IP's?

Just add a free IP to a NIC and then in IIS just choose the unassigned IP.



M.
 
You must log in or register to reply here.
Back
Top Bottom