question

TheWileyOne-9784 avatar image
0 Votes"
TheWileyOne-9784 asked JiaYou-MSFT commented

WSE folder access from non-domain PC

I have a Windows Server 2016 Essentials computer in place named "TheServer" with domain name "TheDomain". All is working well when accessed from a Domain-Joined computer.
Through Server Manager, I've created a shared folder named "Scans" and a user named "TheCopier".
Read/write permission is explicitly given to TheCopier for that folder.
Firewall is turned off for all three zones.

In the Sharp copier, I've added an entry "Scan to server" that points to \\TheServer\scans\ and uses the credentials for Mydomain\TheCopier.
When somebody walks up to the copier and attempts a scan, the result is "Not Authorized" in the log.

When I go to a non-domain-joined computer and enter \\TheServer, I'm asked for credentials so I enter TheDomain\AnAdmin, who is a full domain admin.
Then I get the classic message: "TheServer is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions."

What am I doing wrong?
What else can I try?

windows-server-essentials
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TheWileyOne-9784 avatar image
0 Votes"
TheWileyOne-9784 answered JiaYou-MSFT converted comment to answer

I am able to successfully ping TheServer and it resolves to the correct IP address.
I just need to understand why the server will not allow me to log in using TheDomain\AnAdmin or TheDomain.local\AnAdmin or TheDomain\TheCopier.

Can anybody suggest something I should look at?



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JiaYou-MSFT avatar image
0 Votes"
JiaYou-MSFT answered JiaYou-MSFT edited

HI

1.Which disk did the scan file store, is it disk C?

2.If we access below location on domain joined PC by using "thecopieer" account, will the same issue happen?
\\TheServer\scans\

3.Please add "everyone" for your shared folder "scan",then check if same issue happen on domain joined computer and san printer.

106128-2.png

106129-3.png


4.Please check if the resolution in below document can help you.
Can't access shared folders from File Explorer in Windows 10
https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-access-shared-folder-file-explorer


[1]: /answers/storage/attachments/106010-1.png


============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1.png (142.8 KiB)
2.png (92.6 KiB)
3.png (91.1 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TheWileyOne-9784 avatar image
0 Votes"
TheWileyOne-9784 answered

When accessed from a domain-joined computer, everything works normally.
The group Everyone is already given share and read-write permissions.

Anything else I can try?


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JiaYou-MSFT avatar image
0 Votes"
JiaYou-MSFT answered JiaYou-MSFT edited

HI

For example ,the ip address of wse2016 is 192.168.2.20, if we enter below location in explorer on workgroup pc, will the same issue happen?
\\192.168.2.20\sharedfolder

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TheWileyOne-9784 avatar image
0 Votes"
TheWileyOne-9784 answered WileyWon-3228 commented

I don't understand what you mean by "which disk did the file scan store".
On the server, my C-drive is a small SSD, only for the OS. All data is on the large D-drive.

Yes. The same thing happens when the IP address is used. There are no problems with DNS name resolution.


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HI

1.Did you select "turn on file and printer sharing" and "turn on network discovery" for your guest or public profile like below picture on both wse2016 and none-domain joined PC?

107433-1.png



2.There are other solutions about your error for your reference.

Solved: You might not have permission to use this network resource
https://www.youtube.com/watch?v=9cQc3z107KA

Fix: \\PC Is Not Accessible - You Might Not Have Permission to Use This Network Resource
https://www.youtube.com/watch?v=X2Efu-UCuI0

3.Can you enter below command on wse2016 then export domain policy for this wse2016, is there any setting listed in below 2 items.
gpresult /h c:\wse2016.html

user rights assignment
security options

0 Votes 0 ·
1.png (25.0 KiB)

HI

Is there any progress on your question?

0 Votes 0 ·

Progress? somewhat.
I was able to overcome most of my issues by performing an in-place upgrade to Server 2019 Essentials.
I found it a little strange that the AD and DNS roles were not automatically installed.
I was able to manually add the roles, create a new forest, and promote it to a domain controller, but the same old machine name problem happened again, this time with a different machine name.

And here is where the big kick in the pants happened. After renaming the machine and rebooting, I am no longer able to log in at the console.
I get the classic "The security database of the server does not have a computer account for this workstation trust relationship."

So, now I'm facing a 3-hour drive to execute a Directory Services Restore, or possibly, a full clean install.

Instead of Server 2019 Essentials, might I have better success with 2022 Server Essential Preview?

0 Votes 0 ·
JiaYou-MSFT avatar image
0 Votes"
JiaYou-MSFT answered JiaYou-MSFT commented

HI

So far as I know, in-place upgrade from wse2016 to wse2019(or from wse2019 to wse2022) is not best practice. Migration is always recommended.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Perhaps I might have found your comments useful if I received them in a timely manner.
At this point, it is irrelevant.

0 Votes 0 ·

HI

Thanks for your reply. If you have other issue, we can also post it.

0 Votes 0 ·