ryanATmatraex
MIS
First, this is a not a production server (YET). It's safe to play around with it and mess things up
.
I have windows server 2003 enterprise that I'd like to setup as a DC. I'm running into what I believe are DNS/DHCP issues.
We have DHCP being hosted from one linux server and DNS being hosted from another linux server. DHCP is on IP: X.147 DNS is on IP: X.133.
I can't ping the FQNS of the domain ie: testpdc.local from the workstations even if I do get them to join the Domain which is a 10 min login process. Even from the DC when I start nslookup I see this
"*** Can't find server name for address 192.168.0.3: Non-existent domain
Default Server: UnKnown
Address: 192.168.0.3"
When it should look like this
"Default Server: server01.testpdc.local
Address: 192.168.100.3"
So I'm wondering a few things.
1. Should I even have the server 2003 setup as a DNS and DHCP server?
2. If I do set it up as a DNS and/or DHCP server what setting do I need in order to point the server to the X.147 & X.133 IP addresses of the right DCHP & DNS servers?
3. What should my TCP/IP settings look like on the server?
4. What should my TCP/IP settings look like on the workstations?
Of course I can't have 2 servers running DNS and DHCP so I'm hoping there is a way to tell the windows server with AD running which servers to use so it can pass the right settings to the work stations & so it can resolve DN's.
I have windows server 2003 enterprise that I'd like to setup as a DC. I'm running into what I believe are DNS/DHCP issues.
We have DHCP being hosted from one linux server and DNS being hosted from another linux server. DHCP is on IP: X.147 DNS is on IP: X.133.
I can't ping the FQNS of the domain ie: testpdc.local from the workstations even if I do get them to join the Domain which is a 10 min login process. Even from the DC when I start nslookup I see this
"*** Can't find server name for address 192.168.0.3: Non-existent domain
Default Server: UnKnown
Address: 192.168.0.3"
When it should look like this
"Default Server: server01.testpdc.local
Address: 192.168.100.3"
So I'm wondering a few things.
1. Should I even have the server 2003 setup as a DNS and DHCP server?
2. If I do set it up as a DNS and/or DHCP server what setting do I need in order to point the server to the X.147 & X.133 IP addresses of the right DCHP & DNS servers?
3. What should my TCP/IP settings look like on the server?
4. What should my TCP/IP settings look like on the workstations?
Of course I can't have 2 servers running DNS and DHCP so I'm hoping there is a way to tell the windows server with AD running which servers to use so it can pass the right settings to the work stations & so it can resolve DN's.