F5F Stay Refreshed Power Users Networks Organize file access settings for network locations.

Organize file access settings for network locations.

Organize file access settings for network locations.

Pages (2): 1 2 Next
S
sebasdoce
Member
245
07-29-2016, 09:28 AM
#1
I updated my xpenology setup (Synology) NAS and successfully installed games on the network drive. Steam and Epic Games both worked without issues. Ubisoft Connect blocked Origin and Oculus Home from installing, claiming permission errors for the network folder. I checked the mapped drive properties but found it restricted—only server users or groups could be added, not my PC. The location is locked. Is there a method to modify this setting so my PC can manage groups? Or any tips for installing Oculus and Origin on a NAS?
S
sebasdoce
07-29-2016, 09:28 AM #1

I updated my xpenology setup (Synology) NAS and successfully installed games on the network drive. Steam and Epic Games both worked without issues. Ubisoft Connect blocked Origin and Oculus Home from installing, claiming permission errors for the network folder. I checked the mapped drive properties but found it restricted—only server users or groups could be added, not my PC. The location is locked. Is there a method to modify this setting so my PC can manage groups? Or any tips for installing Oculus and Origin on a NAS?

M
Maddles
Junior Member
10
08-13-2016, 09:03 PM
#2
You might set up a local account on the server using the same username and password as your PC, then give it the necessary access rights. After that, your computer should be able to connect without needing a password, and the shared resources should reflect the correct permissions.
M
Maddles
08-13-2016, 09:03 PM #2

You might set up a local account on the server using the same username and password as your PC, then give it the necessary access rights. After that, your computer should be able to connect without needing a password, and the shared resources should reflect the correct permissions.

M
193
08-15-2016, 10:01 PM
#3
It indicates a special configuration setting is active, typically triggered when the device cannot obtain an IP address through its local DHCP server.
M
Minemanhpminer
08-15-2016, 10:01 PM #3

It indicates a special configuration setting is active, typically triggered when the device cannot obtain an IP address through its local DHCP server.

R
rbesfe
Junior Member
26
08-16-2016, 05:20 AM
#4
R
rbesfe
08-16-2016, 05:20 AM #4

T
Tange
Junior Member
12
08-19-2016, 01:00 PM
#5
Yes, a direct link between PC and Server works well. In the UK with Virgin Media, their router performs poorly—transfer speeds dropped from 100MB/s to just 30MB/s. I tried rebooting and resetting factory settings, but the cap remained at 30MB/s. To regain full performance, I opted for a direct connection, taking advantage of the two LAN ports on the server.
T
Tange
08-19-2016, 01:00 PM #5

Yes, a direct link between PC and Server works well. In the UK with Virgin Media, their router performs poorly—transfer speeds dropped from 100MB/s to just 30MB/s. I tried rebooting and resetting factory settings, but the cap remained at 30MB/s. To regain full performance, I opted for a direct connection, taking advantage of the two LAN ports on the server.

I
IAMaShark
Junior Member
21
09-08-2016, 02:40 PM
#6
Setting fixed IP addresses within standard ranges like 192.*.*.* or 10.*.*.* for both NICs is feasible. It might be happening because SMB is misbehaving with the 169.*.*.* port assigned differently.
I
IAMaShark
09-08-2016, 02:40 PM #6

Setting fixed IP addresses within standard ranges like 192.*.*.* or 10.*.*.* for both NICs is feasible. It might be happening because SMB is misbehaving with the 169.*.*.* port assigned differently.

X
xXSuperNovaXx
Posting Freak
811
09-09-2016, 05:27 PM
#7
I connected the server via the LAN port linked to your router, resulting in the drive receiving the IP address 192.168.0.20. The same issue persists, with permission problems reported.
X
xXSuperNovaXx
09-09-2016, 05:27 PM #7

I connected the server via the LAN port linked to your router, resulting in the drive receiving the IP address 192.168.0.20. The same issue persists, with permission problems reported.

A
52
09-14-2016, 10:52 AM
#8
It was a risk, but at least it was tried.
A
Agentfreddyboy
09-14-2016, 10:52 AM #8

It was a risk, but at least it was tried.

S
SandraRos
Junior Member
16
09-14-2016, 11:38 AM
#9
Have you explored this @bigo93?
S
SandraRos
09-14-2016, 11:38 AM #9

Have you explored this @bigo93?

E
eastland97
Senior Member
644
09-23-2016, 02:58 AM
#10
Even with identical usernames, the device names differ, preventing a connection between them. It might be worth a shot, though I’m really skeptical it will succeed.
E
eastland97
09-23-2016, 02:58 AM #10

Even with identical usernames, the device names differ, preventing a connection between them. It might be worth a shot, though I’m really skeptical it will succeed.

Pages (2): 1 2 Next