Re: Server 2019 - Active Directory
Okay, boys and girls, it's getting scary out there in server land. lol
I was at the school last night trying to figure it out. I logged on another PC under this users name and I could access all the files thru the run command. I logged back on the PC in the user's office and I couldn't access all the files. Specifically, I couldn't access documents and desktop in the FolderRedirect File. But only on that one PC.
It got even more confusing for me when I went back to the run command and accessessed the server via IP address. When I did that, I could access all the files.
In other words, when I tried to access the files like this: \\DC-01\FolderRedirect\documents - couldn't access.
When I tried to access the files like this: \\192.168.0.155, I could acess everything.
This was all very confusing to me. It was only a problem on this one PC but I could acess the files via IP address to the server.
When I ran a nslookup for DC-01, the results were correct.
When I ran gpupdate /force, it showed the expected results.
Out of curiousity, I unlinked the GPO and that caused a major problem on his PC as the desktop was now empty and I was blocked from putting anything on the desktop.
I then noticed that NetBios over TCP/IP was on. I turned it off and ran gpupdate from the server and PC and everything worked again. The error message was now gone and everything worked as it should. Whew!!!
I was kinda freaking out because it was so confusing. I hope that's all it was. I quit while I was ahead.
Okay, boys and girls, it's getting scary out there in server land. lol
I was at the school last night trying to figure it out. I logged on another PC under this users name and I could access all the files thru the run command. I logged back on the PC in the user's office and I couldn't access all the files. Specifically, I couldn't access documents and desktop in the FolderRedirect File. But only on that one PC.
It got even more confusing for me when I went back to the run command and accessessed the server via IP address. When I did that, I could access all the files.
In other words, when I tried to access the files like this: \\DC-01\FolderRedirect\documents - couldn't access.
When I tried to access the files like this: \\192.168.0.155, I could acess everything.
This was all very confusing to me. It was only a problem on this one PC but I could acess the files via IP address to the server.
When I ran a nslookup for DC-01, the results were correct.
When I ran gpupdate /force, it showed the expected results.
Out of curiousity, I unlinked the GPO and that caused a major problem on his PC as the desktop was now empty and I was blocked from putting anything on the desktop.
I then noticed that NetBios over TCP/IP was on. I turned it off and ran gpupdate from the server and PC and everything worked again. The error message was now gone and everything worked as it should. Whew!!!
I was kinda freaking out because it was so confusing. I hope that's all it was. I quit while I was ahead.

Comment