expertclyde
asked on
Event ID Codes 1054, 1053 and 15 causing connectivity problems
Clients Win XP Pro SP 3 Dell Inspiron 530 w/integrated NIC and 4gb RAM, Server Win 2003 for Small Business.
Clients are losing connectivity to Sage Masterbuilder due to the following errors being logged on client's Event Viewer
Userenv, Event 1054
AutoEnrollment, 15
Userenv, Event 1053
Sage is of NO HELP on this issue.
Clients are losing connectivity to Sage Masterbuilder due to the following errors being logged on client's Event Viewer
Userenv, Event 1054
AutoEnrollment, 15
Userenv, Event 1053
Sage is of NO HELP on this issue.
Host Name: FCDC01
OS Name: Microsoft(R) Windows(R) Server 2003 for Small Busines
s Server
OS Version: 5.2.3790 Service Pack 2 Build 3790
OS Manufacturer: Microsoft Corporation
OS Configuration: Primary Domain Controller
OS Build Type: Multiprocessor Free
Registered Owner: admin
Registered Organization: Free Country Design & Construction, Inc.
Product ID: 74995-OEM-4411902-03102
Original Install Date: 7/11/2007, 10:36:25 AM
System Up Time: 13 Days, 22 Hours, 2 Minutes, 40 Seconds
System Manufacturer: HP
System Model: ProLiant ML110 G4
System Type: X86-based PC
Processor(s): 2 Processor(s) Installed.
[01]: x86 Family 6 Model 15 Stepping 2 GenuineIntel ~
1862 Mhz
[02]: x86 Family 6 Model 15 Stepping 2 GenuineIntel ~
1862 Mhz
BIOS Version: HP - 6040000
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (GMT-06:00) Central Time (US & Canada)
Total Physical Memory: 2,046 MB
Available Physical Memory: 1,083 MB
Page File: Max Size: 3,943 MB
Page File: Available: 3,141 MB
Page File: In Use: 802 MB
Page File Location(s): C:\pagefile.sys
Domain: freecountry.local
Logon Server: \\FCDC01
Hotfix(s): 179 Hotfix(s) Installed.
[01]: File 1
[02]: File 1
[03]: File 1
[04]: File 1
[05]: File 1
[06]: File 1
[07]: File 1
[08]: File 1
[09]: File 1
[10]: File 1
[11]: File 1
[12]: File 1
[13]: File 1
[14]: File 1
[15]: File 1
[16]: File 1
[17]: File 1
[18]: File 1
[19]: File 1
[20]: File 1
[21]: File 1
[22]: File 1
[23]: File 1
[24]: File 1
[25]: File 1
[26]: File 1
[27]: File 1
[28]: File 1
[29]: File 1
[30]: File 1
[31]: File 1
[32]: File 1
[33]: File 1
[34]: File 1
[35]: File 1
[36]: File 1
[37]: File 1
[38]: File 1
[39]: File 1
[40]: File 1
[41]: File 1
[42]: File 1
[43]: File 1
[44]: File 1
[45]: File 1
[46]: File 1
[47]: File 1
[48]: File 1
[49]: File 1
[50]: File 1
[51]: File 1
[52]: File 1
[53]: File 1
[54]: File 1
[55]: File 1
[56]: File 1
[57]: File 1
[58]: File 1
[59]: File 1
[60]: File 1
[61]: File 1
[62]: File 1
[63]: File 1
[64]: File 1
[65]: File 1
[66]: File 1
[67]: File 1
[68]: File 1
[69]: File 1
[70]: File 1
[71]: File 1
[72]: File 1
[73]: File 1
[74]: File 1
[75]: File 1
[76]: File 1
[77]: File 1
[78]: File 1
[79]: File 1
[80]: File 1
[81]: Q147222
[82]: KB933854 - QFE
[83]: SP1 - SP
[84]: KB907747 - Update
[85]: KB912442 - Update
[86]: KB916803 - Update
[87]: KB924334 - Update
[88]: KB926666 - Update
[89]: KB931832 - Update
[90]: KB950159 - Update
[91]: KB959897 - Update
[92]: Q927978
[93]: Q936181
[94]: Q954430
[95]: IDNMitigationAPIs - Update
[96]: NLSDownlevelMapping - Update
[97]: KB925398_WMP64
[98]: KB933566-IE7 - Update
[99]: KB937143-IE7 - Update
[100]: KB938127-IE7 - Update
[101]: KB939653-IE7 - Update
[102]: KB944533-IE7 - Update
[103]: KB950759-IE7 - Update
[104]: KB956390-IE7 - Update
[105]: KB961260-IE7 - Update
[106]: KB914961 - Service Pack
[107]: KB921503 - Update
[108]: KB924667-v2 - Update
[109]: KB925902 - Update
[110]: KB926122 - Update
[111]: KB927891 - Update
[112]: KB929123 - Update
[113]: KB930178 - Update
[114]: KB931784 - Update
[115]: KB931836 - Update
[116]: KB932168 - Update
[117]: KB933360 - Update
[118]: KB933566 - Update
[119]: KB933729 - Update
[120]: KB933854 - Update
[121]: KB935839 - Update
[122]: KB935840 - Update
[123]: KB935966 - Update
[124]: KB936021 - Update
[125]: KB936357 - Update
[126]: KB936782 - Update
[127]: KB938464 - Update
[128]: KB938759-v4 - Update
[129]: KB941202 - Update
[130]: KB941568 - Update
[131]: KB941569 - Update
[132]: KB941644 - Update
[133]: KB941672 - Update
[134]: KB941693 - Update
[135]: KB942763 - Update
[136]: KB942830 - Update
[137]: KB942831 - Update
[138]: KB943055 - Update
[139]: KB943460 - Update
[140]: KB943484 - Update
[141]: KB943485 - Update
[142]: KB944653 - Update
[143]: KB945553 - Update
[144]: KB946026 - Update
[145]: KB948496 - Update
[146]: KB948590 - Update
[147]: KB948745 - Update
[148]: KB949014 - Update
[149]: KB950760 - Update
[150]: KB950762 - Update
[151]: KB950974 - Update
[152]: KB951066 - Update
[153]: KB951072-v2 - Update
[154]: KB951698 - Update
[155]: KB951746 - Update
[156]: KB951748 - Update
[157]: KB952069 - Update
[158]: KB952954 - Update
[159]: KB954211 - Update
[160]: KB954600 - Update
[161]: KB955069 - Update
[162]: KB955839 - Update
[163]: KB956391 - Update
[164]: KB956802 - Update
[165]: KB956803 - Update
[166]: KB956841 - Update
[167]: KB957095 - Update
[168]: KB957097 - Update
[169]: KB958644 - Update
[170]: KB958687 - Update
[171]: KB958690 - Update
[172]: KB960225 - Update
[173]: KB960715 - Update
[174]: KB961063 - Update
[175]: KB961064 - Update
[176]: KB961118 - Update
[177]: KB967715 - Update
[178]: KB872769 - Update
[179]: KB954550-v5
Network Card(s): 1 NIC(s) Installed.
[01]: HP NC110T PCIe Gigabit Server Adapter
Connection Name: BottomNIC
DHCP Enabled: No
IP address(es)
[01]: 192.168.1.108ASKER
One problem is:
[WARNING] Cannot find a primary authoritative DNS server for the name
'FCDC01.freecountry.local.
The name 'FCDC01.freecountry.local.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.108'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '65.68.49.50'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
I can't see why the server doesn't register its own IP address in its own DNS ('192.168.1.108'). Of courlse it can't do that in the external one ('65.68.49.50') so this error is normal.
First try on your server in a command prompt:
ipconfig /registerdns
Wait a few moments, then look in the eventlog and check for errors/warnings in DNS, System and Application.
Open the DNS management console and check if the server name is there with the corrrect IP address.
Rerun netdiag /v and dcdiag /v and then run
dcdiag /test:RegisterInDNS >dcdiag2.txt
[WARNING] Cannot find a primary authoritative DNS server for the name
'FCDC01.freecountry.local.
The name 'FCDC01.freecountry.local.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.108'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '65.68.49.50'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
I can't see why the server doesn't register its own IP address in its own DNS ('192.168.1.108'). Of courlse it can't do that in the external one ('65.68.49.50') so this error is normal.
First try on your server in a command prompt:
ipconfig /registerdns
Wait a few moments, then look in the eventlog and check for errors/warnings in DNS, System and Application.
Open the DNS management console and check if the server name is there with the corrrect IP address.
Rerun netdiag /v and dcdiag /v and then run
dcdiag /test:RegisterInDNS >dcdiag2.txt
Also
netdiag /debug /test:dns >netdiag_dns.txt
and maybe
netdiag /fix
can fix your problem
netdiag /debug /test:dns >netdiag_dns.txt
and maybe
netdiag /fix
can fix your problem
ASKER
By the way the router is the DHCP server, not the Win 2003 server.
I'm waiting for the results of the below test.
ipconfig /registerdns
I'm waiting for the results of the below test.
ipconfig /registerdns
ASKER
ASKER
The Event Log showed no errors reported in DNS, System and Application.
In the DNSMGMT console under forward lookup zones main2 there is a WINS lookup of the correct IP of the server.
In the DNSMGMT console under forward lookup zones main2 there is a WINS lookup of the correct IP of the server.
WINS lookup won't help. Youm ust get your DNS working or your problems won't disappear.
if you look at the netdiag-fix.txt you'll see that it tries to register the required DNS records but fails
[WARNING] Cannot find a primary authoritative DNS server for the name\par
'FCDC01.freecountry.local.
The name 'FCDC01.freecountry.local.
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.freecountry.loc
ration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.freecountry.local. re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.free
re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.freec
re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.gc._msdcs.freecountry.lo
iled.\par
Check this KB article http://support.microsoft.com/kb/260371/da/en-us and follow the guidelines for DNS
if you look at the netdiag-fix.txt you'll see that it tries to register the required DNS records but fails
[WARNING] Cannot find a primary authoritative DNS server for the name\par
'FCDC01.freecountry.local.
The name 'FCDC01.freecountry.local.
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.freecountry.loc
ration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.freecountry.local. re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.free
re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.freec
re-registeration on DNS server '192.168.1.108' failed.\par
DNS Error code: DNS_ERROR_RCODE_SERVER_FAI
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-S
s.gc._msdcs.freecountry.lo
iled.\par
Check this KB article http://support.microsoft.com/kb/260371/da/en-us and follow the guidelines for DNS
You should have a forward lookup zone that has the same name as your domain freecountry.local
Also it has to be an active directory integrated DNS
Also it has to be an active directory integrated DNS
ASKER
Should I include the server IP address, 192.168.1.108, in the DNS look up. Or just the DNS entries that AT&T provided?
ASKER
Thanks for the Microsoft KB article. It would appear the article fits our situation...right down to "Some common issues...". However, I noticed the KB article says it applies to
* Microsoft Windows 2000 Server
* Microsoft Windows 2000 Advanced Server
* Microsoft Windows 2000 Datacenter Server
* Microsoft Small Business Server 2000 Standard Edition
but does not include MS Server 2003. Will this matter?
* Microsoft Windows 2000 Server
* Microsoft Windows 2000 Advanced Server
* Microsoft Windows 2000 Datacenter Server
* Microsoft Small Business Server 2000 Standard Edition
but does not include MS Server 2003. Will this matter?
I haven't found a version for 2003, but it seems the same. Maybe some minor differences in the menu selections.
Some important things:
1) Your server's IP config must have its own IP address as primary DNS (according to netdiag it does)
2) Your DNS must be Active Directory Integrated
3) There has to be a forward lookup zone named exactly as your internal AD domain, you may want to create a reverse lookup zone for your subnet.
4) In DNS, enter your ISPs DNS as forwarder so your server can resolve external internet names for your clients
HTH
Some important things:
1) Your server's IP config must have its own IP address as primary DNS (according to netdiag it does)
2) Your DNS must be Active Directory Integrated
3) There has to be a forward lookup zone named exactly as your internal AD domain, you may want to create a reverse lookup zone for your subnet.
4) In DNS, enter your ISPs DNS as forwarder so your server can resolve external internet names for your clients
HTH
ASKER
I'm not sure but I think I got it working.
Could you verify by checking the attached logs?
Can I delete the forward zones of fcdc01.freecountry.local and freecountrydc.com.
If I understand your comment correctly, I did not realize the Forward Lookup Zone name had to be EXACTLY the same as the domain name of the network. In this case, freecountry.local. The way the wizard implies it is the domain name that is found out on the Internet. In this case, freecountrydc.com. However, freecountrydc.com is hosted by Yahoo. You can see where the confusion came from.
I now see after running the netdiag-fix, it has populated freecountry.local Forward Lookup Zone with _msdcs, _sites, _tcp, _udp, DomainDnsZones and ForestDnsZones. I couldn't understand, until now, why the directions, per KB link, had this information. It boiled now to using the wrong name.
dcdiag.txt
NetDiag.txt
netdiag-debug.txt
netdiag-fix.txt
Could you verify by checking the attached logs?
Can I delete the forward zones of fcdc01.freecountry.local and freecountrydc.com.
If I understand your comment correctly, I did not realize the Forward Lookup Zone name had to be EXACTLY the same as the domain name of the network. In this case, freecountry.local. The way the wizard implies it is the domain name that is found out on the Internet. In this case, freecountrydc.com. However, freecountrydc.com is hosted by Yahoo. You can see where the confusion came from.
I now see after running the netdiag-fix, it has populated freecountry.local Forward Lookup Zone with _msdcs, _sites, _tcp, _udp, DomainDnsZones and ForestDnsZones. I couldn't understand, until now, why the directions, per KB link, had this information. It boiled now to using the wrong name.
dcdiag.txt
NetDiag.txt
netdiag-debug.txt
netdiag-fix.txt
ASKER
3) There has to be a forward lookup zone named exactly as your internal AD domain, you may want to create a reverse lookup zone for your subnet.
4) In DNS, enter your ISPs DNS as forwarder so your server can resolve external internet names for your clients
Do I create a new zone? Or do I create a pointer? I'm needing a KB article on how to do #3 and #4.
4) In DNS, enter your ISPs DNS as forwarder so your server can resolve external internet names for your clients
Do I create a new zone? Or do I create a pointer? I'm needing a KB article on how to do #3 and #4.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've attached the updated logs, along with screen shots of the DNS server.
I don't think I got #4 right. I'm not sure what I'm supposed to select when the wizard starts up.
I'm now getting Event ID 6702, aargh!
I'm going back to the client location on Friday. I'm hoping I will not see Userenv, Event 1054
AutoEnrollment, 15; Userenv, Event 1053 in the Event Log of the WinXP client PCs.
netdiag-fix.txt
netdiag-debug.txt
netdiag.txt
dcdiag.txt
Document.doc
three.doc
I don't think I got #4 right. I'm not sure what I'm supposed to select when the wizard starts up.
I'm now getting Event ID 6702, aargh!
I'm going back to the client location on Friday. I'm hoping I will not see Userenv, Event 1054
AutoEnrollment, 15; Userenv, Event 1053 in the Event Log of the WinXP client PCs.
netdiag-fix.txt
netdiag-debug.txt
netdiag.txt
dcdiag.txt
Document.doc
three.doc
Please post the data field of event 6702, it should contain the error code why DNS is unable to update the DNS record. Or did you enter it manually?
The forwarder entries look good you can check by browsing to some internet domains.
The Forward lookup zone looks good
Event 6702 is a bit strange. Its a SBS and you do not have replication partners...
http://www.eventid.net/display.asp?eventid=6702&source=
The forwarder entries look good you can check by browsing to some internet domains.
The Forward lookup zone looks good
Event 6702 is a bit strange. Its a SBS and you do not have replication partners...
http://www.eventid.net/display.asp?eventid=6702&source=
ASKER
Thanks for your help resolving the server DNS mess! Based on your review/comments of the logs, I think the server DNS issue is resolved. With that being said, I'm going to accept the solution.
By the way, based on the URL you sent on Event 6702, I deleted some Host A entries that were competing with the server's IP address for DNS listing.
If you are interested in helping me with some other Event IDs, I'm going to post these client side issues soon on EE.
By the way, based on the URL you sent on Event 6702, I deleted some Host A entries that were competing with the server's IP address for DNS listing.
If you are interested in helping me with some other Event IDs, I'm going to post these client side issues soon on EE.
ASKER
Thanks for your help.
Thanks for the points, expertclyde. I'll try to keep an eye on your questions.
Install the Windows Server 2003 Support Tools on your server and run
dcdiag /v > dcdiag.txt
netdiag /v netdiag.txt
on it and attach the resulting files here.