File Share Write Access Denied to user from one PC
Hello, I have a user that cannot access a file share from one computer. Normally replacing the computer or anything like that would be a fine resolution, but in this scenario I can't. I have however used a backup from a day ago and restored the computer to a previous, 'believed to be working' state. So I am not entirely sure when it started occurring (as I don't know how often the user uses this computer and it still doesn't work), and I don't have that much retention on the device's backup. Either way here is what we have. A domain authenticated user is trying to access \\share\drive\baby\ and save files to the directory. The permissions haven't changed on the share before it stopped working (they had full control before I changed it today but it wasn't working then so I left it on modify as that is my preference), the account isn't locked, the computer hasn't changed, and I can sign into any other computer as this user, and save to the share in question. So I am at a loss on what is going on or what to check next. Here is what I have tried: For giggles, I removed the user's permissions (as they are explicitly defined by user and not designated by groups), and I added them back (as modify though). I also tested adding them to a group, giving the group full control, signing out/in of the computer and trying again. I have removed the computer from the domain, deleted the computer object and added it back, and still no dice. The credentials are not in Windows credential manager for me to clear. Tested from several other PCs as this user and I can edit as needed from them. I have not deleted the account and rebuilt it on the computer, but if there are no other suggestions this is my next step. Here are some visual aids:
DNS for local SOHO, ip ranges and suffixes
Setting up a local DNS on 2019 to eventually become a small AD. IP range used is 192.168.1.1/24 and the number of devices are about 40, including phones and infrastructure and such. I have been reviewing some documentation, but it does not really answer some questions. Gateway is at *.1.1 Server has currently static IP at *.1.51 Can I use an IP from the used range as DNS server or should I use something completely different? I see different answers and references in regards to what local suffix to use, there is an article on MS Tech net advising against using ".local" as local suffix. What goes?
Bitlocker activated on several servers without human action
Hello everyone, We have encountered a problem on several of our servers with different settings. Bitlocker ran on all servers and domain controllers. We can no longer access them without the key. It could be that this was set in the past and that an update and reboot activates Bitlocker? Is it possible from the login page of BitLocker at the server launch, to go through a recovery and get access? Thanks for y
DNS suffix is added when using nslookup but not when using ping or browsing
Hi everyone, I am using Windows Server 2016, running DHCP and DNS. I have configured DHCP option 15 to add suffix "abc.de". In the DNS server, I've created a zone called "corp.abc.de" .Entries in that zone should be resolvable only by hostname. In theory, if I want to ping user.corp , this should be resolved as the FQDN user.corp.abc.de . example: Server config: A record: "user" inside the forwarding Lookup zone "corp.abc.de" Client machine: We run the below command that works nslookup user.corp Server: DC.corp.abc.de Address: 10.130.3.254 Name: user.corp.abc.de Address: 10.150.70.11 Then we rung the below command that should also work, but it doesn't. ping user.corp Ping request could not find host user.corp. Please check the name and try again. This however, works on Linux machines, but doesn't work on Windows or MAC. I've tried reinstalling the server (both with DC AD and without).After spending 2 days on this, I'm out of ideas. Any help will be highly appreciated.RemoteApp Credentials incorrect
We run access to a specific place through Remote App Services, before now the client machine just clicks on the .rdp and presses enter at the credentials screen and they are in. Recently we imposed new passwords on the client machines and since then the credentials for the client on the remote app (should be taking credentials from server) is initially coming up as incorrect, we are able to click on ok and then select user and press enter again and they are in, but this should be ok on initial run. Any ideas on the possible cause?
Shared folders missing
I recently upgraded server 2012 essentials to 2016 essentials. I reformatted the SSD for the OS and did a clean install. After everything booted up I turned the server of and then plugged in the 3 hard drives I had running nder 2012. I cannot see or find any of the folders or files even thogh the hgard drive volumes say they are there. This sounds like a permission issue but I need to know how to recover the old file folders as they had irreplaceble pictures and financial dats in them. Any sugfgestions? Sam
