Recommended Posts

ive looked through all the mods that have been done and there is nothing that could really stuff this up, but i found some things on the audit logs on the server

so ive included everything that it has from the login i used to add the account

Event Type: Success Audit

Event Source: Security

Event Category: Logon/Logoff

Event ID: 538

Date:  1/01/2005

Time:  2:50:19 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

User Logoff:

  User Name: jamesas

  Domain:  JHOME

  Logon ID:  (0x0,0x211B42)

  Logon Type: 3

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Account Management

Event ID: 646

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

Computer Account Changed:

  -

  Target Account Name: STINGER$

  Target Domain: JHOME

  Target Account ID: JHOME\STINGER$

  Caller User Name: jamesas

  Caller Domain: JHOME

  Caller Logon ID: (0x0,0x211B42)

  Privileges: -

Changed Attributes:

  Sam Account Name: -

  Display Name: -

  User Principal Name: -

  Home Directory: -

  Home Drive: -

  Script Path: -

  Profile Path: -

  User Workstations: -

  Password Last Set: -

  Account Expires: -

  Primary Group ID: -

  AllowedToDelegateTo: -

  Old UAC Value: 0x80

  New UAC Value: 0x81

  User Account Control:

  Account Disabled

  User Parameters: -

  Sid History: -

  Logon Hours: -

  DNS Host Name: -

  Service Principal Names: -

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Account Management

Event ID: 629

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

User Account Disabled:

  Target Account Name: STINGER$

  Target Domain: JHOME

  Target Account ID: JHOME\STINGER$

  Caller User Name: jamesas

  Caller Domain: JHOME

  Caller Logon ID: (0x0,0x211B42)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Directory Service Access

Event ID: 565

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

Object Open:

  Object Server: Security Account Manager

  Object Type: SAM_DOMAIN

  Object Name: DC=JHOME,DC=ath,DC=cx

  Handle ID: 47271400

  Operation ID: {0,2169795}

  Process ID: 528

  Process Name: C:\WINDOWS\system32\lsass.exe

  Primary User Name: CURLY$

  Primary Domain: JHOME

  Primary Logon ID: (0x0,0x3E7)

  Client User Name: jamesas

  Client Domain: JHOME

  Client Logon ID: (0x0,0x211B42)

  Accesses: DELETE

  READ_CONTROL

  WRITE_DAC

  WRITE_OWNER

  ReadPasswordParameters

  WritePasswordParameters

  ReadOtherParameters

  WriteOtherParameters

  CreateUser

  CreateGlobalGroup

  CreateLocalGroup

  GetLocalGroupMembership

  ListAccounts

 

  Privileges: -

  Properties:

---

domain

DELETE

READ_CONTROL

WRITE_DAC

WRITE_OWNER

ReadPasswordParameters

WritePasswordParameters

ReadOtherParameters

WriteOtherParameters

CreateUser

CreateGlobalGroup

CreateLocalGroup

GetLocalGroupMembership

ListAccounts

  Domain Password & Lockout Policies

  lockOutObservationWindow

  lockoutDuration

  lockoutThreshold

  maxPwdAge

  minPwdAge

  minPwdLength

  pwdHistoryLength

  pwdProperties

  Other Domain Parameters (for use by SAM)

  serverState

  serverRole

  modifiedCount

  uASCompat

  forceLogoff

  domainReplica

  oEMInformation

  Domain Administer Server

  Access Mask: 0

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Logon/Logoff

Event ID: 538

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

User Logoff:

  User Name: jamesas

  Domain:  JHOME

  Logon ID:  (0x0,0x211B8C)

  Logon Type: 3

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Logon/Logoff

Event ID: 540

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

Successful Network Logon:

  User Name: jamesas

  Domain:  JHOME

  Logon ID:  (0x0,0x211B8C)

  Logon Type: 3

  Logon Process: Kerberos

  Authentication Package: Kerberos

  Workstation Name:

  Logon GUID: {b5971aae-3c83-4c93-27a7-551b90b7b6bf}

  Caller User Name: -

  Caller Domain: -

  Caller Logon ID: -

  Caller Process ID: -

  Transited Services: -

  Source Network Address: 192.168.0.21

  Source Port: 1552

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit

Event Source: Security

Event Category: Privilege Use

Event ID: 576

Date:  1/01/2005

Time:  2:50:18 PM

User:  JHOME\jamesas

Computer: CURLY

Description:

Special privileges assigned to new logon:

  User Name: jamesas

  Domain:  JHOME

  Logon ID:  (0x0,0x211B8C)

  Privileges: SeChangeNotifyPrivilege

  SeBackupPrivilege

  SeRestorePrivilege

  SeDebugPrivilege

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Link to comment
https://www.neowin.net/forum/topic/265015-joining-domain/#findComment-585208280
Share on other sites

Is your PC getting DHCP and DNS from the Server. Check on the server to see if the computer has already been created. If so delete it and try to join again. Can you ping the server by IP. Check if you have a firewall on both machines. Cause it seems like it cannot comunicate via RPC. Make sure the RPC services are started on both the server and the workstation.

Have fun!!!

Link to comment
https://www.neowin.net/forum/topic/265015-joining-domain/#findComment-585230558
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!