After you make your changes to your DHCP, you should be able to use
ipconfig /release
ipconfig /renew
on your clients. This will first release DHCP lease and it will request new
IP address from the DHCP with other options set.
Again, you clients must point to Active Directory DNS or they will fail (or
take a long time) to locate DC, GC and other roles needed to work in domain
environment. To check you can run this on your client PC from Start -> Run
option:
cmd /k "ipconfig /all | find "DNS Servers"
and make sure that DNS Server point to your Active Directory DNS server.
Mike
"Sri" <(E-Mail Removed)> wrote in message
news:473D5D38-DA23-4189-9D09-(E-Mail Removed)...
> Thanks Mike, my AD server is also a DNS server.
>
> I have everything else performed correctly as you mentioned except the
> local
> DNS server's IP address was not included in my dhcp leases.
>
> I made some changes to the PIX, so far don't see any differenct. Will wait
> till tomorrow to see after the dhcp lease has been renewed.
>
> Thanks for your time.
>
> -Sri
>
>
> "Miha Pihler" wrote:
>
>> Hi,
>>
>> How is your DNS setup? Is your Active Directory server also a DNS server?
>>
>> Clients will use DNS service to locate DC servers. Make sure that your
>> clients point to Active Directory DNS server. This is the only DNS server
>> that knows something about your internal domain resources.
>>
>> Your PIX is probably serving DNS IP of your ISP. Reconfigure it in a way
>> to
>> give out DNS server of your Active Directory domain.
>>
>> How did you configure your Windows 2003 AD under TCP/IP? Where does
>> preferred DNS point to? If you AD is also DNS server it should point back
>> to
>> himself (you can e.g. enter 127.0.0.1). If you make any changed to
>> preferred
>> DNS on your DC restart the NetLogon service.
>>
>> On your AD DNS server open DNS MMC and right click on server name in MMC.
>> Click on Forwarders tab and enter your ISP's DNS server. This will enable
>> your clients to resolve resources on the Internet since they will only
>> know
>> about your internal DNS server.
>>
>> I hope this helps,
>>
>> Mike
>>
>> "Sri" <(E-Mail Removed)> wrote in message
>> news:6BC3B8DC-8028-48C8-90F4-(E-Mail Removed)...
>> >I setup a W2K3 standard server as DC on AD. I have PIX firewall
>> >performing
>> > DHCP. Everything works fine, but very very slow on all computers logged
>> > into
>> > the domain.
>> >
>> > If I login to a local computer (XP,W2K) by avoiding domain login,
>> > everything
>> > is normal, super fast.
>> >
>> > The DC is setup with default settings, just servers file, no heavy
>> > processing like database or exchange.
>> >
>> > I tried applying MS hotfix, still it is extremely sloooow.
>> >
>> > Any suggestions?? Could it be that I am performing dhcp on a PIX and
>> > Windows
>> > is unable to resolve DNS query in timely manner???
>> >
>> > Any pointers????
>> >
>> > Thanks in advance.
>> > -Sri
>>
>>
>>
|
Similar Threads
Linear Mode
