New server and client install

You should read up on SBS and possibly hire a consultant.  Even if you knew server, you should not be trying to install/manage a small business server network in the same manner.  SBS is VERY reliable when setup properly.  

I have a set of links, mostly provided by EE's SBS guru TechSoEasy available here:
www.lwcomputing.com/tips/static/sbs.asp

In short, you have to ensure DNS is PROPERLY setup and you need to setup the server using the wizards and only the wizards except where there are no wizards (and there are wizards for most things).

Also, especially since this is your first SBS setup - I would recommend installing the server and network at least TWICE before doing a FINAL (third or more) time so that you get used to the procedures for everything.

The DNS I have setup is 192.168.100.100
It is now reading the server but cant get the lisence to run.  I am a tech but not trained in servers and have been thrown into the fire on this one and am not happy about it.  Right now we can access the server and have it configured to make a connection and it even recognizes the server when you do the (http://SERVER/ConnectComputer)  When I click continue and use the login name that is setup on the server it stops flashes and error message then boots me from the installation (all without clicking a button).  I have caught that it doesnt see the username or the computers name within the server management software which is where we setup the user account.  I also made sure that the Computer name for the client matches the computer name on the server under clients.  Not sure if this is helpful.  A consultant really isnt much of an option at this point in time.  I am looking over the site provided and I do thank you I will continue to monitor and keep up to date on this until its completed.  I have installed SBS 3 times now and have the SBS installation down pat thats pretty simple once you have it.  I will see if I can get a copy of the error I will post it that should help

Please post a COMPLETE ipconfig /all from both the SBS as well as the workstation you are trying to join to the domain.

Thanks.

Jeff
TechSoEasy

Server settings:
Windows IP Configuration

Host Name:            OrthoServer
Primary DNS Suffix:      MidwestOrthodontics.local
Node Type:            Unknown
IP Routing Enabled:      Yes
WINS Proxy Enabled:      Yes
DNS Suffix Search List:      MidwestOrthodontics.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix:      
Description:                  HP NC373i Multifunction Gigabity Server Adapter
Physical Address:            00-1E-0B-8E-D8-C2
DHCP Enabled:                  No
IP Address:                  192.168.2.2
Subnet Mask:                  255.255.255.0
Default Gateway:            192.168.2.1
DNS Servers:                  192.168.2.2
Primary WINS Server:            192.168.2.2      

Client:



Windows IP Configuration



        Host Name . . . . . . . . . . . . : Ortho101

        Primary Dns Suffix  . . . . . . . :

        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

        DNS Suffix Search List. . . . . . : MidwestOrthodontics



Ethernet adapter Local Area Connection:



        Connection-specific DNS Suffix  . : MidwestOrthodontics

        Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC

        Physical Address. . . . . . . . . : 00-1D-92-25-43-B6

        Dhcp Enabled. . . . . . . . . . . : No

        IP Address. . . . . . . . . . . . : 192.168.2.3

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . :

        DNS Servers . . . . . . . . . . . : 192.168.100.100

        Primary WINS Server . . . . . . . : 192.168.2.2

Why aren't you using DHCP?

Because on your workstation the DNS Server IP should be 192.168.2.2, and the gateway should be 192.168.2.2 as well, but these things are best handled by allowing DHCP running on your SBS to do the work.

Jeff
TechSoEasy

We are not running on the network that will be installed.  We are physically working at our offices 20 miles from where this will be installed we are preconfiguring and going to run static ip's.  We didnt want it to interfere with the system currently in place on our network which is 192.168.0.1  Would it be best to default that and run it off our system then assign the statics when we install at the place of operation?

No, it would be best to install SBS in its own LAN.  What device is 192.168.2.1?  Because if that's a router, then you have kept things separate.

Jeff
TechSoEasy

Sorry, my bad... if you only have a single NIC in your SBS then the workstation's gateway would be set to 192.168.2.1, not 192.168.2.2 as I stated.  In any event this would have been configured by DHCP if you had allowed it to be.

Jeff
TechSoEasy

Ok what we are going to do is set them to auto.  The router is 2.1 so it should autoconfigure the server and the workstation with the correct ip's in sequence I am assuming correct?  We set the router up manually, which is something I am very confident in, so if we set the workstation and server NIC's to autodetect they should autoconfigure into the same group correct? (Same group being 192.168.2.2, 192.168.2.3, ect)

Yes it is a single NIC in the server

NO, don't have DHCP running from the router, and especially don't let the router autoconfigure the Server.

That's not what I had suggested above.

Jeff
TechSoEasy

The router is preconfigured by us.  We have set hte router as 192.168.2.1 with 255.255.255.0 and 192.168.0.1 as the default gateway.  We didnt let the router DHCP.  I was asking should we set just the server and workstation to auto on the nic settings.  I am sorry I am not trying to be confusing.

Ok here

The router is preconfigured and not set to DHCP
Settings are as follows
IP ADDRESS: 192.168.2.1
Subnet Mask: 255.255.255.0
Gateway: 0.0.0.0 (we preset this at 192.168.0.1 and 192.168.2.1 and it just reset to all 0's but it isnt plugged into a modem with internet access it is pretty much just giving connection between the computers I am using a seperate comp to access this)

Should we (not messing with the router) turn autoconfig on the server and workstation and let them define their own ip's and such?  Kind of like our network which hits the router which sends out the static ip's 192.168.0.17 (this computers IP)

You should NOT set the server's NIC to auto, that's what I'm trying to explain to you.  The workstation SHOULD be set to auto, but only once you've got the DHCP service running on the SBS.  In order to do this you need to have a separate router for this SBS if you are going to set it up on your current network.

Jeff
TechSoEasy

Ok I think I am getting you there.  I know I am confusing myself more than anything more than likely.... a week on this 1 server and probably 25 hours in 2 days (15 consecutive today already).

Here is what we have:


There is a router for the network that we are installing that is completely seperate from the router that we use for our personal network

Tree 1: TR&L (THIS IS US)
Our router
Our computers


Tree 2: Midwest (THIS IS THE SERVER TREE WHICH HAS A SEPERATE ROUTER FROM OUR NETWORK this is for their network and will be installed in their location)
Server
Workstations



The router is setup as I explained before.  We just set the server to host DHCP and the workstation is now set to auto with DHCP enabled... the router DOES NOT have DHCP enabled.  I think we are starting to really understand this.



You really don't understand how much I appreciate this.

I will post what happens after we configure we are going back and going to retry the connection and see if it will run the wizard (http://Server/connectcomputer)

We preset the DNS to be 192.168.100.100 on the server and the Workstation but set the workstation to auto.  Should we set the DNS on the workstation to auto assign?

Here you go.  I drew a picture for you about how this should be configured.

Jeff
TechSoEasy
Setup-Configuration.pdf

Ok so the server is providing the DHCP for the computers comming off the Midwest Router.  As far as I can tell that is how we have it setup this instant (we have made modifications as we are working here).

The server is configured Statically (192.168.2.1) and with DHCP enabled (Hosting DHCP so it assigns a ip to the computers).  The router is configured LAN: 192.168.2.1 and the workstations are configured to autoassign with DHCP enabled.

I had to copy and cut your information to setup paint (sorry no pdf formating for me).  We dont have where you have marked the current router.  Should we have a second router as shown?
Current-Configuration.bmp

I have just been informed that this is how its going to operate.
There will be a switch in there which should be whatever.

Ok not changing much but this is how its going to look
Current-Configuration.bmp

Thanks so much Jeff you are an absolute life saver.  I really do appreciate all of your help.