Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 789
  • Last Modified:

DFS FQDN??

I have an AD domain, in the login scripts  I reference the NETLOGON directory via "\\DOMAIN.Local\NETLOGON".  Our users also access the DFS files this way "\\DOMAIN.Local\DFS Name\"

Our users are experiencing long delays when logging in and when access DFS files.

In looking around I see that when you try to ping DOMAIN.Local it responds with an IP.

First how is this IP assigned?  At the moment it's assigned to an IP address assigned with DHCP and is not valid.

Anyone have any suggestions as to how I can correct this, not sure if the IP has anything to do with it or not.

Thanks in Advance.
0
ARSCO
Asked:
ARSCO
  • 5
  • 4
1 Solution
 
Darius GhassemCommented:
The IP of the domain controller and DNS should be static.
0
 
ARSCOAuthor Commented:
They are and always have been.
0
 
Darius GhassemCommented:
When you ping the domain the address comes from the server holding the FSMO PDC emulator for the domain.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ARSCOAuthor Commented:
The ping request returns with 192.168.10.11 which at one time was the PDC of our 2000 Domain.  A long time ago we switch to a 2003 domain and 10.24 and 10.25 are our current DC's.   With 10.24 being the one that's the FSMO PDC.

Correction, the domain IP is not a DHCP assigned IP.  I was thinking about another question I had asked.
0
 
Darius GhassemCommented:
Have you checked in DNS to see if you see any old records with the 192.168.10.11
0
 
ARSCOAuthor Commented:
Ok in playing some more.  If I do a ipconfig /flushdns and then ping DOMAIN.Local I get a different IP, 10.42 which also used to be a DC.  I flushed it again and I got 10.24 as the ping response.

So obviously there's a list of DC's somewhere which isn't valid any more.  All the DC's demoted properly when taken out of service, they were 2000 servers.

Users are experiencing delays because they have to wait to get a DC that responds.

Any ideas where I can go to fix list list?
0
 
ARSCOAuthor Commented:
Ok in looking in DNS...

There were a bunch of (same as parent folder) entries for IPs that shouldn't be there.  I removed all them (leaving only the two authorized DNS servers) and things have settled down.  Now to wait and see if the list is repopulated for some reason.
0
 
Darius GhassemCommented:
Look in DNS find your DomainDNSZones to view the current IP addresses. Also, right-click your server in DNS then click Update Server data files. Right-click your server again then Scavenge Stale Resource records. Do you have any errors on your servers about the Naming Browser. Do you have WINS setup?
0
 
Darius GhassemCommented:
I'm surprise you didn't have more problems then you have had.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now