New Users unable to login to WIn2003 based domain.
Hi ,
I have an issue. in our DNS servers whatever the User ID that I have create those users are unable to login to client M/c, In my organization all the client M/c are running in WinXp. DNS server is configured in WIn2003. previously it was working fine. all the users who are already been created can login to domain. But the new users are unable to login to domain. can someone suggest me. here we have two DNS servers. IP is 10.16.1.20 & 21 all are active directory intergrated zone configured. But when i check the zone information in -msdsc zone zore records are not replicatied properly. In .20 SOA record value is 323 & in .21 SOA record is 303. I have applied dnslint command on both servers & founded on .20 everything is fine but in .21 when i tested with IP dns name is not resolved & showing SOA record is missing. But i have applied NSlookup command on .21 its resolving name. SO cant find out what the cause.
Please anyone suggest me how to solve the issue. As new joinees are not able to login to our domain by accessing any client M/c .
Please update me asap.
Thanks,
Biplab
I have an issue. in our DNS servers whatever the User ID that I have create those users are unable to login to client M/c, In my organization all the client M/c are running in WinXp. DNS server is configured in WIn2003. previously it was working fine. all the users who are already been created can login to domain. But the new users are unable to login to domain. can someone suggest me. here we have two DNS servers. IP is 10.16.1.20 & 21 all are active directory intergrated zone configured. But when i check the zone information in -msdsc zone zore records are not replicatied properly. In .20 SOA record value is 323 & in .21 SOA record is 303. I have applied dnslint command on both servers & founded on .20 everything is fine but in .21 when i tested with IP dns name is not resolved & showing SOA record is missing. But i have applied NSlookup command on .21 its resolving name. SO cant find out what the cause.
Please anyone suggest me how to solve the issue. As new joinees are not able to login to our domain by accessing any client M/c .
Please update me asap.
Thanks,
Biplab
Darius Ghassem
Do you have a seperate zone for the msdcs folder? Your msdcs folder should be listed under your domain.com zone and not a seperate zone. If it is then your zone is delegated which means you must manually update the records or you can delete both the msdcs zone and the domain.com zone then recreate the domain.com zone so the msdcs folder will be placed back under the domain.com zone.
ASKER
Yes msdsc folder is listed under domain.com zone in both DNS servers. Just now I have check the replication topology using repadmin CLI utility & also have checked with replication mornitor its showing RPC servers is unavailable. 1722( Error code) ( 10.16.1.21). on .21. i have check on both DNS servers RPC services & FRS services are running. What should I do? under that domain zone there is ( -msdcs, _sites, _tcp, _udp,domaindnszones, -forestdnszones are listed. ) Do you mean I have delete the domain.com zone on both DNS servers & re-created again. ? Plz advise.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Executed but doesnt help anything. I am just enclosing the result of repadmin /showreps result may it will help u to troubleshoot.
C:\Documents and Settings\biplab-a>repadmin
INDIA\K2I-DC-01
DC Options: IS_GC
Site Options: (none)
DC object GUID: 9f05c1ac-aa47-4379-b3cb-7c
DC invocationID: f7e6cb22-80ba-4ba9-ad9f-1d
==== INBOUND NEIGHBORS ==========================
DC=k2,DC=local
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:59 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:47:16.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:03 was successful.
CN=Configuration,DC=k2,DC=
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:24:03.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:02 was successful.
CN=Schema,CN=Configuration
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:38 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:24:03.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:03 was successful.
DC=DomainDnsZones,DC=k2,DC
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
638 consecutive failure(s).
Last success @ 2009-04-03 18:34:32.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:04 was successful.
DC=ForestDnsZones,DC=k2,DC
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
639 consecutive failure(s).
Last success @ 2009-04-03 18:24:04.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:04 was successful.
Source: INDIA\K2I-DC-02
******* 17 CONSECUTIVE FAILURES since 2009-04-30 02:33:47
Last error: 1722 (0x6ba):
The RPC server is unavailable.
C:\Documents and Settings\biplab-a>repadmin
INDIA\K2I-DC-01
DC Options: IS_GC
Site Options: (none)
DC object GUID: 9f05c1ac-aa47-4379-b3cb-7c
DC invocationID: f7e6cb22-80ba-4ba9-ad9f-1d
==== INBOUND NEIGHBORS ==========================
DC=k2,DC=local
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:59 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:47:16.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:03 was successful.
CN=Configuration,DC=k2,DC=
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:24:03.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:02 was successful.
CN=Schema,CN=Configuration
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:38 failed, result 1722 (0x6ba):
The RPC server is unavailable.
638 consecutive failure(s).
Last success @ 2009-04-03 18:24:03.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:03 was successful.
DC=DomainDnsZones,DC=k2,DC
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
638 consecutive failure(s).
Last success @ 2009-04-03 18:34:32.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:04 was successful.
DC=ForestDnsZones,DC=k2,DC
INDIA\K2I-DC-02 via RPC
DC object GUID: 8746a08d-3dfc-408f-a440-e2
Last attempt @ 2009-04-30 06:28:17 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
639 consecutive failure(s).
Last success @ 2009-04-03 18:24:04.
USA\K2C-DC-01 via RPC
DC object GUID: 7f81bb9e-54b4-4a8d-b3e6-64
Last attempt @ 2009-04-30 06:29:04 was successful.
Source: INDIA\K2I-DC-02
******* 17 CONSECUTIVE FAILURES since 2009-04-30 02:33:47
Last error: 1722 (0x6ba):
The RPC server is unavailable.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After executing netdiag LDAP test was failed " its howing [FATAL] Cannot open an LDAP session to K2I-dc-02 AT 10.16.1.21. But while executing netdiag /test:dns all results are passed . DNS test also passed showing meesage" All the DNS entries for DC are registered on DNS servers . But while executing only netdiag command its showing LDAP test faild to 10.16.1.21. even i also execute repadmin /showconn with all DNS servers in India & US its connected accept ( 10.16.1.21) K2I-DC-02 " the RPC server is unavailable"
ASKER
Can anyone help me out about this situation.? Since it has been long time no one has been responded. Please reply back ASAP.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have checked its only issue with 10.16.1.20. This server since not replicated to any of the DC in forest. either in india site or US site. But 10.16.1.21 is replicatiing to all DC in forest.
ASKER
Hi dariusg
I am enclosing the attachment. Please take a look , may it will help you.
Thanks,
Biplab
DNS.JPG
I am enclosing the attachment. Please take a look , may it will help you.
Thanks,
Biplab
DNS.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
really helpfull to troubleshoot the problem