Re: Fresh sbs install needed?
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Tue, 9 Aug 2005 21:44:53 -0700
Nick,
If you have not cleared your Event Viewer logs, look through them and post
the Sharepoint error you got. When you say that all updates are installed,
do you mean that you installed Server 2003 SP1, Sharepoint SP1, and SBS SP1,
per http://www.smallbizserver.net/Default.aspx?tabid=236?
Gregg Hill
"Nick" <nickmirro@xxxxxxxxxxxxxx> wrote in message
news:OHy40KWnFHA.3256@xxxxxxxxxxxxxxxxxxxxxxx
> Something is definately wrong. sql server manager lists no server or
> services to chose from and is not running. I have the ports configured
> correctly. I did run the ceicw. I recall a sharepoint error during os
> installation but I thought it resolved itself. All updates are installed.
>
> I just ran the ceicw again and now http://servername does not bring up
> sharepoint any longer. http://localhost does though. Starting to feel in
> over my head.
>
>
>
> "Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
> news:e2z27vKnFHA.1480@xxxxxxxxxxxxxxxxxxxxxxx
>> Nick,
>>
>> If you use https://servername/remote from the LAN, you should get the
>> login prompt. When you enter a valid user name and password, you should
>> get your RWW home page. You need to figure out why you get a "page not
>> found" error at this point. If it will not work on the LAN, you will
>> never see it from the Internet.
>>
>> Technically, http://www.DomainName.net does not point to your Linux
>> server, it points to your router's WAN IP address. The router then
>> directs port 80 traffic to the Linux server by port forwarding. When you
>> say that you have "forwarded ports 443, 444 and 4125 to the sbs server"
>> are you saying the Internet router is doing the forwarding? It should be
>> the one that does the forwarding. I ask because some people use Linux as
>> a router/firewall.
>>
>> You should have your router forward port 80 to the Linux server for your
>> web site, and forward ports 443 and 4125 to the SBS server for RWW. I
>> cannot remember if port 444 is company web or ???? but it is not needed
>> for RWW, nor is port 80 needed for RWW, assuming that you have set it up
>> to require SSL.
>>
>> Have you run the CEICW on the SBS to get it ready to run RWW?
>>
>> Gregg Hill
>>
>>
>> "Nick" <nickmirro@xxxxxxxxxxxxxx> wrote in message
>> news:%23yw1RhJnFHA.2920@xxxxxxxxxxxxxxxxxxxxxxx
>>> Well this all makes perfect sense and is very helpful. When I try to
>>> connect locally, I can get to the sharepoint site by typing
>>> https://ServerName only. If I add the /remote, I still get the logon
>>> but then a "page cannot be found" error results.
>>>
>>> If I try to connect by the internet, https://www.DomainName.net/remote,
>>> I cannot connect. This would make sense to me since
>>> http://www.DomainName.net points to the Linux server. I have forwarded
>>> ports 443, 444 and 4125 to the sbs server. Does rww also use port 80?
>>> The linux server is currently using that port. Apache can be configured
>>> to forward requests. Can I ask which machine should do what, port wise?
>>>
>>> Nick
>>>
>>>
>>>
>>> "Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
>>> news:OX1DIjGnFHA.3900@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Nick,
>>>>
>>>> To get to RWW from the LAN as a test, you would enter
>>>> https://server-netbios-name/remote into your IE browser. If your
>>>> server's name is Bubba, you would enter https://bubba/remote to access
>>>> it from the LAN.
>>>>
>>>> As far as getting to RWW via the Internet, since you have your web site
>>>> running on the same router as SBS, you would not need any new DNS
>>>> entries, because the world already knows your domain name. For example,
>>>> if www.domain-name.net points to the router that has your web site and
>>>> SBS server behind it and you just port-forward one IP address to the
>>>> appropriate server (web or SBS), you would access RWW by entering
>>>> https://www.domain-name.net/remote into your browser. Assuming you have
>>>> Exchange running, if you wanted to access OWA, you would enter
>>>> https://www.domain-name.net/exchange into the browser. Most of my
>>>> clients host their web presence at another site. We set up MX and A
>>>> records that point mail.domain-name.net to the IP address of their SBS
>>>> server. That allows their web site to function independently of where
>>>> their mail goes. When I set up a new SBS 2003 server, I always give it
>>>> a WAN name of mail.domain-name.net (or whatever suffix you have
>>>> registered for your domain). That way, I can get to RWW or Exchange by
>>>> entering https://mail.domain-name.net/remote or
>>>> https://mail.domain-name.net/exchange and it will not interfere with
>>>> the WWW site a company may have hosted elsewhere.
>>>>
>>>> Is that clear now?
>>>>
>>>> Gregg Hill
>>>>
>>>>
>>>>
>>>> "Nick" <nickmirro@xxxxxxxxxxxxxx> wrote in message
>>>> news:efDbAIDnFHA.2180@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Well this is really good news! Thanks for the help. Being I am new
>>>>> to sbs, I would really benefit from some clarification.
>>>>>
>>>>> Since the .local suffix will not work from the web, would I first need
>>>>> to register a new domain name such as remote.DomainName.net? Our
>>>>> linux website is run locally through the same router sbs uses.
>>>>>
>>>>> On the local network, if I browse to https://SBSServerPrivateIP I am
>>>>> taken to the sharepoint site instead of the primary rww screen. Is
>>>>> this correct? The logon screen does not appear to be the regular rww
>>>>> logon page. It is just a popup. Have I not fully completed sbs
>>>>> setup?
>>>>>
>>>>> Nick
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
>>>>> news:OnYM$m%23mFHA.1948@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> SuperGumby,
>>>>>>
>>>>>> Did I misread the original post? First, he says that "Our internet
>>>>>> (Linux based) domain name matches our sbs server domain name" but
>>>>>> then clarifies that "On the web we are: DomainName.net. The sbs
>>>>>> server domain is called: DomainName.local" which to me shows that the
>>>>>> Internet FQDN and internal domains are indeed named differently as
>>>>>> they should be.
>>>>>>
>>>>>> Nick, as long as the internal domain name is not EXACTLY the same as
>>>>>> your Internet FQDN, you should be fine. What I mean by that is the
>>>>>> domain name and suffix should NOT match between your Internet name
>>>>>> and local name, nor do they match, according to what you said ("On
>>>>>> the web we are: DomainName.net. The sbs server domain is called:
>>>>>> DomainName.local.")
>>>>>>
>>>>>> For example, your Internet FQDN could be abc-company.net and your
>>>>>> internal name could be abc-company.local (which is what you said) or
>>>>>> abc-company.internal or abc-company.lan or abc-company.bubba if you
>>>>>> wanted it to be. It is the internal domain suffix that should be
>>>>>> different from the Internet FQDN suffix. I never set up an internal
>>>>>> domain using the .local suffix, since as SuperGumby stated, it can
>>>>>> cause problems with Macs on the local network. Your internal name
>>>>>> could be xyz123.any-stinkin-name-I-want if you desired to get very
>>>>>> strange. The idea is to keep Internet FQDN which includes the suffix
>>>>>> different from the LAN name, especially the suffix.
>>>>>>
>>>>>> Nick, when you ask "To access rww, shouldn't I have named the sbs
>>>>>> domain: SubdomainName.DomainName.net?" the answer is no, you should
>>>>>> not have. Whether or not your Internet domain and SBS domains are
>>>>>> both at the same location (it sounds as though you run your web
>>>>>> server locally and not at an ISP), what you can do is create a public
>>>>>> DNS record and point it to the IP of your SBS server's WAN NIC (or
>>>>>> preferably the WAN firewall for the SBS external NIC). Even if your
>>>>>> web site is hosted at an ISP, you could create a DNS record called
>>>>>> remote.DomainName.net and point it to your SBS server's WAN IP
>>>>>> address.
>>>>>>
>>>>>> Gregg Hill
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
>>>>>> news:%23kSbaZ9mFHA.3380@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>>I am probably the most RABID proponent of 'you stuffed up and named
>>>>>>>your AD DNS the same as your internet FQDN' however not even I would
>>>>>>>call it the basis for a reinstall.
>>>>>>>
>>>>>>> You should have named your AD DNS whatever.something_private, .lan
>>>>>>> is my preference because Mac OS and some versions of Linux have
>>>>>>> started treating .local (as advised by the installation wizard) in a
>>>>>>> special manner. There is _no reason_ for your AD DNS name to reflect
>>>>>>> your public namespace.
>>>>>>>
>>>>>>> I will go so far as to say that _IF THIS IS A NEW INSTALL AND YOU
>>>>>>> ARE NOT YET TOO COMMITTED_ it is worth rectifying. With three
>>>>>>> attached ws's I'd probably do it.
>>>>>>>
>>>>>>> "Nick" <nickmirro@xxxxxxxxxxxxxx> wrote in message
>>>>>>> news:eqAaXH9mFHA.3336@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>>> Our internet (Linux based) domain name matches our sbs server
>>>>>>>> domain name. : - ( On the web we are: DomainName.net. The sbs
>>>>>>>> server domain is called: DomainName.local. To access rww,
>>>>>>>> shouldn't I have named the sbs domain:
>>>>>>>> SubdomainName.DomainName.net?
>>>>>>>>
>>>>>>>> To get rww working do I need to completely reinstall sbs with
>>>>>>>> naming as described?
>>>>>>>>
>>>>>>>>
>>>>>>>> There are 3 machines added to the sbs domain by the web based
>>>>>>>> utility. Should they be removed from (invalid?) domain? Will I be
>>>>>>>> stuck with obsolete domain client logon options if I reinstall sbs?
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Fresh sbs install needed?
- From: Nick
- Re: Fresh sbs install needed?
- References:
- Fresh sbs install needed?
- From: Nick
- Re: Fresh sbs install needed?
- From: SuperGumby [SBS MVP]
- Re: Fresh sbs install needed?
- From: Gregg Hill
- Re: Fresh sbs install needed?
- From: Nick
- Re: Fresh sbs install needed?
- From: Gregg Hill
- Re: Fresh sbs install needed?
- From: Nick
- Re: Fresh sbs install needed?
- From: Gregg Hill
- Re: Fresh sbs install needed?
- From: Nick
- Fresh sbs install needed?
- Prev by Date: Re: VPN errors After SBS2003 SP1 install.
- Next by Date: Re: NT PDC and BDC on new SBS 2003 install
- Previous by thread: Re: Fresh sbs install needed?
- Next by thread: Re: Fresh sbs install needed?
- Index(es):
Relevant Pages
|
