Solved

Cannot perform network logon from domain servers

Posted on 2006-12-01
5
265 Views
Last Modified: 2008-02-01
We are running Windows Server 2003 SP1. Clients are either Windows XP SP2 or Windows 2000 SP4. I have two accounts that have domain admin rights. When I'm logged in to any server using either of the domain admin accounts I am unable to perform a network logon to any of the client computers. Specifically, when I go to run->\\<computername>\admin$ I get an error that says, " The account is not authorized to log in from this station". When I try to map(i.e. cmd-> net use * \\<comptuername>\admin$) I get system error 1240 - The account is not authorized to log in from this station. However, when I perform the same function but on one of the client computers using the same domain admin accounts it works. I've been through the group policies and didn't see anything out of the ordinary but then again I'm not a group policy expert. I'm hoping someone here can point me in the right direction. Thanks in advance.

James
0
Comment
Question by:gadzooks2
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 26

Accepted Solution

by:
Pber earned 500 total points
ID: 18055437
See this
http://support.microsoft.com/default.aspx/kb/281648

these setting might be different on both machines.

The Digitally sign client/server communications (always) set to enabled usually causes problems.
0
 

Author Comment

by:gadzooks2
ID: 18056568
That worked! Thank you! Thank you! Thank you!

All of the policies in that article(shown below) were enabled and applied to our domain controllers and servers. The funny thing is none of the other admins owed up to changing anything. Is this something that was enabled with SP1? Here are the policies that were enabled. I disabled all of them and the problem went away after the reboot.

Digitally sign client communications (always)
• Digitally sign server communications (always)
• Digitally sign server communications (when possible)
• LAN Manager Authentication Level set to Send LM and NTLM - use NTLMv2 session security if negotiated
• Secure channel: Digitally encrypt or sign secure channel data (always)
• Secure channel: Require strong (Windows 2000 or later) session key
0
 
LVL 26

Expert Comment

by:Pber
ID: 18056679
Glad you got it going.  One thing I hate about this M$ article, they go from maximum security to minimal security to fix a problem.

I would enable these:

Digitally sign server communications (when possible)
Digitally encrypt server communications (when possible)
LAN Manager Authentication Level set to Send LM and NTLM - use NTLMv2 session security if negotiated

In other words, the ones with (always) should be set to disabled as these cause issues.
The ones that have (if server agrees), (if client agrees), (when possible) can be set to enabled if you configure these at both ends(client and server).  This allows for the ability for more secure communication instead of just outright denying it.

Also Require strong session key usually causes problems.  make sure you keep that disabled.

0
 

Author Comment

by:gadzooks2
ID: 18057251
Great! Thanks for the tip. Do you know if Server 2003 SP1 would enable those policies? This is the only thing that has changed in our environment and we didn't have this problem until a couple of days ago. Wierd.

Thanks again for all of your help.
0
 
LVL 26

Expert Comment

by:Pber
ID: 18076296
Possibly.  We have those settings set in a GPO, so if SP1 turned them on, the GPO would have turn them off.
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question