• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 54
  • Last Modified:

Client access by hostname/FQDN error in Domain environment

I am in the process of cross forest DC migration with an environment of 400 users, first I have configured the GPO to add the dns suffix search domains to the current clients of the old domain however upon applying policy I get The RPC server is unavailable or RPC was cancelled or access denied sometimes.

I have checked the domains (4) health , replication and all looks very well. I checked the DNS as well and there seems to be no issues what so ever.

I connected to one of the clients that has an issue to make sure these clients are joined to the domain and using the proper DNS list. then checked if the domain has the correct hostname as it appears in the domain and everything looked fine.

I disabled Kaspersky firewall on the client and disabled Windows firewall client but still the same issue occur .

When trying to connect to any of these clients with hostname to browse to the C$ folder it gives an error, I also tried with the FQDN and had the same problem but with IP it connects fine.

I checked the RPC service, Computer browser service to see if they are running and they were running.

I am attaching screenshots of the GPO policy and the error that appears when trying to browse to the client folder C$ with hostname or fqdn.

I am out of options and would appreciate if someone could point me to a solution.

thanks
clientaccessbyhostnameerror.jpg
rpc-issue.jpg
0
Mohammed Hamada
Asked:
Mohammed Hamada
  • 6
  • 3
1 Solution
 
chinguettiCommented:
Don't know if you've done it already but try disabling IPv6 and test it again maybe?
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Have you tried ensuring the DNS Suffix is added in advanced tcp ip properties on one of the clients?

By best practice this is usually issued through DHCP option 015.

How many active directory domains in total here? How many domain controllers in each domain?
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
There's two domains (Old.local) and (new.local) the migration is still not in progress due to this problem. In teh old domain there are 4 DCs.

Could you please tell me what do you mean exactly by DNS suffix is added in advanced tcp ip properties?

I am trying to add the dns suffix using the DNS client in the GPO.... the only dns suffix available now is the domain suffix which is the joined domain to the client.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
look in the advanced properties of the network card on one of the machines having the issue you can add a dns suffix in here try adding old.local

as I said above this is usually distributed by DHCP option 15.
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
Yes I can add it to the dns suffix in the nic properties but I have 270 clients that have this issue and I can't go to them one by one to do so.

The main problem is that I can't push any GPO policy to work on these clients. Adding the dns suffix search domain is just a policy that I wanted to apply.
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Can you test whether it works or not that's what im asking.

This is usually pushed out through 015 option in DHCP.
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
Could you please explain what are you asking for is working or not? Are you asking if the GPO is working or not?
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
What I have tried is disabled all the firewalls the user have for test, I have then pointed the computer with the problem to a different DC using the following command

nltest /Server:client0 /SC_RESET:domain.local\DC2

This is not working ... on the GPO it gives RPC was cancelled

We don't involve anything in relation to the DHCP
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
I found the problem, the main issue was caused due to duplicated hostnames on the DNS server. the scavenging features seems to haven't been working since 2013. I am working on fixing it now and hope this will solve the issue.

thanks
0
 
Mohammed HamadaSenior IT ConsultantAuthor Commented:
Self solved
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now