liamthefirst
Prominent Member
Another thing that comes to mind is the workgroup. Are all three machines joining the same workgroup?
all the same
Another thing that comes to mind is the workgroup. Are all three machines joining the same workgroup?
When you say servers do you mean NAS drives I think Synology call them Media Servers. If so the model numbers would help!
Also has this ever worked before?
Sorry forgot to add, when you login to your Windows 10 devices, do you have a password, a pin or neither?
Could you see if this works when you plug the laptop into your switch? There are a few things that could be causing this. The one that springs to mind is that Windows 10 likes to run the homegroup itself and I have seen issues with this. I like to change that setting so I use usernames and passwords to do it. Not related to asking you to do it wired!!
No its likely that you either have a firewall issue or probably like that network discovery has not been enabled.
Have you checked the network discovery settings. Right click on your wireless or wired icon in the bottom right hand side. Then click on Change advanced sharing settings.
You should get something like this
View attachment 743792
If you computer says it is on Guest or Public then you need to change this to Private
Servers will include any machine that provide a service within the LAN. The Synology machine usually have several services running simultaneously. At the very least they have a file server and media server. Network printers, wireless or wired will also be consider a print server. All such devices should have always the same IP address so that they can be found at the same IP. These devices should be within the same range of IP addresses, same netmask and DNS server. The router will do all that unless one of them have been giving an IP manually.
Talking about it. The OP could also check that the DHCP server in the router is not giving the IP addresses of the servers as well. It could be that the laptop is grabbing one of the IP addresses before the server join the network.
For what you describe it seems that there is some misconfiguration on the network settings.if im honest i sort of understand what your saying but not sure how i would check any of this info
I guess we all have different opinions. I'd advise to do it because it simply fits the bill and unless one knows networking very well it solves many problems that configuring manually brings to the table. For all intent and purpose it will behave like an static IP and no need to do all the configuring that can tricky for most users.I'd advise NOT to do this. Reserved DHCP addressing was designed for very specific usage scenarios with diskless workstations. It's far better to use static addressing on each static device.
I guess we all have different opinions. I'd advise to do it because it simply fits the bill and unless one knows networking very well it solves many problems that configuring manually brings to the table. For all intent and purpose it will behave like an static IP and no need to do all the configuring that can tricky for most users.
FYI - the OP PM'd me an IPCONFIG - it all looks fine, G/W, DNS and DHCP servers are all pointing to the same device which one presumes is his router at 192.168.0.1. However, this doesn't look like an IP addressing issue to me. It looks more like either a firewall issue or some drive handles/security (as in credentials, SID's, etc.) nastiness. Presumably the Synology NAS's are using some form of *NIX and as we know *NIX is fussy about case sensitivity (e.g. names, loginids, passwords, etc) where Windows is not.
FWIW - I'm Win10 and didn't encounter any issues when transitioning from Win7 - my media server is Linux based HP micorserver (no idea which version of SMB) - it all worked fine - I'm not using any (old school) drive handles, normal URL's seem to be working fine and I can browse for the shares without issue.
I guess it may be worth establishing whether he's using SMB (versus NFS) shares just to rule that out.
Can't see it being a firewall issue - why would internal LAN traffic be crossing the router firewall? Even if the laptop and synology boxes are connect via the router switch ports, they wouldn't be crossing the firewall as the rules are applied to the WAN port... unless the synology boxes are attached to the switch, in turn connected to a port on the router that has been designated a DMZ...
You might call it whatever you want that it is your opinion. Enterprise best practice does not extrapolate to small home LAN. MAC addresses are one of the easiest to get from the network configuration, the fact that they are in hexadecimal is neither here nor there. MAC addresses are a series of characters for most users. Most users in a home environment will have a very limited number of servers. One or two file, media servers a printer and pretty much everything else can have dynamic addresses.Its not so much opinion, but using the tool as it was designed for and the advantages it delivers, borrowing from enterprise best practice.
If you have a consistent approach to addressing, then when trying to troubleshoot why something doesn't work you don't need to constantly check on what device has what address, reconfigure the network, or spend time in the DHCP server.
Reserved addressing was designed for diskless workstations that needed a static IP address, for example an application that would only respond to IP addresses in a given range, and it is obviously impossible to assign a static address to a diskless client.
I'd have to disagree that manual configuration of a client is any "trickier" than using a reserved address; I'd argue that it is easier; both require configuring the DHCP server. One then accesses the client, and enters a set of numbers; address, mask, gateway, and DNS. Compare that to trying to instruct a novice how to extract a hexadecimal MAC address and enter that into a router, assign an IP address, and do it for each static device on their network.
I'm not arguing that it doesn't work, it's simply 'arrse-about-face' for network configuration... Its also far more work if - no, when - the router is changed or the firmware updated) one has to recreate the entire reserved pool, ie re-enter by hand a list of MAC and IP addresses. OTOH, with a designed addressing strategy using manual addressing on the fixed clients, on simply has to change - at most - router's DHCP pool and it's address.
It's also one less area to have to check when there are issues, ie double checking the MAC addresses are correct, which has to be done by hand.
I would tend to agree with @tich77 that it is not a firewall issue. If the windows 10 machine would be the one providing the service the firewall might be the one blame but the fact that it cannot find a service I would tend to find the problem in some sort of network configuration, user-password access to the service.I'm thinking of the Windows firewall (on the errant client) rather than the router firewall. As surmised, local LAN traffic doesn't transcend the router firewall so it's not relevant, but Windows clients have had a local "personal" firewall in the last few versions. There could be a scenario in a laptop with multiple NIC's, that the rulesets differ between the NIC's which could give rise to the observed behaviour (works one NIC and not the other.) Whilst I agree it's unlikey (SMB et al tends to be permitted by default) it would be fairly trivial to test and rule it out: Find the firewall control in Systems and Security, turn it off, test, then turn it back on again.
You might call it whatever you want that it is your opinion.
Enterprise best practice does not extrapolate to small home LAN.
MAC addresses are one of the easiest to get from the network configuration, the fact that they are in hexadecimal is neither here nor there. MAC addresses are a series of characters for most users.
]Most users in a home environment will have a very limited number of servers. One or two file, media servers a printer and pretty much everything else can have dynamic addresses.
Anybody who is doing it by hand will have to understand IP range, netmask and dns which can be very tricky for users who never have configured networks. A DCHP server will do all that without the user having to understand any network configuration.
If the user understands networking very well then by all means go and configure it by hand. Otherwise allow the router to do all the work. It also guarantee that those device with more than one adapter will have the same IP.
I have a Synology NAS which has several services and network printer/fax/scanner and Windows, Linux, OSX systems as well as media devices like TV, players, amps, phones, etc, all working perfectly fine and none of them have ever lost access to one of my services, shares.
Static IP address configuration will always have the issue that if you networking configuration changes your static IP addresses might be out of range, wrong netmask or not direct access to the DNS servers specially if using DNS servers outside you LAN as you suggested.
SmbFYI - the OP PM'd me an IPCONFIG - it all looks fine, G/W, DNS and DHCP servers are all pointing to the same device which one presumes is his router at 192.168.0.1. However, this doesn't look like an IP addressing issue to me. It looks more like either a firewall issue or some drive handles/security (as in credentials, SID's, etc.) nastiness. Presumably the Synology NAS's are using some form of *NIX and as we know *NIX is fussy about case sensitivity (e.g. names, loginids, passwords, etc) where Windows is not.
FWIW - I'm Win10 and didn't encounter any issues when transitioning from Win7 - my media server is Linux based HP micorserver (no idea which version of SMB) - it all worked fine - I'm not using any (old school) drive handles, normal URL's seem to be working fine and I can browse for the shares without issue.
I guess it may be worth establishing whether he's using SMB (versus NFS) shares just to rule that out.
Wow thats a lot to read. I will work through it tonight. Thanks all