Assuming your domain controller is a DNS server also, which it pretty much has to be you NEED to point your client DNS to the DC to process logins. Your clients should use your DC as primary DNS and then your DC will forward (if set up properly) outside DNS requests to the next higher server.
If you don't have your clients set to use your DC as their DNS server, that is certainly your problem.
What Subnet mask are you using?
Ehren J. Benson, MCSE
Windows Systems Administrator
[log in to unmask]
517-884-5469
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On Behalf Of John Valenti
Sent: Friday, June 12, 2009 12:14 PM
To: [log in to unmask]
Subject: [MSUNAG] Netmasks and campus AD setup -- was [MSUNAG] Problem with MSUnet Wireless
Doug & others,
Do you have documents on the proper AD setup, since I seem to be
suffering with an improper setup?
My problems are mostly that the clients don't find the AD to
authenticate logins (unless I point client DNS to the AD server), and
clients don't find printers shared off servers reliably. This seemed
to start after upgrading the domain controller from 2000 to 2008.
I just found out that part of my problem might be with the computer
browser service. That used to be on default, but with Windows 2008 it
is off. I restarted it on the 2008 domain controller, but it is only
seeing two other computers. I think it might be related to having
computers in multiple subnets. I have clients on 35.8.190.x (static),
35.10.64.x & 35.10.69.x (campus dhcp) and 35.15.64.x (restricted to
building access).
thanks for any suggestions!
-John
On May 29, 2009, at 5:57 PM, Doug Nelson wrote:
>
> .......
>
> 1. The local broadcast IP will not be consistent for servers or
> workstations which are in different IP subnets, but are on the same
> local net. This affects some Windows environments, but can generally
> be resolved with a proper Windows AD setup. ....
|
