genaccounting
asked on
What are the correct IP & DNS settings for a domain controller with active directory on Windows Server 2008 using Verizon FIOS (small biz)
What are the correct IP & DNS settings for a domain controller with active directory on Windows Server 2008 using Verizon FIOS (small biz)?
When I ping the server, it sees itself on the network, but when I try to set up a workstation to work with the server (in other words, create a LAN), I get this error message:
An Active Directory Domain Controller for the domain "GATSSERVER.GENACCOUNTING.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "GATSSERVER.GENACCOUNTING.
The error was: "DNS server failure."
(error code 0x0000232A RCODE_SERVER_FAILURE)
The query was for the SRV record for _ldap._tcp.dc._msdcs.GATSS
Common causes of this error include the following:
- The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
68.237.161.12
192.168.1.1
- One or more of the following zones contains incorrect delegation:
GATSSERVER.GENACCOUNTING.C
GENACCOUNTING.COM
COM
What needs to be corrected so that I can set up the workstations to work with the server?
The workstations are able to get out to the internet... But they can't join the server's domain.
Please help!
When I ping the server, it sees itself on the network, but when I try to set up a workstation to work with the server (in other words, create a LAN), I get this error message:
An Active Directory Domain Controller for the domain "GATSSERVER.GENACCOUNTING.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "GATSSERVER.GENACCOUNTING.
The error was: "DNS server failure."
(error code 0x0000232A RCODE_SERVER_FAILURE)
The query was for the SRV record for _ldap._tcp.dc._msdcs.GATSS
Common causes of this error include the following:
- The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:
68.237.161.12
192.168.1.1
- One or more of the following zones contains incorrect delegation:
GATSSERVER.GENACCOUNTING.C
GENACCOUNTING.COM
COM
What needs to be corrected so that I can set up the workstations to work with the server?
The workstations are able to get out to the internet... But they can't join the server's domain.
Please help!
ASKER
I'm sorry I don't understand. Is there someone I can call to walk me through this?
Thank you...
Thank you...
It's pretty straight onward just follow my instructions above.
demazter is right on track. If you don't have things set that way, you'll have lots of AD problems.
How do your workstations get their IP addresses? Is it through DHCP or are they individually set? If DHCP, what is the DHCP server? It is common to use the router for DHCP, but probably not a good idea. Inexpensive routers typically don't allow as much configuration as one would like. I much prefer doing DHCP on the file server and disabling it on the router.
If they are getting their IP addresses from static settings, you would go into the network configuration on each workstation and set DNS there to point to the server as demazter suggested.
It would be useful if you went to the server and to a couple of workstations, ran the following, and gave us the results:
start
run
cmd
ipconfig /all
exit
How do your workstations get their IP addresses? Is it through DHCP or are they individually set? If DHCP, what is the DHCP server? It is common to use the router for DHCP, but probably not a good idea. Inexpensive routers typically don't allow as much configuration as one would like. I much prefer doing DHCP on the file server and disabling it on the router.
If they are getting their IP addresses from static settings, you would go into the network configuration on each workstation and set DNS there to point to the server as demazter suggested.
It would be useful if you went to the server and to a couple of workstations, ran the following, and gave us the results:
start
run
cmd
ipconfig /all
exit
ASKER
I tried to but there seems to be info missing. Where are you getting that address for DNS? It's not the DNS that Verizon FIOS provided. Please see the error message I posted.
ASKER
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Angelina>ipconfig
Windows IP Configuration
Host Name . . . . . . . . . . . . : Angelina-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : test.com
Description . . . . . . . . . . . : Intel(R) 82578DC Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 44-87-FC-F6-37-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : 11a/b/g/n Wireless LAN Adapter
Physical Address. . . . . . . . . : C0-CB-38-23-1A-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fd3c:915a:68a1:825d%
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, April 03, 2011 2:37:50 PM
Lease Expires . . . . . . . . . . : Monday, April 04, 2011 2:37:50 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 197184312
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-70-EA-74-C0
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.237.161.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.home:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:107d:178:
rred)
Link-local IPv6 Address . . . . . : fe80::107d:178:b59f:43f1%1
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Users\Angelina>
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Angelina>ipconfig
Windows IP Configuration
Host Name . . . . . . . . . . . . : Angelina-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : test.com
Description . . . . . . . . . . . : Intel(R) 82578DC Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 44-87-FC-F6-37-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : 11a/b/g/n Wireless LAN Adapter
Physical Address. . . . . . . . . : C0-CB-38-23-1A-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fd3c:915a:68a1:825d%
IPv4 Address. . . . . . . . . . . : 192.168.1.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, April 03, 2011 2:37:50 PM
Lease Expires . . . . . . . . . . : Monday, April 04, 2011 2:37:50 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 197184312
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-70-EA-74-C0
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.237.161.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.home:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:107d:178:
rred)
Link-local IPv6 Address . . . . . : fe80::107d:178:b59f:43f1%1
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\Users\Angelina>
ASKER
I can also get any server info you gents might need, just let me know what.
ASKER
Verizon FIOS provided the wireless router.
The HP ProLiant server is connected to the router via cat 5e. The stand-alone workstations are connected to the internet via the router.
Verizon told me my router's IP is 192.168.1.1.
I *had* the server set to 192.168.1.2 but Verizon FIOS tech told me to make everything dynamic.
The genaccounting.com was reserved from 1and1.com, and the URL as well as the primary & secondary DNS have been completed.
The HP ProLiant server is connected to the router via cat 5e. The stand-alone workstations are connected to the internet via the router.
Verizon told me my router's IP is 192.168.1.1.
I *had* the server set to 192.168.1.2 but Verizon FIOS tech told me to make everything dynamic.
The genaccounting.com was reserved from 1and1.com, and the URL as well as the primary & secondary DNS have been completed.
ASKER
Verizon static IP: 74.96.188.14
primary DNS: 68.237.161.12
secondary DNS: 71.252.0.12
default gateway: 74.96.188.1
subnet mask: 255.255.255.0
primary DNS: 68.237.161.12
secondary DNS: 71.252.0.12
default gateway: 74.96.188.1
subnet mask: 255.255.255.0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The server should have its IP address set statically. I like to use .254 for that.
I tend to have workstations use DHCP (with reservations so that the addresses don't change) and have servers set statically. Other devices, such as print servers, should either have static addresses or DHCP with a reservation.
I tend to have workstations use DHCP (with reservations so that the addresses don't change) and have servers set statically. Other devices, such as print servers, should either have static addresses or DHCP with a reservation.
ASKER
That didn't solve my problem with the workstations not being able to join the server's domain (unable to see the server). Maybe I should be pointing the DNS servers to my own server, which is set up as a domain controller; & not Verizon Fio's DNS servers???
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Server should be using only 127.0.0.1 for DNS, no other entries should've present.
The clients should be using the servers IP address for DNS, again, no other entries should be present.
If you find Internet names resolution unreliable then open the DNS management snapin and right cluck on the server name and select properties. Under the forwarders tab add your ISP DNS servers.