jwattsit
asked on
XP SP3 Client can logon to server but cannot access some shared folders
On multiple clients running XP, SP3 client I receive this error in event viewer (screen shot attached)
Source: LSASRV
Category: SPNEGO (negotiation)
Event ID: 40961
The Security System could not establish a secured connection with the server ldap/DOHERTY-S1.doherty.lo
I can logon to the domain fine. I can access some of my mapped drives OK. However, other mapped drives or shared folders on server are not accessible.
All permissions on server are correct and have not been changed. My current setup has been working for years and I haven't changed anything that I'm aware of.
Microsoft has a hotfix for SP2, but all clients are on SP3
I have tried:
Resetting user password
Giving user Domain Admin privileges
Creating new shared folders with same name
Removing computer from domain and rejoining
My server is Server 2003. I have Desktop Authority Installed (has always been installed)
Only recent change: Migrated from local exchange server to Google Apps
doherty.PNG
Source: LSASRV
Category: SPNEGO (negotiation)
Event ID: 40961
The Security System could not establish a secured connection with the server ldap/DOHERTY-S1.doherty.lo
I can logon to the domain fine. I can access some of my mapped drives OK. However, other mapped drives or shared folders on server are not accessible.
All permissions on server are correct and have not been changed. My current setup has been working for years and I haven't changed anything that I'm aware of.
Microsoft has a hotfix for SP2, but all clients are on SP3
I have tried:
Resetting user password
Giving user Domain Admin privileges
Creating new shared folders with same name
Removing computer from domain and rejoining
My server is Server 2003. I have Desktop Authority Installed (has always been installed)
Only recent change: Migrated from local exchange server to Google Apps
doherty.PNG
Are all automatic services running on the PC's that are having the problem?
ASKER
All Automatic Services are running
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just a few things to consider:
Is DNS set up correctly? (workstation points only to server, server points to itself)
Here are some links on other EE discussions that are similar:
https://www.experts-exchange.com/questions/22850927/EventID-40961-LSASRV-No-authentication-protocol-was-available.html
This one points to a potential issue with reverse DNS:
http://support.microsoft.com/kb/259922
Is DNS set up correctly? (workstation points only to server, server points to itself)
Here are some links on other EE discussions that are similar:
https://www.experts-exchange.com/questions/22850927/EventID-40961-LSASRV-No-authentication-protocol-was-available.html
This one points to a potential issue with reverse DNS:
http://support.microsoft.com/kb/259922
ASKER
Wow - WinsockFix XP actually resolved the issue.
Can anyone explain what / why this happens?? How to prevent?
Thank You!
Can anyone explain what / why this happens?? How to prevent?
Thank You!
ASKER
UPDATE
winsockxp gave me access to the mapped drive temporarily on one of the computers. Upon rebooting it is still an issue, and running winsockxp does not work again
on the other computers, winsockxp did not work.
Seems that we are back to square 1 and this is still an issue, can I reopen this question?
winsockxp gave me access to the mapped drive temporarily on one of the computers. Upon rebooting it is still an issue, and running winsockxp does not work again
on the other computers, winsockxp did not work.
Seems that we are back to square 1 and this is still an issue, can I reopen this question?
ASKER
I notice that another client is receiving the attached error (Netlogon, no domain available) in event viewer. I removed / added him to the domain and am still having issues.
I have a feeling this is a DNS issue, however I have not made any changes to DNS and have used many troubleshooting steps including the ones in this post
paulc.PNG
I have a feeling this is a DNS issue, however I have not made any changes to DNS and have used many troubleshooting steps including the ones in this post
paulc.PNG
re DNS: What are the workstations using for DNS?
Try:
Start
Run
cmd
ipconfig /all
(copy and post the output here)
exit
It is odd that this problem would appear when there are no changes having been made. Nevertheless, one should check the basics before getting too far into more complicated troubleshooting.
Try:
Start
Run
cmd
ipconfig /all
(copy and post the output here)
exit
It is odd that this problem would appear when there are no changes having been made. Nevertheless, one should check the basics before getting too far into more complicated troubleshooting.
ASKER
The issue was that users were logging on with their username but had an exchange account with different credentials. The workstation was using the exchange credentials to authenticate to the server causing some resources to be restricted.
Thanks for the help!
Thanks for the help!