Networks

Ask something
Discussion Locked

Setup 2003 network with Linksys router

0 helpful
13 replies

by jsarinana

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Linksys router BEFSX41. I have a Win2000 Prof. and a Win XP Prof. using it. My ISP is Comcast cable connection. Router is running the defaults: DHCP server and firewall LAN setting is:192.168.2.1 s.m. 255.255.255.0 WAN setting on this router: IP 66.229.10.131 s.m. 255.255.252.0 gateway 66.229.8.1 DNS 204.127.198.19/63.240.76.19.0 I just setup a Win2003 server which got an IP address from the router 192.168.2.103, I then made this 2003 server static: 192.168.2.103 255.255.255.0 gateway 192.168.2.1 DNS 204.127.198.19/63.240.76.19.0 and is Domain server

I took the Win2000 Prof computer and joined the Domain. When I boot/login to domain this computer it takes a long time. I then changed the DNS on the Win2003 server to 192.168.2.103. Still does not help. What am I doing wrong ? need help setting my Domain up with router Help

13 replies

by darts32

The optimal setting should be that your DNS on the workstations are set as follows:

1st = Your local domain controller
2nd = your router (ie 192.168.2.1)
3rd = your ISP's primary domain controller

by jsarinana

Thanks darts32

To confirm, I should add DNS on the clinet computers being:
1st: 192.168.2.103
2nd: 192.168.2.1
3rd: 204.127.198.19
??

1st = Your local domain controller
2nd = your router (ie 192.168.2.1)
3rd = your ISP's primary domain controller

by pgm554

Add 2 things to the network,a second NIC to the 2003 server and a hub/switch to use on the work stations.
Install the 2nd NIC and use it along with the second hub to have the workstations connect through to the primary NIC using the ICS wizard on 2003 server.
Do not use the router to assign IP addresses to the workstations.
Use the DHCP on the W2K3 server,AD is very picky about who assigns IP addresses and how they are trusted.(IE You can't use RIS or PXE without a W2K3 DHCP server)

Check this out and watch for Xtra spaces in the URL

www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03mngd/33_s3ics.mspx

by jsarinana

Thanks darts32 and pgm554

I first tried:
darts32 setting which is one NIC using static and
1st: 192.168.2.103 <-first DNS server's IP
2nd: 192.168.2.1 <-second DNS routers IP
3rd: 204.127.198.19 <- Third DNS router's DNS
and it's working fine now with one issue, if I vpn into work from any of the computers that have joined the domain, I cannot remote to any desktops and if I ping a computer I get a reply but it's a public IP so it does not see the NAT ip's.

I'm going to try two NICs to see if this resolves my issue, to confirm:
1. One NIC will conntect to router from the server 2003 using ICS, I will turn off DHCP on the router. What do I use for IP settings on this NIC ?

2. second NIC on server 2003 using DNS and DHCP will have a reserved IP and static with DNS IP the same as the server's IP, then connected to a switch, switch will connect to PC's on Domain.

any feed back would be appricaited
Thanks

by ewgny

Configure the DNS Settings on your workstations ONLY with the ip address of your Domain Controller. Configure your DC's DNS to forward any requests it can't resolve to your ISP's DNS
You never want workstations to send a DNS query to an external DNS server

by ewgny

Go into DNS. Right click your server - properties
- Forwarders tab - enter the IP of the DNS server you want to forward to.

by jsarinana

Thanks ewgny@hotmail.com
How do you configure DC's DNS to forward any requests it can't resolve to your ISP's DNS ?

This discussion is closed to new replies.