Yashy
asked on
Rejected when RDP'ing by IP. Accepted when using FQDN?!
hi guys,
we have a windows 2008 R2 Virtual machine (Vmware).
It's been running fine for ages. However, now when I try to log onto it by RDP with the IP address, it asks me for the domain credentials. When I enter them, I am rejected.
When I do the same thing using the FQDN, it asks me for credentials and when I enter them, I'm in!
Also, when I go to the Vcenter console and log onto the machine using the same credentials, it also works!
In the event id for security, I'm getting the event ID 4625 showing up and something about a NULL SID when I get rejected.
Is it possible, that this machine needs to be taken off the domain. Applied a Newsid (risky?) Rejoined to the domain?
It's a very important server, so I need to sort this out soon.
Thanks for your help:)
Yashy
we have a windows 2008 R2 Virtual machine (Vmware).
It's been running fine for ages. However, now when I try to log onto it by RDP with the IP address, it asks me for the domain credentials. When I enter them, I am rejected.
When I do the same thing using the FQDN, it asks me for credentials and when I enter them, I'm in!
Also, when I go to the Vcenter console and log onto the machine using the same credentials, it also works!
In the event id for security, I'm getting the event ID 4625 showing up and something about a NULL SID when I get rejected.
Is it possible, that this machine needs to be taken off the domain. Applied a Newsid (risky?) Rejoined to the domain?
It's a very important server, so I need to sort this out soon.
Thanks for your help:)
Yashy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm getting this:
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: administrator
Account Domain: FC
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: CAMIT
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: administrator
Account Domain: FC
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: CAMIT
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
ASKER
Nothing has changed in this environment as far as I know.
If we restart the server, we can log onto the server by IP address. Then around one hour later, we are unable to. But then I wonder if there are some services that could be affecting it?
If we restart the server, we can log onto the server by IP address. Then around one hour later, we are unable to. But then I wonder if there are some services that could be affecting it?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hi,
This apparently has been removed.
This apparently has been removed.
Hello,
I have the same problem actually on two physical servers in my Active Directory. It's working fine with all other servers.
Does somebody find anything ?
TIA for answering
I have the same problem actually on two physical servers in my Active Directory. It's working fine with all other servers.
Does somebody find anything ?
TIA for answering
Is this how the Event 4625 Looks?
The event entry that has an Event ID 4625 resembles the following:
Log Name: Security
Source: Microsoft-Windows-Security
Date: date
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: computer name
Description:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: COMPU1$
Account Domain: MYDOMAIN
Logon ID: ID
Logon Type: 7
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0xc0000380
Process Information:
Caller Process ID: 0x384
Caller Process Name: C:\Windows\System32\winlog
Network Information:
Workstation Name: computer name
Source Network Address: IP address
Source Port: 0
Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
if that's the case then it is a "Logon failure" issue nothing to do with SID because if it is a SID issue then AD cannot authenticate you either using IP Address or FQDN,but in our case its working fine with FQDN,So "NULL SID" has nothing to do with this issue.
As you stated that it was working for ages, then what changed in the Environment? after which it stopped working?
Any change at all? in a Physical machine/VM - like windows updates/driver updates etc.