Re: Fresh sbs install needed?
- From: scottylans@xxxxxxxxx
- Date: 8 Aug 2005 18:03:35 -0700
Greg,
I'm sorry to hassle you like this but I can't find your email anywhere
due to your spam prevention.
Did you ever get a solution for this problem
http://www.mcse.ms/message1756020-1.html
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_frm/thread/3aba16852d34e2f8/1ae3b80c1ddb2e1b?lnk=st&q=30000+NtFrs&rnum=2&hl=en#1ae3b80c1ddb2e1b
NTfrs, 30000 ms problem - and the woman from MS was telling you it's a
hardware error)
Drop me an email (if you can please) - I don't have spam prevention but
gmail blocks it all pretty well anyhow.
Thanks.
- Scott
P.S I'm using a 2.5" USB external caddy for backups on my server - I
thnik this has something to do with it - but I'm not sure.
fingers crossed it's not the hard disks dying (software raid 5 - don't
ask why)...
Gregg Hill wrote:
> 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: Gregg Hill
- 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
- Fresh sbs install needed?
- Prev by Date: Backup to file - something weird is happening!
- Next by Date: Re: "Online Backup"
- Previous by thread: Re: Fresh sbs install needed?
- Next by thread: Re: Fresh sbs install needed?
- Index(es):
Relevant Pages
|
