F5F Stay Refreshed Software Operating Systems Problem encountered (resolved)

Problem encountered (resolved)

Problem encountered (resolved)

B
Batpod400
Junior Member
17
07-07-2017, 02:54 PM
#1
I have two Windows 10 systems both configured to access my NAS through homegroup. The latest updates are installed, yet I’m encountering issues. Both my 1600x and 1800x rigs display network shares under the homegroup, but my 1800x still shows all shares under the network. My 1600x, however, doesn’t show the NAS at all despite having full access. Recently, after resetting my router during maintenance, my 1800x updated to a new IP address, and it seems to recognize the new one. But my 1600x’s NAS icon isn’t showing up. I attempted to map the 1800x icon onto the 1600x, but it didn’t work. If homegroup settings persist after removal, will deleting the direct link restore access like with the 1600x? It’s strange because I can still map network drives to any share on my NAS from the 1600x, so the system recognizes it. This behavior feels unusual, especially since I can see network drives on my 1600x. The 1800x appears to be retaining its setup, but I’m unsure if removing the direct connection will fix everything. This seems like a Windows update issue.
B
Batpod400
07-07-2017, 02:54 PM #1

I have two Windows 10 systems both configured to access my NAS through homegroup. The latest updates are installed, yet I’m encountering issues. Both my 1600x and 1800x rigs display network shares under the homegroup, but my 1800x still shows all shares under the network. My 1600x, however, doesn’t show the NAS at all despite having full access. Recently, after resetting my router during maintenance, my 1800x updated to a new IP address, and it seems to recognize the new one. But my 1600x’s NAS icon isn’t showing up. I attempted to map the 1800x icon onto the 1600x, but it didn’t work. If homegroup settings persist after removal, will deleting the direct link restore access like with the 1600x? It’s strange because I can still map network drives to any share on my NAS from the 1600x, so the system recognizes it. This behavior feels unusual, especially since I can see network drives on my 1600x. The 1800x appears to be retaining its setup, but I’m unsure if removing the direct connection will fix everything. This seems like a Windows update issue.

W
Wercerp
Junior Member
18
07-09-2017, 09:46 AM
#2
It seems the map drives handle everything properly now.
W
Wercerp
07-09-2017, 09:46 AM #2

It seems the map drives handle everything properly now.

J
JXMESxD
Member
89
07-13-2017, 07:01 AM
#3
It's strange how this allows me to assign shares one by one, but not the entire server as it did before.
J
JXMESxD
07-13-2017, 07:01 AM #3

It's strange how this allows me to assign shares one by one, but not the entire server as it did before.

_
_iSing
Member
50
07-23-2017, 12:28 PM
#4
I solved the issue, though I’m not familiar with other NAS systems. I mapped a share and it functioned properly. Later I saw it added to my network list, so I right-clicked it and saved it to the start menu. Now I can access all shares easily. I created a shortcut on the desktop and renamed it—everything is working now.
_
_iSing
07-23-2017, 12:28 PM #4

I solved the issue, though I’m not familiar with other NAS systems. I mapped a share and it functioned properly. Later I saw it added to my network list, so I right-clicked it and saved it to the start menu. Now I can access all shares easily. I created a shortcut on the desktop and renamed it—everything is working now.