If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Hello Guest,Our records indicate that you have never posted to our site before! Why not make your first post today by saying hello to our community in our Introductions forum.

Please review the forums rules, start with your first post today and become an active part of petri.co.il forums now!

I added an additional DHCP server to cover the class B range and also an additional DNS server to reside on the class B subnet. The dns server was basically setup as a zone transfer from the master DNS server on SRV1.

My problem seems to be, that after startup or restart of a machine we have to wait for upto 80seconds or two failed logins, then we can finally login to the domain.

Or we manage to get a connection first time, but cannot locate the server based profiles.

But once connected speeds and dns resolution are very fast!!

We are connected via both subnets using Cisco 2950 switches connected to our main gigabit router.

Comment

Is the Zone on your primary server an ADI zone or just standard primary zone ?

This error occurs when there are basically 2 copies of the zone floating around your directory partitions, it may just be waiting for replication to occur to rid the old copy, or you may have set it up incorrectly leaving 2 copies around is not good and should be fixed ASAP.

topper

* Shamelessly mentioning "Don't forget to add reputation!"

Comment

Am using AD Intergrated across srv2 and srv1, have added the ptr records for the servers and now across the class C 193.xxx.xxx.xxx subnet machines have no problem resolving the domain and can login into the machines as soon as they start.

On the class B subnet 172.xxx.xxx.xxx, I have now made the default DNS servers that of those on the class C 193.xxx.xxx.xxx SRV1 & SRV2, but the problem still exists, even though all nslookups work perfect!!!