Hi, in a recent thread I've been battling with my network. Thanks Ed and Samuria for the suggestions.
(This is the thread Ping OK but HTTP/HTTPS (mostly) failing)
Current status is my PC seems to be working BUT the issue that I noted just before it all fell around my ears remains.
I have a NAS. It holds all my archive images. I usually connect to it as a drive P: (P for pictures) and access images via Lightroom.
My configuration is thus:
PC > wifi > router > wifi > bridge/access point > 1) NAS 2) printer.
This config is down to neither the printer nor NAS being wifi capable but being needed by various machines in the house and I can't plug them direct to the router as they're in a different place in the house.
Back history (for completeness). The router was recently changed from an 802.2g to an 802.2ac model and the bridge/access point had to be reset to link in with it.
PC is (currently) DHCP addressed to 192.168.1.104
router (ISP provided Technicolour MediaAccess TG589vac v2 box) is 192.168.1.1
the bridge/access point is a TP-Link TL-WA701ND access point on 192.168.1.254 set in client mode, it then is cabled into a TP-Link SF1005D switch and the printer and the NAS are cabled into the switch.
The printer has a static IP address set in its control panel as 192.168.1.101 with subnet 255.255.255.0
The NAS has a DHCP address picked up at boot, currently 192.168.1.78, same netmask.
I can ping/tracert either printer or NAS.
I can print happily.
If I go to my browser and type in 192.168.1.78 I am prompted to enter the admin credentials and can get into the NAS dashboard (Seagate 4 bay business NAS).
In other words my local network appears to be working fine.
However I can't access the drive on the network.
Whether I use the desktop PC, which has been experiencing problems in the above thread, or whether I use my laptop PC which has shown no networking issues, when I go to Windows Explorer and choose NETWORK I see nothing.
What I used to see was the "NASDevicename" in that folder. I could click on it and see two folders, "Mark" and "public".
I could right click on Network and choose to map as P: either "\\NASDevicename\public" or "\\192.168.1.78\public".
If I launch the Seagate NAS Discovery tool it shows no drives present.
If I go to a command prompt and try:
NET USE P: \\NASDevicename\public
NET USE P: \\192.168.1.78\public
I get "System Error 53 Network Path Not Found"
So I can ping it, I can get into the admin panel, the shared folders exist, but I can't see them on either a PC or a laptop (both Win 10).
I did find one hit online that suggested to go to Control Panel\All Control Panel Items\Network Connections select the connection, adjust the properties for IPv4\advanced\WINS from "default" to "enable NetBIOS over TCP/IP".
I was about to try that when my previous issues hit me and now that I've got access to the network again am reluctant to try it without a cross check!
It's some 20 years since I worked in networking so my memory is hazy on this stuff but I know SYS53 is likely name resolution issues.
Running NET VIEW \\192.168.1.78 or NET VIEW \\NASDevicename will retunr system error 53.
I don't have an LMHOSTS file in c:\windows\System32\drivers\etc (the .sam sample is there, obviously) and I've not edited the hosts file - and given that the NAS is DHCP setup I haven't done so in the past either.
In the past this stuff has just worked. Other than the router nothing substantial has changed.
Of possible interest is that in the router dashboard the devices list shows the IP address for the NAS but not its device name (I can't edit that).
For that reason I tried setting up in the router a static IP for the NAS using its proper "NASDevicename" and 192.168.1.78 for the IP address.
The result doesn't change. I get a sys 53 in trying to NET USE from the command prompt or if I try to map network drive in Windows Explorer I get "Windows cannot access \\NASDevicename\public" and an error code of 0x80070035 The network path was not found.
Any bright ideas, please?