Windows Server 2008 Setup

Hi

I'm setting up a new server this week for our busy little office, we have 20 users and a decent server with raid etc.

It's a simple setup, all we really need is to setup the server as a domain controller, so that users can backup their files, share printers etc.

In the initial Configuration Tasks do i do the following.

Configure networking, static ip 192.168.0.70

We have an adsl linksys router on 192.168.0.2

I need to call the server "Black" and the domain "RED" as that was the names that the last server used before it packed in.

Do i then run the Active Directory Domain Service then DCPROMO

I had SBS 2000 before and all this was taken care off.

Thanks

Hello darkblueo,

Just to get you correct, you will install a new domain without keeping the
old configuration? All user accounts, groups computers and policies you have
to rebuilt/rejoin in the new domain.

Configure the IP like this:
server 192.168.0.70
sm 255.255.255.0
dg 192.168.0.2
dns pref 192.168.0.70

Hi

Yes that's correct.

We're starting from fresh. We are just importing the user data from the old server nothing else.

I just would like it to be easy for users to log in to the same domain with changing anything on the users machine.

Thanks

Well, with creating a new domain, even with the same name, you have to create
everything again. Also the machines have to join the new domain. You can
not prevent this the way you will do it. So the users get new user accounts,
also the existing user folders under "documents and settings" will not be
accessible for them, only an administrator can access the content and then
copy it to the new user profile. For example, if you have user TEST from
the SBS domain and now create a new user TEST on the new domain, on the client
machine you see the old TEST and the TEST.domainname under "documents and
settings".

To keep all the old settings i strongly recommend you to post the upgrade/change/migrate
wish to this NG:
microsoft.public.windows.server.sbs

There are the experts that can give you the best information how to change
from 2000 SBS to 2008 with keeping the domain setup.

Thanks for your reply, I'm only copying over user files like Word and Excel docs etc by and external hard drive. I'll be creating new users accounts and new passwords as some people have left etc.

I was just wondering if there was a guide to setting up Windows 2008 Server for novices :) I'm not too sure how to set it up fom scratch.

Here are some step-by-step guides:
https://www.microsoft.com/downloads/...displaylang=en

http://technet.microsoft.com/en-us/l.../cc755258.aspx

HI

Thanks for the guides, everything is setup but we have a weird problem, the xp workstations are very slow to connect to the domain?

We have a router Netgear router 192.168.2.1

Our setting on the server are:

IP Address: 192.168.50.1
Subnet: 255.255.255.0
Default Gateway. 192.168.2.1

Preferred DNS Server 192.168.2.1

Hello darkblueo,

You have two different subnets configured on one NIC on the server. You have
to change it that way:

IP Address: 192.168.50.10
Subnet: 255.255.255.0
Default Gateway. 192.168.50.1
Preferred DNS Server 192.168.50.10

See the difference with 1 and 10.

or

IP Address: 192.168.2.2
Subnet: 255.255.255.0
Default Gateway. 192.168.2.1
Preferred DNS Server 192.168.2.2

The router should not be used for DNS and also DHCP when a Domain is involved.
The DC is also DNS server and because Active directory relies on functional
DNS use it. Disable all that functionality on the router or if that is not
possible do not use it.

So i assume the clients also have x.x.2.x as ip addresses and the router
for DNS? Change it to meet the DC's requirements for domain access and see
here how to configure DNS for internet access:
http://support.microsoft.com/kb/323380

Excuseme
One question about win server 2008 R2...please helpme

I have a server with one role NMS (network management system).
I have two NICs..one to the network...and one to the client.
The client see the network through the NMS program.
The Networks for the clients is 172.22.41.0
The network to the Network is 192.168.8.0
The NMS program has the IP 192.168.8.10
The first client has the IP 172.22.41.34

I can't see since client the NMS service.
It's necessary routing??
It's Nessesary ARP?
It's neccesary something?

Please helpme

Quote:

---

Originally Posted by luisamaria

Excuseme
One question about win server 2008 R2...please helpme

I have a server with one role NMS (network management system).
I have two NICs..one to the network...and one to the client.
The client see the network through the NMS program.
The Networks for the clients is 172.22.41.0
The network to the Network is 192.168.8.0
The NMS program has the IP 192.168.8.10
The first client has the IP 172.22.41.34

I can't see since client the NMS service.
It's necessary routing??
It's Nessesary ARP?
It's neccesary something?

Please helpme

---

Does your switch and NICs support it, you can do bonding. What make/model is the switch and the NICs? If it's server-class hardware, most of those can do it, using their drivers. Read the documentation for the server NICs and your switch that it plugs into. Have you performed any testing on your environment to determine if LAN throughput actually is at risk of being a bottleneck?

The server is HP:

HP DL160 G6 E5504 HOT PLUG US SVR. Windows Server 2,008.R2, 2 ports GE.

Thanks for your reply

Have you tried to unbind IPv6 from both NICs - unless you use it, get that out of the equation. RRAS would be the way to configure routing between the 2 NICs. You may need to add a route for 0.0.0.0 to give it the gateway of the external NIC. Follow this: http://www.microsoft.com/technet/net...6/ipv6faq.mspx

You'll need to uncheck the protocol then add a registry key. As well, you may need to remove any IPv6 forwarders in DNS if you cannot restart the service.

Dear Expertz

Do you say route add 0.0.0.0 0.0.0.0 172.22.41.34 ??