Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hello everyone,
I have recently installed windows server 2003 standard on my PC1 and I wanted to create a domain controller (active directory) for all the other PCs in my network. The only thing is I wanted to keep my server behind my d-link router with all my others PC. Here is a list of all my PCs and there configuration:
D-Link Router
IP = 192.168.0.1
DHCP: PC1 = 192.168.0.100 (static)
PC2 = 192.168.0.101 (static)
PC3 = 192.168.0.102 (static)
PC4 = 192.168.0.103 (static)
MAC Control on all static IPs in the DHCPPC1 Windows Server 2003
IP = 192.168.0.100
DG = 192.168.0.1
DNS = 192.168.0.1PC2 Windows XP Pro SP2
Default settingPC3 Windows XP Pro SP2
Default settingPC4 Windows XP Pro SP2
Default settingAt this point, I have successfully created domain controller with active directory on the server (PC1) and by default a DNS was also created on the server. Furthermore, I have also created a user\password on the server and I have logged that user on PC2.
At this point, I’ve tried to share a folder in PC2 but couldn’t see the domain or any user in the active directory in the security tab for sharing. So I have tried modifying the TCP\IP settings in PC2 to PC4 :
PC2 Windows XP Pro SP2
IP = 192.168.0.101
DG = 192.168.0.1
DNS = 192.168.0.100
Windows Firewall = OFFPC3 Windows XP Pro SP2
IP = 192.168.0.102
DG = 192.168.0.1
DNS = 192.168.0.100
Windows Firewall = OFFPC4 Windows XP Pro SP2
IP = 192.168.0.103
DG = 192.168.0.1
DNS = 192.168.0.100
Windows Firewall = OFFThis has resolved my problem of sharing a folder on the network but it seems extreme.
Can someone tell me if this secure?
Or is there a better way of doing this?
Also what is your opinion of the settings that works?

thanks Trae Barlow but I prefer discussing the problem with someone rather than reading a big document ...

Article did not pertain to your questions either.
Server should not be getting a dhcp ip even if mac filtered. Just do a static ip assignment to it. Router goes down you can still access the server.
You are behind a router. Lan security for you isn't an issue.
It is a requirement of AD and clients that the clients point to the MS AD dns server which you figured out.
You need to configure the MS dns server forwarders tab to include your ISP's dns servers or your pcs won't be able to resolve names on the internet.
Nothing extreme in the share setup. Looks like you are on track.

![]() |
![]() |
![]() |
| Login or Register to Reply | |
| Login | Register |
| Ads by Google |