Active Directory Services (DHCP, DNS, ADS and LinkSys)

[slurpyx]

Here's the variable:

i have a linksys wireless-g router. the current setup is simple the linksys will feed/share evryone on the network with internet access (dhcp).

now my boss wants me create a server in which evrybody can log in (secured sharing) and centralize all the files.

my problem/solution is to fire up a windows 2000 advance server and enable/configure ads.

i use the wizard and read some tech docs... says that i need to configure dhcp and dns before i install ads.

question # 1: do i need to manage and authorize my linksys router (10.x.x.1) and if so.. my win2k server says "Access Denied"

question # 2: am i doing this all wrong!? am just a newbie.


tnx.

 

[jaksen112]

1. you dont need advaned server, plain vanilla 2000 server will do, depending on the size of your network, you could probably setup a workstation to share your files (workgroup)

if you did go with server, AD install sets up dns for you During setup.

01110000

 

[slurpyx]

workgroup wouldnt do the trick for us anymore. i need login accounts, group policy and all that bla bla bla..

basically i just want a user when loged on to my server i just want a drive to be map for him/her..

so if i want to roll out ADS its just ADS and DNS. nothing more? so there would be no conflict with my ad server and my router? right?

 

[wbg34]

Slurpyx,
You can either disable dhcp on your wireless router and then set it up on the Win2k server or you can let your router handle the dhcp and only set up dns on the win2k server. The simplest way is to just set up your AD and don't worry about DHCP. Make sure your server has a static IP though.

 

[slurpyx]

ok. hmm. ok.. i will make it simple.. (Stupid Me!)

now.. how do i map a drive? thru profile... like UNC format \\ and all that? how about the login script? is the maping of the drive will work on all version of windows. xp, 2k, me, 98?

sowee guys.. am used to the novell thing.. i havnt playd with network since novell 4.somthing..

 

[slurpyx]

Where does the home folder of the users reside?

 

[swabs]

I would recommend setting up home folders for each user (located in Active Directory Users and computers in the profile properties tab)
Or you can use a logon script for users. Create a notepad file that has
net use z: \\servername\%username%
#used to create home
net use y: \\servername\sales #used to map to sales folder
net use x: \\servername\accounting
#mapped to shared accouting folder

Save that file as logon.bat in the \\domaincontroller\netlogon directory

then use group policy to apply that logon script to the users.

 

[slurpyx]

OK.. 1 more question.. am just using an up link to my linksys router that uplink connected to a hub attached to the hub is win2k server with ads.

my xp computers attached to the same hub is seeing the DC (win2k with ads) but the other computers outside that hub cant see my dc (other computers also connected via the linksys thru a diff hub) my 2k computers (thru a diff hub) is saying that "DNS Error something... cant see the domain"

is there a problem on my dns configuration? how can i check if i did the configuration right?

tnx..

 

[slurpyx]

And another thing.. on my DC server with ADS, should i point my PDNS to my on IP Address.

like this:
IP Address: 10.0.1.25
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.1.1

Preferred DNS: 10.0.1.25
Alternate DNS: I leave it blank.

Is this right?

 

[Treyze]

I'm going to chime in here.

Slurpyx.

1. Set up a win2k/Srv (adv or std) doesn't matter.
2. Set up AD services on the Svr w/DNS
3. Set up wins, even though not needed for a Win2k/svr AD, it helps resolve win9x issues of finding other win9x machines on the domain.
3. Set up DHCP services w/Scope. make sure you configure options
- 003 Router (your linksys)
- 006 DNS services (your win2k/svr's address)
- 015 DNS domain name (what you named your dns zone)
ex. corp.companyname.com
- 044 Wins/NBNS server (Wins Server - essential for win9x
machines) (also you win2k/svr address)
- 046 Wins/NBT node type 0x8
4. add all the machines to the domain
This allows your everyone to have a central account for secured and centralized sharing.
5. Create share folders on the server.
6. If you want, you can setup scripts for sharing. This makes life easier.

here is a script that I use... it comes w/ printer mapping if you choose to add a network or LPT printer to the server. if not. delete the printer section of the script.


:START
if not "%OS%" == "Windows_NT" goto EOF
set LogonDir=%logonserver%\netlogon
set HomeDir=\\svr\Home /yes
set UserDir=\\svr\Home\%USERNAME% /yes
set GroupDir=\\svr\Group /yes
set PublicDir=\\svr\Pub /yes

rem net time %logonserver% /set /yes

riveMap
%LogonDir%\ifmember "Domain Users"
if not errorlevel 1 goto EOF
net use H: %HomeDir%
net Use P: %PublicDir%
net use G: %GroupDir%
net use U: %UserDir%

rinterMap
%LogonDir%\ifmember "Domain Users"
if not errorlevel 1 goto EOF
%LogonDir%\adprintx /c \\svr\printer1
%LogonDir%\adprintx /c \\svr\printer2

:EOF
EXIT

The linksys does a good job as a dhcp server but it lacks the ability to resolve DNS correctly. This is why you can only see some machines on your domain. I recommend you use DHCP on your win2k/svr with the settings above.

my $.02

 

[slurpyx]

wow tnx. for the replies...

is it an absolute must that my pdc server will have a STATIC IP Address?

tnx.. i know that lots of "newbies" will benifit from this thread..

 

[slurpyx]

i tried using:

net use x: \\domainname\sharedfolder

on my server but its saying "network path not found"

what is wrong? am just testing it before i tried on client computers..

 

[slurpyx]

How would i know if i got this right?