F5F Stay Refreshed Power Users Networks Problem with sharing files on Windows network.

Problem with sharing files on Windows network.

Problem with sharing files on Windows network.

Pages (2): 1 2 Next
S
samigurl0903
Senior Member
603
08-16-2016, 04:50 PM
#1
Hey! Your Windows 10 PC in the cupboard has been functioning well as your NAS, media server, and other services for years. The new gaming PC connected smoothly once you enabled file sharing. After a recent Windows upgrade, the network share stopped showing up on your new PC, even though you followed the same steps as before. You mentioned possible router issues or a recent installation affecting connectivity. After checking both devices, you tried adjusting services and registry settings, but still faced problems like the "0x80070035" error. You removed licensing files and rebooted, yet the network PC vanished from view. It seems you're unsure whether the router itself is the problem or if something went wrong during the new PC setup. You might want to double-check your network adapter settings, ensure the correct driver is installed, and verify that Windows services are running properly. If needed, consider reinstalling Windows on both machines for a clean setup.
S
samigurl0903
08-16-2016, 04:50 PM #1

Hey! Your Windows 10 PC in the cupboard has been functioning well as your NAS, media server, and other services for years. The new gaming PC connected smoothly once you enabled file sharing. After a recent Windows upgrade, the network share stopped showing up on your new PC, even though you followed the same steps as before. You mentioned possible router issues or a recent installation affecting connectivity. After checking both devices, you tried adjusting services and registry settings, but still faced problems like the "0x80070035" error. You removed licensing files and rebooted, yet the network PC vanished from view. It seems you're unsure whether the router itself is the problem or if something went wrong during the new PC setup. You might want to double-check your network adapter settings, ensure the correct driver is installed, and verify that Windows services are running properly. If needed, consider reinstalling Windows on both machines for a clean setup.

W
WZ_Galaktiik
Senior Member
251
08-18-2016, 09:01 PM
#2
Map the network drive, discovery problems persist, avoid using it for NAS. You can reach the NAS by going to \\NASIP\share in Explorer.
W
WZ_Galaktiik
08-18-2016, 09:01 PM #2

Map the network drive, discovery problems persist, avoid using it for NAS. You can reach the NAS by going to \\NASIP\share in Explorer.

P
Parzival10
Member
180
08-19-2016, 01:35 PM
#3
I attempted that method, sorry I didn’t note it earlier. It’s the usual way since I need to use various login details, and it hasn’t caused any problems. When trying to connect, it just loops or displays the message: “The mapped network drive could not be created because the specified network name is no longer available.”
P
Parzival10
08-19-2016, 01:35 PM #3

I attempted that method, sorry I didn’t note it earlier. It’s the usual way since I need to use various login details, and it hasn’t caused any problems. When trying to connect, it just loops or displays the message: “The mapped network drive could not be created because the specified network name is no longer available.”

D
davidspyro
Member
213
08-19-2016, 02:32 PM
#4
It seemed like someone was about to mention something but was too fast.
D
davidspyro
08-19-2016, 02:32 PM #4

It seemed like someone was about to mention something but was too fast.

W
witherman_1987
Junior Member
37
08-19-2016, 04:23 PM
#5
Using IP or hostname? Which SMB version is supported? Can you simply attempt to open the path?
W
witherman_1987
08-19-2016, 04:23 PM #5

Using IP or hostname? Which SMB version is supported? Can you simply attempt to open the path?

F
Foxing_Box
Member
80
08-19-2016, 11:53 PM
#6
Have you explored mounting at an IP address or just at a host address? Can you send a ping to the IP address? Is the DNS handling its tasks correctly? A ping command in the prompt will confirm this. If you can't ping using the hostname, updating the hostfile is a fast solution.
F
Foxing_Box
08-19-2016, 11:53 PM #6

Have you explored mounting at an IP address or just at a host address? Can you send a ping to the IP address? Is the DNS handling its tasks correctly? A ping command in the prompt will confirm this. If you can't ping using the hostname, updating the hostfile is a fast solution.

T
TaylorMay
Junior Member
11
08-27-2016, 01:52 AM
#7
I've attempted to link to the PC using both hostname and IP address. The router has a fixed IP, so SMB works but I'm still seeing "Windows cannot access \\Rick-pc\g". It seems the issue might be with the shared folder setup or network configuration. I tried recreating the share by naming it "g" due to frustration.
T
TaylorMay
08-27-2016, 01:52 AM #7

I've attempted to link to the PC using both hostname and IP address. The router has a fixed IP, so SMB works but I'm still seeing "Windows cannot access \\Rick-pc\g". It seems the issue might be with the shared folder setup or network configuration. I tried recreating the share by naming it "g" due to frustration.

S
SayNoToNWO
Posting Freak
879
09-03-2016, 11:44 PM
#8
It is successfully connecting to the static IP of the network drive's computer and sending all four pings as expected.
S
SayNoToNWO
09-03-2016, 11:44 PM #8

It is successfully connecting to the static IP of the network drive's computer and sending all four pings as expected.

M
MECrageman
Member
180
09-09-2016, 05:36 PM
#9
SMB has frequently encountered issues. There are no other alternatives I can offer.
M
MECrageman
09-09-2016, 05:36 PM #9

SMB has frequently encountered issues. There are no other alternatives I can offer.

T
timmyblack
Member
229
09-09-2016, 07:49 PM
#10
-t and ping four times don't display any results.
T
timmyblack
09-09-2016, 07:49 PM #10

-t and ping four times don't display any results.

Pages (2): 1 2 Next