The account is not authorized to log in from this station

[Guest]

When I try to browse or connect to a member server (with Windows Explorer) from my W2K DC I get the following error

\\Server1 is not accessible. The account is not authorized to log in from this station

I can access the server from other servers and workstations

I can also access the server by using the server's IP Address or FQDN \\server1.domain.co

Here is the history that led up to this

Server1 was originally a NT4.0 BDC. I purchased new server hardware, installed W2K SP4, configured as a member server and named the new server Server2

I removed the original Server1 from the domain. I renamed Server2 as Server1, gave it Server1's IP Address, and joined the domain

All the shares on the new Server1 are accessible from all servers and workstations (Win98, WinNT, W2K and XP) except from the Domain Controller

I suspect a disconnect in Active Directory or DNS hasd the DC confused. How do I fix it

 

[David Pharr [MSFT]]

1. Check SMB signing. Specifically, if RequireSecuritySignature is set to
0x1 (enabled) but EnableSecuritySignature is set to 0x0 then the machines
will not talk. Make sure the following registry keys match between client
and server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkStation\Param
eters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters


If one machines requires smb signing but the other does not have it
enabled, the machine that does not have it enabled will not be able to
communicate with the machine that requires it. An explanation of SMB
signing is located within the following article:
823659 Client, Service, and Program Incompatibilities That May Occur When
You
http://support.microsoft.com/?id=823659

2. You could also be encountering the following problem (could be coming
from the a policy other than the local policy):
281648 Error Message: The Account Is Not Authorized to Login from This
Station
http://support.microsoft.com/?id=281648

David Pharr, (e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: The account is not authorized to log in from this station
| thread-index: AcQbX8iVhGoc19HmTYiYRIjXX/zHyg==
| X-Tomcat-NG: microsoft.public.win2000.active_directory
| From: "=?Utf-8?B?YWxhbg==?=" <[email protected]>
| Subject: The account is not authorized to log in from this station
| Date: Mon, 5 Apr 2004 15:46:07 -0700
| Lines: 19
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.win2000.active_directory
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.active_directory:72302
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| When I try to browse or connect to a member server (with Windows
Explorer) from my W2K DC I get the following error:

\\Server1 is not accessible. The account is not authorized to log in from
this station.

I can access the server from other servers and workstations.

I can also access the server by using the server's IP Address or FQDN
\\server1.domain.com

Here is the history that led up to this:

Server1 was originally a NT4.0 BDC. I purchased new server hardware,
installed W2K SP4, configured as a member server and named the new server
Server2.

I removed the original Server1 from the domain. I renamed Server2 as
Server1, gave it Server1's IP Address, and joined the domain.

All the shares on the new Server1 are accessible from all servers and
workstations (Win98, WinNT, W2K and XP) except from the Domain Controller.

I suspect a disconnect in Active Directory or DNS hasd the DC confused.
How do I fix it?


|

 

[Guest]

Thank you for your help. Digitally sign server communications (always) was enabled on the DC and not on the member server. I disabled (default), rebooted, and everything is working fine.