PDA

View Full Version : Workstation issue, connection with server.


Knightsman
04-12-2011, 12:33 AM
Anyone understand what this is about? I have googled and am so confused. These are not setup to be static IP workstations, could that be the issue?

The Security System could not establish a secured connection with the server cifs/Server******. No authentication protocol was available.

Event ID: 40961

This a constant issue with this workstation. No other workstations have this issue. Thanks for any help.

arrow_runner
04-12-2011, 01:02 AM
Off the top of my head, things to check for:

Remove/readd the computer to the domain(if there is one?)

Reset the firewall and winsock?

Current date

NETWizz
04-12-2011, 01:22 AM
Looks like an authentication problem to a file-share. Is this computer in a domain?

Check the Event Viewer to start!

Have you checked the time-sync with a domain controller that is a member of the Active Directory sites and services?

i.e. Might try a w32tm /resync

Have you checked that other computers work? and/or run dcdiag on a domain controller?

Knightsman
04-12-2011, 01:35 AM
Looks like an authentication problem to a file-share. Is this computer in a domain?

Check the Event Viewer to start!

Have you checked the time-sync with a domain controller that is a member of the Active Directory sites and services?

i.e. Might try a w32tm /resync

Have you checked that other computers work? and/or run dcdiag on a domain controller?

Yes its in a domain, and Im getting huge DNS issues with the server....not sure if this coexists.

This server was never setup right, and the company is always to busy for me to get it right, at least until the summer months. Which is when ill be able to fix these issues. But now this workstation is having "freeze" issues with a share program.

ugh :(


The DNS server encountered a packet addressed to itself on IP address 192.168.0.5. The packet is for the DNS name "_ldap._tcp.a24287fc-5323-44d2-ab64-55d572af68e5.domains._msdcs.mcss.local.". The packet will be discarded. This condition usually indicates a configuration error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints.

Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.

Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record.

You can use the DNS server debug logging facility to track down the cause of this problem.

For more information, see Help and Support Center at