Re: Installing WSS3 on remote SQL Server 2005 & Different Internet
- From: Andre Viens <AndreViens@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 15:32:01 -0800
Well primarily DNN has been slow in its response time when I request a page.
I understand its due to the way the codebase operates, and if it was accessed
more frequently, the site itself would be speedier. My boss hasn't been very
keen as to the speediness.
I've also been running into some technical issues with the Windows
authentication for some people not recognizing them, and since the new 4.x
updates, the display name doesn't get filled in from AD.
DNN is still something I enjoy to check out, and I used to be very hyped
about it, but I find that it's still a work in progress... I keep
experiencing small bugs that I report and then wait for the next minor
version upgrade... it's acceptable on a non critical app, but I'm leary to
use it on something like an intranet portal... because if I explain to people
that "this bug is being worked on", and things like that, they may lose
confidence in the product I'm touting and not use it at all.
But I still love DNN and the community. Open source is always a great thing
to have.
--
- Andre
"Matt" wrote:
Oh yeah, WSS3 way better than v2 ... What don't you like about DNN? I.
was planning on using it for our public website, so non-tech people
could maintain it.
Andre Viens wrote:
Hi Matt,
Thanks for confirming that. I suspected farm setup as well. I will give it a
go.
I haven't extensively checked the WSS team blog. I will look it over in more
detail over the weekend.
Perhaps using farm setup will also allow me to change port numbers too? I
just thought I'd have no problems installing on an existing web server with
other apps. Note that I did check the important information Microsoft stated
regarding existing web apps... when I clicked on the link, it just talks
about making it work with OWA. Our front end is another machine for the
outside world only.
Perhaps down the line I may utilize WSS for an Internet site for our
organization. We have multiple individuals that need to upload information
both for our intranet and Internet sites.
I was going to use DotNetNuke for our intranet, but WSS3 is here, and I'm
not fully done launching the DNN portal yet (it hasn't really won me over
completely now that I've been utilizing it). So far I've been really
impressed with what WSS3 has to offer over WSS2.
--
- Andre
"Matt" wrote:
Hmmm ... you're going for a "farm" setup ... the server you are
installing on should only be a front-end server. I think that is the
first question you answer in the install. Have you checked out the WSS
team blog?
Not sure about the port.
Andre Viens wrote:
Hello,
I'm attempting to install the recently released Windows Sharepoint Services
3 onto our web server.
I ran into a problem with two things:
First, how do I install WSS3 onto a remote SQL Server install instead of
using the embedded DB that comes with it?
Secondly, how does one configure the ports that you run WSS on? I appeared
to run a basic installation, as the advanced scenario didn't tell me "choose
a remote SQL server" and I never had a chance to choose a port on my web
server.
As a result, Sharepoint decided to make it the end all/be all of port 80,
screwing up my other web sites running on the same port.
I stopped the web site and started my apps sites, and it worked fine.
Changing the Sharepoint port to an alternate port will not work.
I can't seem to find the installation instructions for these advanced
scenarios anywhere. Perhaps I am looking in the wrong places.
Is my set up considered a "web farm" despite using only one web server?
Thanks to anyone who can shed light on this.
- Andre
- References:
- Prev by Date: Re: Transfer data from V2 to V3 server
- Next by Date: IE 7 Problem: Admin web site WSS V2
- Previous by thread: Re: Installing WSS3 on remote SQL Server 2005 & Different Internet
- Next by thread: Re: Installing WSS3 on remote SQL Server 2005 & Different Internet
- Index(es):
Relevant Pages
|
