chrispols
asked on
Win98 losing connection to server every morning???
Hi Everyone,
Problem has just cropped up in the last 7 days. Running Windows 2003 server with Win98 clients (call centre). The problem started with the clients getting an error of "Cannot connect to network drive: Out of system Memory". The event log on the server is :
--------------------------
This computer was not able to set up a secure session with a domain controller in domain HOMEMARK due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------
I have checked the Page file (somewhere on the net said it was that issue). I upgraded to Service pack 1 etc. I have plenty of space on the server, so I don't know why it says "Not enough storage is available to process this command. "
After I reboot the server, it can run fine for the rest of the day, but come around 11pm, I see on the event log that it messes up again, causing people in the morning to have no access.
Any ideas on what is going on with this server? My other 2003 server hasn't needed a reboot in Months, and I don't know what could have changed to cause this.
Thanks a lot,
Chris from South Africa.
Problem has just cropped up in the last 7 days. Running Windows 2003 server with Win98 clients (call centre). The problem started with the clients getting an error of "Cannot connect to network drive: Out of system Memory". The event log on the server is :
--------------------------
This computer was not able to set up a secure session with a domain controller in domain HOMEMARK due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------
I have checked the Page file (somewhere on the net said it was that issue). I upgraded to Service pack 1 etc. I have plenty of space on the server, so I don't know why it says "Not enough storage is available to process this command. "
After I reboot the server, it can run fine for the rest of the day, but come around 11pm, I see on the event log that it messes up again, causing people in the morning to have no access.
Any ideas on what is going on with this server? My other 2003 server hasn't needed a reboot in Months, and I don't know what could have changed to cause this.
Thanks a lot,
Chris from South Africa.
Do the Win98 boxes have the Directory Services client installed?
Also, check the security settings on this server to make sure that NTLM is one of the authentication methods available to you.
You may want to add the DS Client on one machine if you aren't using it - to test if that machine will behave properly once installed.
There is an updated client available - but you need to call MS for it. Given what you are experiencing, you should not have to pay anything for it. Quote the KB number when you call them.
http://support.microsoft.com/default.aspx?scid=kb;en-us;323455
Also, check the security settings on this server to make sure that NTLM is one of the authentication methods available to you.
You may want to add the DS Client on one machine if you aren't using it - to test if that machine will behave properly once installed.
There is an updated client available - but you need to call MS for it. Given what you are experiencing, you should not have to pay anything for it. Quote the KB number when you call them.
http://support.microsoft.com/default.aspx?scid=kb;en-us;323455
ASKER
Hi,
Just got off the phone with M-Soft, will call me back. Thanks for that, i'll install on one machine and see what happens in the morning.
So you're saying is that this intermittent problem could definitely be fixed with this HotFix. Souunds about right from M-Soft.
I'll update you with the findings the next time this machine gives issues.
Thanks,
Chris
Just got off the phone with M-Soft, will call me back. Thanks for that, i'll install on one machine and see what happens in the morning.
So you're saying is that this intermittent problem could definitely be fixed with this HotFix. Souunds about right from M-Soft.
I'll update you with the findings the next time this machine gives issues.
Thanks,
Chris
ASKER
Hi again,
Ok, my security setting for this server is set to "Send NTLM response only" Is that correct? Still waiting for M-Soft to call me back for the Hotfix.
Thanks
Chris
Ok, my security setting for this server is set to "Send NTLM response only" Is that correct? Still waiting for M-Soft to call me back for the Hotfix.
Thanks
Chris
I'm not by a server right now, but you might want to set this to: Send LM & NTLM - use NTLMv2 session security if negotiated
This should cover all the bases.
This should cover all the bases.
ASKER
Hey,
I've just checked the Event Viewer "Application" and the error seen quite a bit is:
--------------------------
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------
Another "Not enough storage is available".. What and why is that happening?
I have loaded 1 DSClient on a 98 machine and am waiting for it to happen again and see if that machine will keep running fine.
Thanks,
crhis
I've just checked the Event Viewer "Application" and the error seen quite a bit is:
--------------------------
Windows cannot determine the user or computer name. (Not enough storage is available to complete this operation. ). Group Policy processing aborted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------
Another "Not enough storage is available".. What and why is that happening?
I have loaded 1 DSClient on a 98 machine and am waiting for it to happen again and see if that machine will keep running fine.
Thanks,
crhis
ASKER
Hi,
Ok, this weekend this machine didn't fair any better.
I changed the authentication to Send LM & NTLM - use NTLMv2. Even the 98 machine with the DSC Client cannot get access. Same errors above in the Application and the System views of Event Viewer.
Not enough storage is available to complete this operation????? I don't get it. plenty of space on all machine.
Help?
Thanks
Chris
Ok, this weekend this machine didn't fair any better.
I changed the authentication to Send LM & NTLM - use NTLMv2. Even the 98 machine with the DSC Client cannot get access. Same errors above in the Application and the System views of Event Viewer.
Not enough storage is available to complete this operation????? I don't get it. plenty of space on all machine.
Help?
Thanks
Chris
This might help:
http://support.microsoft.com/?kbid=280830
Where is your user account located? If you moved it out of the Users container in AD and placed it in an OU try putting it back in the Users container.
http://support.microsoft.com/?kbid=280830
Where is your user account located? If you moved it out of the Users container in AD and placed it in an OU try putting it back in the Users container.
ASKER
Hi,
User account located on the Domain Controller (another 2003 machine) There has been no movements between any user accounts whotsoever. Literally, the machine hasn't been touched for quite a while. Checked Domain Controller, and it has no error at all on it. Clean as a whistle.
I have removed Symantec Corporate edition 9 from this server, as well as added the IRPStack reg. key as documented in other forums.
Have to wait around 5 hours or so for error to occur. Only 3 hours left./ Hopefull it's fixed now.
thanks
Chris
User account located on the Domain Controller (another 2003 machine) There has been no movements between any user accounts whotsoever. Literally, the machine hasn't been touched for quite a while. Checked Domain Controller, and it has no error at all on it. Clean as a whistle.
I have removed Symantec Corporate edition 9 from this server, as well as added the IRPStack reg. key as documented in other forums.
Have to wait around 5 hours or so for error to occur. Only 3 hours left./ Hopefull it's fixed now.
thanks
Chris
ASKER
Hi,
Ok, so far I haven't had this server give issues. (holding thumbs).
Seems like issue was either with the Symantec Antivirus or the Regedit.
Will leave the server the way it is at the moment. If no other problems occur for the next 18 hours, i'll re-install Symantec Antivirus and monitor again.
Will give points once all testing has concluded that it's working fine again.
Thanks
Chris
Ok, so far I haven't had this server give issues. (holding thumbs).
Seems like issue was either with the Symantec Antivirus or the Regedit.
Will leave the server the way it is at the moment. If no other problems occur for the next 18 hours, i'll re-install Symantec Antivirus and monitor again.
Will give points once all testing has concluded that it's working fine again.
Thanks
Chris
ASKER
Hi,
Ok, 5 minutes before leaving work yesterday, error occurred again. So am going to re-install Antivirus.
I'm going to try to disconnect this machine from the Domain and reconnect. Hopefully that will do something.
Any ideas from anyone else?
Thanks
Chris
Ok, 5 minutes before leaving work yesterday, error occurred again. So am going to re-install Antivirus.
I'm going to try to disconnect this machine from the Domain and reconnect. Hopefully that will do something.
Any ideas from anyone else?
Thanks
Chris
ASKER
Well, found an error message on one of the Windows 98 machines that read:
-----------------------
g:\ Not accessible
File System error (2215)
Retry / Abort
-----------------------
So I Googled " Windows 98 File System Error 2215.
Found this link : http://www.chicagotech.net/2003issues.htm
Apparently resolution is:
--------------------------
Windows 2000 Pro or 2003 Server Is Inaccessible from the Domain
Symptoms: When attempting to connect to a Windows 2000 Pro or 2003 server from other computers on the network, you may receive one of the following error messages.
* From a Microsoft Windows NT Server 4.0-based computer, you receive the following error message: Error = There are currently no logon servers available to service the logon request.
* From a Microsoft Windows 98-based computer, you receive the following error message: Error 2215: serverrname is not accessible. The logon server cannot be found
The Windows 2000 Pro or 2003 server is logged on to the domain and can connect to everything else on the network, but Event Viewer shows that the computer cannot contact the domain controller. The Netdiag utility reports that the computer is logged on to the domain through cached credentials.
Resolutions: To resolve this behavior, join the Windows 2000 Pro or 2003 server to a workgroup named WORKGROUP, and then restart the computer. Rejoin the computer to the domain, and then restart the computer again. The computer no longer logs on through cached credentials.
--------------------------
So I have now done this on the server, and will now have to wait to see if it has resolved this issue.
If the issue has not resurfaced by 12:00 South African time tomorrow, then this is what the resolution was. Generally the error surfaced every 7 hours.
Will update when I know it's fixed (or not fixed)
Cheers,
Chris
-----------------------
g:\ Not accessible
File System error (2215)
Retry / Abort
-----------------------
So I Googled " Windows 98 File System Error 2215.
Found this link : http://www.chicagotech.net/2003issues.htm
Apparently resolution is:
--------------------------
Windows 2000 Pro or 2003 Server Is Inaccessible from the Domain
Symptoms: When attempting to connect to a Windows 2000 Pro or 2003 server from other computers on the network, you may receive one of the following error messages.
* From a Microsoft Windows NT Server 4.0-based computer, you receive the following error message: Error = There are currently no logon servers available to service the logon request.
* From a Microsoft Windows 98-based computer, you receive the following error message: Error 2215: serverrname is not accessible. The logon server cannot be found
The Windows 2000 Pro or 2003 server is logged on to the domain and can connect to everything else on the network, but Event Viewer shows that the computer cannot contact the domain controller. The Netdiag utility reports that the computer is logged on to the domain through cached credentials.
Resolutions: To resolve this behavior, join the Windows 2000 Pro or 2003 server to a workgroup named WORKGROUP, and then restart the computer. Rejoin the computer to the domain, and then restart the computer again. The computer no longer logs on through cached credentials.
--------------------------
So I have now done this on the server, and will now have to wait to see if it has resolved this issue.
If the issue has not resurfaced by 12:00 South African time tomorrow, then this is what the resolution was. Generally the error surfaced every 7 hours.
Will update when I know it's fixed (or not fixed)
Cheers,
Chris
ASKER
INCREASED POINTS!!!
Ok, error came back yet again. Forget the previous post as a fix.
Note these times that this problem occurs:
9/12/05 - 6:40
9/12/05 - 11:37
9/12/05 - 16:48
9/12/05 - 20:57
9/13/05 - 6:37
9/13/05 - 11:23
9/13/05 - 16:44
9/13/05 - 23:14
9/14/05 - 6:19
It looks quite suspicious that it occurs every 5 hours or so. NETLOGON, what are you doing?
Can anyone share some ideas?.
Thanks
Chris
Ok, error came back yet again. Forget the previous post as a fix.
Note these times that this problem occurs:
9/12/05 - 6:40
9/12/05 - 11:37
9/12/05 - 16:48
9/12/05 - 20:57
9/13/05 - 6:37
9/13/05 - 11:23
9/13/05 - 16:44
9/13/05 - 23:14
9/14/05 - 6:19
It looks quite suspicious that it occurs every 5 hours or so. NETLOGON, what are you doing?
Can anyone share some ideas?.
Thanks
Chris
ASKER
Points updated as i'm frustrated with this stupid server. Need some fix sometime.
Chris
Chris
ASKER
Hi again,
Maybe this is the solution : http://support.microsoft.com/?id=839880
RPC call issue???
Removed TCP/IP.. restarted, put it back in. restarted. Will see what happens now I suppose.
Chris
Maybe this is the solution : http://support.microsoft.com/?id=839880
RPC call issue???
Removed TCP/IP.. restarted, put it back in. restarted. Will see what happens now I suppose.
Chris
If this fails, run the following two commands from the server at a CMD window. You'll need the Support tools installed from the server CD.
netdiag /v > c:\netdiag.txt
dcdiag /v > c:\dcdiag.txt
Those 2 files will contain information that might help us.
netdiag /v > c:\netdiag.txt
dcdiag /v > c:\dcdiag.txt
Those 2 files will contain information that might help us.
ASKER
I installed the support tools on the CD, but I still cannot run netdiag or dcdiag. Should those tools be on the main Server 2003 Standard CD or on the Server Support tools? Installed both but still nada.
cheers,
Chris
cheers,
Chris
ASKER
Ok, found the Netdiag for windows 2000 (not 2003). And gives me an error of:
The procedure entry point DnsGetPrimaryDomainName_UT
So could be the wrong version of Netdiag.. trying to find the proper version.
The procedure entry point DnsGetPrimaryDomainName_UT
So could be the wrong version of Netdiag.. trying to find the proper version.
ASKER
Ok, I found the NETDIAG.EXE for Server 2003 here:
http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
downloading now, will update with the results asap.
chris
http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
downloading now, will update with the results asap.
chris
ASKER
Hey Netman66,
Ran the netdiag on this server (it's not a PDC so no information for dcdiag).
Read through the huge file and didn't look like anything failed.
What should I be looking for?
Thanks
Chris
Ran the netdiag on this server (it's not a PDC so no information for dcdiag).
Read through the huge file and didn't look like anything failed.
What should I be looking for?
Thanks
Chris
ASKER
Ok, this is quite large, so don't kill me but I did find some problems (I think) on the Domain Controller.
__________________________
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine accounts, is a DC.
* Connecting to directory service on server accounts.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\AC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ACCOUNTS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\AC
Starting test: Replications
* Replications Check
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:56:18.
The last success occurred at 2005-08-23 07:54:49.
535 failures have occurred since the last success.
[SERVER] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Printing RPC Extended Error Info:
Error Record 1, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 1722: The RPC server is unavailable.
Detection location is 323
Error Record 2, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 1237: The operation could not be completed. A retry should be performed.
Detection location is 313
Error Record 3, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 311
NumberOfParameters is 3
Long val: 135
Pointer val: 0
Pointer val: 0
Error Record 4, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 318
The source remains down. Please check the machine.
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: CN=Configuration,DC=homema
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:55:57.
The last success occurred at 2005-08-23 08:02:57.
535 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: DC=homemark,DC=co,DC=za
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:55:36.
The last success occurred at 2005-08-23 08:44:22.
535 failures have occurred since the last success.
The source remains down. Please check the machine.
* Replication Latency Check
REPLICATION-RECEIVED LATENCY WARNING
ACCOUNTS: Current time is 2005-09-14 15:48:14.
CN=Schema,CN=Configuration
Last replication recieved from SERVER at 2005-08-23 07:54:49.
CN=Configuration,DC=homema
Last replication recieved from SERVER at 2005-08-23 08:02:57.
DC=homemark,DC=co,DC=za
Last replication recieved from SERVER at 2005-08-23 08:44:22.
* Replication Site Latency Check
......................... ACCOUNTS passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC ACCOUNTS.
* Security Permissions Check for
DC=ForestDnsZones,DC=homem
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=homem
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=homema
(Configuration,Version 2)
* Security Permissions Check for
DC=homemark,DC=co,DC=za
(Domain,Version 2)
......................... ACCOUNTS passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\ACCOUNTS\netlogon
Verified share \\ACCOUNTS\sysvol
......................... ACCOUNTS passed test NetLogons
Starting test: Advertising
The DC ACCOUNTS is advertising itself as a DC and having a DS.
The DC ACCOUNTS is advertising as an LDAP server
The DC ACCOUNTS is advertising as having a writeable directory
The DC ACCOUNTS is advertising as a Key Distribution Center
The DC ACCOUNTS is advertising as a time server
The DS ACCOUNTS is advertising as a GC.
......................... ACCOUNTS passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Domain Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role PDC Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Rid Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Infrastructure Update Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
......................... ACCOUNTS passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2105 to 1073741823
* accounts.homemark.co.za is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1105 to 1604
* rIDPreviousAllocationPool is 1105 to 1604
* rIDNextRID: 1274
......................... ACCOUNTS passed test RidManager
Starting test: MachineAccount
Checking machine account for DC ACCOUNTS on DC ACCOUNTS.
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/ACCOUNTS
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/ffb248b5-0765-4c31-a
* SPN found :E3514235-4B06-11D1-AB04-0
* SPN found :HOST/accounts.homemark.co
* SPN found :HOST/accounts.homemark.co
* SPN found :HOST/ACCOUNTS
* SPN found :HOST/accounts.homemark.co
* SPN found :GC/accounts.homemark.co.z
......................... ACCOUNTS passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... ACCOUNTS passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
ACCOUNTS is in domain DC=homemark,DC=co,DC=za
Checking for CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Object is up-to-date on all servers.
......................... ACCOUNTS passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... ACCOUNTS passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... ACCOUNTS passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... ACCOUNTS passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... ACCOUNTS passed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
on
CN=ACCOUNTS,CN=Servers,CN=
are correct.
The system object reference (frsComputerReferenceBL)
CN=ACCOUNTS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=homem
and backlink on
CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
The system object reference (serverReferenceBL)
CN=ACCOUNTS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=homem
and backlink on
CN=NTDS Settings,CN=ACCOUNTS,CN=Se
are correct.
......................... ACCOUNTS passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : homemark
Starting test: CrossRefValidation
......................... homemark passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... homemark passed test CheckSDRefDom
Running enterprise tests on : homemark.co.za
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... homemark.co.za passed test Intersite
Starting test: FsmoCheck
GC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
PDC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
Time Server Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
KDC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
......................... homemark.co.za passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
__________________________
This replication issue looks like it started around the same time the problems started occurring. Checked the logs and never had a problem before that date.
So.. question is. what can I do?
Thanks
Chris
__________________________
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine accounts, is a DC.
* Connecting to directory service on server accounts.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\AC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ACCOUNTS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\AC
Starting test: Replications
* Replications Check
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:56:18.
The last success occurred at 2005-08-23 07:54:49.
535 failures have occurred since the last success.
[SERVER] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Printing RPC Extended Error Info:
Error Record 1, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 1722: The RPC server is unavailable.
Detection location is 323
Error Record 2, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 1237: The operation could not be completed. A retry should be performed.
Detection location is 313
Error Record 3, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 311
NumberOfParameters is 3
Long val: 135
Pointer val: 0
Pointer val: 0
Error Record 4, ProcessID is 2284 (DcDiag)
System Time is: 9/14/2005 13:48:35:671
Generating component is 8 (winsock)
Status is 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Detection location is 318
The source remains down. Please check the machine.
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: CN=Configuration,DC=homema
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:55:57.
The last success occurred at 2005-08-23 08:02:57.
535 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,ACCOUNTS] A recent replication attempt failed:
From SERVER to ACCOUNTS
Naming Context: DC=homemark,DC=co,DC=za
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-09-14 14:55:36.
The last success occurred at 2005-08-23 08:44:22.
535 failures have occurred since the last success.
The source remains down. Please check the machine.
* Replication Latency Check
REPLICATION-RECEIVED LATENCY WARNING
ACCOUNTS: Current time is 2005-09-14 15:48:14.
CN=Schema,CN=Configuration
Last replication recieved from SERVER at 2005-08-23 07:54:49.
CN=Configuration,DC=homema
Last replication recieved from SERVER at 2005-08-23 08:02:57.
DC=homemark,DC=co,DC=za
Last replication recieved from SERVER at 2005-08-23 08:44:22.
* Replication Site Latency Check
......................... ACCOUNTS passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC ACCOUNTS.
* Security Permissions Check for
DC=ForestDnsZones,DC=homem
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=homem
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=homema
(Configuration,Version 2)
* Security Permissions Check for
DC=homemark,DC=co,DC=za
(Domain,Version 2)
......................... ACCOUNTS passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\ACCOUNTS\netlogon
Verified share \\ACCOUNTS\sysvol
......................... ACCOUNTS passed test NetLogons
Starting test: Advertising
The DC ACCOUNTS is advertising itself as a DC and having a DS.
The DC ACCOUNTS is advertising as an LDAP server
The DC ACCOUNTS is advertising as having a writeable directory
The DC ACCOUNTS is advertising as a Key Distribution Center
The DC ACCOUNTS is advertising as a time server
The DS ACCOUNTS is advertising as a GC.
......................... ACCOUNTS passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Domain Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role PDC Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Rid Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Role Infrastructure Update Owner = CN=NTDS Settings,CN=ACCOUNTS,CN=Se
......................... ACCOUNTS passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2105 to 1073741823
* accounts.homemark.co.za is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1105 to 1604
* rIDPreviousAllocationPool is 1105 to 1604
* rIDNextRID: 1274
......................... ACCOUNTS passed test RidManager
Starting test: MachineAccount
Checking machine account for DC ACCOUNTS on DC ACCOUNTS.
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/ACCOUNTS
* SPN found :LDAP/accounts.homemark.co
* SPN found :LDAP/ffb248b5-0765-4c31-a
* SPN found :E3514235-4B06-11D1-AB04-0
* SPN found :HOST/accounts.homemark.co
* SPN found :HOST/accounts.homemark.co
* SPN found :HOST/ACCOUNTS
* SPN found :HOST/accounts.homemark.co
* SPN found :GC/accounts.homemark.co.z
......................... ACCOUNTS passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... ACCOUNTS passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
ACCOUNTS is in domain DC=homemark,DC=co,DC=za
Checking for CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=ACCOUNTS,CN=Se
Object is up-to-date on all servers.
......................... ACCOUNTS passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... ACCOUNTS passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... ACCOUNTS passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... ACCOUNTS passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... ACCOUNTS passed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
on
CN=ACCOUNTS,CN=Servers,CN=
are correct.
The system object reference (frsComputerReferenceBL)
CN=ACCOUNTS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=homem
and backlink on
CN=ACCOUNTS,OU=Domain Controllers,DC=homemark,DC
The system object reference (serverReferenceBL)
CN=ACCOUNTS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=homem
and backlink on
CN=NTDS Settings,CN=ACCOUNTS,CN=Se
are correct.
......................... ACCOUNTS passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : homemark
Starting test: CrossRefValidation
......................... homemark passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... homemark passed test CheckSDRefDom
Running enterprise tests on : homemark.co.za
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... homemark.co.za passed test Intersite
Starting test: FsmoCheck
GC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
PDC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
Time Server Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
KDC Name: \\accounts.homemark.co.za
Locator Flags: 0xe00003fd
......................... homemark.co.za passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
__________________________
This replication issue looks like it started around the same time the problems started occurring. Checked the logs and never had a problem before that date.
So.. question is. what can I do?
Thanks
Chris
ASKER
Ok, something else that's funny.
I'm running a server 2003 machine as well. So there are 3 in total on-site. When I run:
portqry -n servername -o 135
I get the normal response.
I run the same command from the Domain Controller, and I get a normal response.
When I run it from the problem computer, I get this error:
"Error opening Socket: 10055
An unspecified winsock error has been encountered"
I'm pretty sure that cannot be right.
I'm running a server 2003 machine as well. So there are 3 in total on-site. When I run:
portqry -n servername -o 135
I get the normal response.
I run the same command from the Domain Controller, and I get a normal response.
When I run it from the problem computer, I get this error:
"Error opening Socket: 10055
An unspecified winsock error has been encountered"
I'm pretty sure that cannot be right.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, after a reboot, that winsock error goes away. After 5 hours though, it comes back. So maybe I should just re-install 2003 over this?
ASKER
Hi,
Well, I decided to format the server and re-install the entire stupid thing. All seems to be working so far. Not one error on either PDC or this machine.
So, i'm not going to say it's fixed yet, so will update this tomorrow. Hopefully someone at the office won't be calling me at 6am to fix the problem again.
Cheers,
chris
Well, I decided to format the server and re-install the entire stupid thing. All seems to be working so far. Not one error on either PDC or this machine.
So, i'm not going to say it's fixed yet, so will update this tomorrow. Hopefully someone at the office won't be calling me at 6am to fix the problem again.
Cheers,
chris
It sounds like Winsock was the issue, but something continued to corrupt it after each fix.
Too bad we couldn't nail this down - but, I understand that time was a factor to getting this production box working correctly.
Keep us posted.
Too bad we couldn't nail this down - but, I understand that time was a factor to getting this production box working correctly.
Keep us posted.
ASKER
Hey Netman,
Well, I wish we could have resolved the issue in the end, but it seems that it's now working 100% No early morning calls, everyones happy. But because you helped so much, you get the points. Thanks a lot!!
Chris
Well, I wish we could have resolved the issue in the end, but it seems that it's now working 100% No early morning calls, everyones happy. But because you helped so much, you get the points. Thanks a lot!!
Chris
Excellent! Thanks for the update and the points.
Cheers,
NM
Cheers,
NM
ASKER
Thanks
Chris