Re: Configure RWW using Single NIC and Static IP
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Sat, 23 Sep 2006 14:08:13 -0700
Ken,
From the beginning, you used an internal domain name that matches a validexternal name, i.e., cp.com, which belongs to Chicago Pneumatic. Some time
in the future, that **may** cause problems. You should use an internal
domain name with an extension such as .lan or .internal, but not the default
..local because it can cause problems with Macs.
Second, you did not "arrive at the same place as an automated process would
take me" as Lanwench and Leythos pointed out already. You manually created
your users in the wrong place for SBS to work properly.
Gregg Hill
"Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C32143DD-23A8-405A-898B-BFAF7A1EBB54@xxxxxxxxxxxxxxxx
Thanks susan for your input, but really, this isnt the case. Because i
choose
not to use idiot proof wizards, but rather want to configure the system
manually, to arrive at the same place as an automated process would take
me,
is not going to create a cost differential.
And ... if another IT professional should come along down the road, and
NOT
know how to configure the system manually, but ONLY knows how to use
wizards,
they cannot really say they understand the system in its entirety now can
they?
As i said in another reply, while wizards may be great for the novice,
they
should NOT be the only method of configuration.
We have done without them for Decades now, as far back as i can remember,
and i cant see HAVING to use them, with no other choice.
Thank you for the reply
"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
Not to mention it's not fair to this firm to install this SBS so non
standard that any other var/vap coming along will flatten it and
reinstall.
You will cost this firm more money in the long run.
Lanwench [MVP - Exchange] wrote:
In news:92409E96-BBE5-4961-94E7-646E1BD18A32@xxxxxxxxxxxxx,
Ken <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I am in the process of setting up a new SBS Premium Server for a small
organization of 10 users. Currently, I have set up the server
internally with no issues. I manually created the local domain,
(cp.com, which is not there actual external domain name, but just a
short internal only domain name) and added users to AD the way i'm
used to doing it, rather than using the wizards.
You really want to stop doing that. Seriously. Use all the wizards,
even if
you think you know better; SBS is very picky. I myself botched several
installations the first times I played with SBS, and I've been using
Exchange, AD, NT domains, etc for a gazillion years.. Fortunately,
these
were
mainly 'test' machines that didn't matter. So, I learned the hard way
to
cede control to the
wizards.
One thing you likely need to do now is to go to ADUC and move the users
you've
created out of the default Users OU, and into the
MyBusiness\Users\SBSUsers
OU. You are going to have group policy problems if you don't have the
computers, servers, and users in the OUs SBS expects to find them. Also
check the group membership, login script, etc. You can compare them to
the
properties of a test user you create using the wizards.
The Server is not
handling DHCP,
I suggest you change it, so it does. Things will probably work a lot
better
if you let SBS handle it. You can generally configure more options (DNS
domain suffix, WINS, etc) and your dynamic DNS updates will work
better.
Not using exchange
Why not, if I may ask? Exchange is swell.
, no VPN's ... Single NIC and Static
IP.
Veering off topic, but as you've mentioned that you have Premium, I am
wondering why you aren't using ISA - particularly since further along
in
this post, you mention that you have a 'very simple hardware
firewall/router'.
Now i am trying to configure the RWW site.
The company has an external domain name for their website, but i would
rather not involve their hosted website or email accounts yet. I am
not going to configure exchange at this time.
After much reading, i went ahead and tried using the CEICW to set up
the RWW using a Static IP as opposed to an FQDN.
That can work, although it's sure more of a pain for the users to
remember.
Remember, it wouldn't mess up anything in their existing web or mail
hosting
if you were merely to add an A record (something.mydomain.com) and
point it
at the correct public IP. And you won't have to redo it all later.
What i found after running the wizard though, is that local users
could not log on to the local domain.
What errors did you get, and how did you test this? Via RWW, or on the
actual computers themselves? Just enabling RWW from the Internet
certainly
does not do anyting to your users' ability to login to the domain on
their
workstations, so either you
changed something else - or you were testing via remote desktop, and
they
wouldn't have rights to do that by default.
I'm suspecting you didn't add the computers to the domain using the
appropriate wizards, either.....this also makes a big difference.
It removed the users from the
Active Directory users and computers list, and added them to the
Users section in the Server Management window.
No it didn't. What you see in Server Management is a taskpad - and
that's
just a view of the objects in AD, in particular the SBSUsers OU. If you
look
in ADUC I'm sure they are all still where you left them, which is (as
mentioned above) by default not the right OU for them to be in.
So i had to redo all the accounts again, and am now trying to manually
configure RWW without using the wizard.
This is also not a good idea - I fear you are making things worse, my
friend.
I have thus far successfully set up the site, so that when typing in
the IP, the Welcome page appears. this screen has four links;
My Company Web, Network Configuration Wizard, remote Web Workplace
and Help and Support.
I have also successfully remapped the Internal Companyweb site so
that it
can be accessed from the welcome screen, using the instructions from
MS about replacing the companyweb default page entries with the IP
address.
But i cannot get the Remote Web Workplace Link to work,
You mean, "connect to computers" - right?
and i cannot
seem to find any instructions on remapping the RWW with the IP
address manually. All i get is a page cannot be displayed.
Im sure there is a way to configure RWW so that it can be accessed
using https://xxx.xxx.xxx.xxx/remote, but i cannot seem to find the
right config.
I hate to say it, but via the wizards. And something has gone seriously
awry
already.....not sure that re-running the wizards will help, although
you
might be able to reinstall some components and get them back to their
defaults.
The whole configuration is very basic,
It should be, but because you aren't doing things the way the server
expects
to, it is no longer basic.
and i am not
trying to add any VPN's, Im not looking to implement exchange yet,
Why not, if I may ask? It's one of the main benefits of SBS, in my
view.
and they have a simple hardware router/firewall that has been opened
up using all of the appropriate ports listed for RWW.
That's just 4125 and 443.
What am i missing?
Thank you all in advance
I don't mean to sound like the Voice of Doom, but at this point, I
really
think you ought to set up a test machine to play
with - and install SBS a couple of times start to finish using all the
wizards / to do list. You will find life a lot easier if you learn how
to do
this right. I'm not sure what's going on in your server, but without
doing
some more detailed forensic work, it's probably not going to be a piece
of
cake. If
your users are not yet really using this domain (which I presume they
aren't, given that you said you deleted & recreated their accounts), I
suggest you consider
reinstalling from scratch - once you've gotten some test installs under
your
belt. Just my $.02.
.
- References:
- Re: Configure RWW using Single NIC and Static IP
- From: Lanwench [MVP - Exchange]
- Re: Configure RWW using Single NIC and Static IP
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: Configure RWW using Single NIC and Static IP
- From: Ken
- Re: Configure RWW using Single NIC and Static IP
- Prev by Date: Re: Last reply
- Next by Date: Re: Unable to access shared folders from XP to SBS 2003 server
- Previous by thread: Re: Configure RWW using Single NIC and Static IP
- Next by thread: Re: Configure RWW using Single NIC and Static IP
- Index(es):
Relevant Pages
|
