[mdns] SMB between windows machines doesn't work
[mdns] SMB between windows machines doesn't work
Hello and thank you in advance.
I have created an mDNS rule to enable access from my main LAN (192.168.0.1/24) to my office VLAN (192.168.20.1/24) and obviously SMB is enabled in the Bonjour Service.
After spending hours configuring the Windows firewall settings, I am now able to ping the Windows machines (located in the office VLAN) from my Windows PC in the main LAN, but I can't access to my smb folder.
I can successfully access my Epson printer (https) and ping every device in my office VLAN from my main LAN. However, it seems that the issue may lie with the Windows machines themselves.
Do you have any ideas on how I can access shared folders on my office VLAN from my main LAN?
I have created ACL rules to permit access from the main VLAN to the office VLAN and to restrict the office VLAN's access to other VLANs. Could this possibly be the source of the problem?
Thank you very much!
ER605 v1.0
Firmware 1.3.0
EDIT: the office vlan has the following DHCP Range 192.168.20.100 - 192.168.20.200
The two windows machine are outside this range (192.168.20.98 and 192.168.20.99)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @umbertodm
Thanks for posting in our business forum.
umbertodm wrote
After set mdns my windows pc (192.168.0.110) can access trough smb (windows file explorer) to my Qnap NAS (192.168.20.137) that's why I thought the prolbem was in the other two windows machine (192.168.20.98 and 192.168.20.99).
I am not sure about the Windows SMB service. Yes, we do have a preset about SMB. Our internal shared platform is hosted by a Windows Server. But I cannot capture the mDNS about it. Probably I should capture at the ingress port.
Is this working fine now? For extra reference, Troubleshooting - mDNS Repeater on the Router Doesn't Take Effect
Would be helpful if you could share more knowledge about that.
Update: The issue is not caused by the Omada router. If you face similar issues, please use the error code and contact MS support or seek help on the MS forum.
Typically, if this is an mDNS issue, you should fail to access from the Windows PC to the NAS. Or fail to discover the NAS by network map. Only when you doing a cross-network discovery, and you fail to discover the other device, that's a typical symptom of mDNS.
You may refer to the troubleshooting link above if you face an mDNS issue.
- Copy Link
- Report Inappropriate Content
are you sure that windows smb service is using mDNS?????
i use wireshark and I found nothing about it.
- Copy Link
- Report Inappropriate Content
Thank you for your reply.
No, I'm not sure, I just saw smb in the Bonjour services and I thought it could work.
- Copy Link
- Report Inappropriate Content
without acl, without vlan interface, can you access the file server? i was once having a trouble with the windows SMB. i set up my NAS with SMB. i also spent hours on user privilege. was facing an issue that I had no authority to access it. you should rule that out.
- Copy Link
- Report Inappropriate Content
After set mdns my windows pc (192.168.0.110) can access trough smb (windows file explorer) to my Qnap NAS (192.168.20.137) that's why I thought the prolbem was in the other two windows machine (192.168.20.98 and 192.168.20.99).
- Copy Link
- Report Inappropriate Content
Hi @umbertodm
Thanks for posting in our business forum.
umbertodm wrote
After set mdns my windows pc (192.168.0.110) can access trough smb (windows file explorer) to my Qnap NAS (192.168.20.137) that's why I thought the prolbem was in the other two windows machine (192.168.20.98 and 192.168.20.99).
I am not sure about the Windows SMB service. Yes, we do have a preset about SMB. Our internal shared platform is hosted by a Windows Server. But I cannot capture the mDNS about it. Probably I should capture at the ingress port.
Is this working fine now? For extra reference, Troubleshooting - mDNS Repeater on the Router Doesn't Take Effect
Would be helpful if you could share more knowledge about that.
Update: The issue is not caused by the Omada router. If you face similar issues, please use the error code and contact MS support or seek help on the MS forum.
Typically, if this is an mDNS issue, you should fail to access from the Windows PC to the NAS. Or fail to discover the NAS by network map. Only when you doing a cross-network discovery, and you fail to discover the other device, that's a typical symptom of mDNS.
You may refer to the troubleshooting link above if you face an mDNS issue.
- Copy Link
- Report Inappropriate Content
Thank you for your reply.
Perhaps I didn't explain the issue clearly.
My Windows PC on the main LAN (192.168.0.110) can access the Qnap NAS (192.168.20.137) through the file explorer, indicating that the SMB connection works well via mDNS.
However, I am unable to access other computers (192.168.20.98) on the 192.168.20.1/24 VLAN via SMB from the same Windows PC, even though I can successfully ping them.
- Copy Link
- Report Inappropriate Content
Hi @umbertodm
Thanks for the updated message.
If so, that should be an issue with the parameters on your Windows. Not a problem with the mDNS on the router.
- Copy Link
- Report Inappropriate Content
Hi @umbertodm
Any update on this problem?
- Copy Link
- Report Inappropriate Content
Unfortunately I didn't solve the problem.
I tried a lot of setting on the Windows pc I cannot access to, but I can't found enough on internet.
- Copy Link
- Report Inappropriate Content
Hi @umbertodm
Thanks for posting in our business forum.
You probably gonna find this and add the user account to that computer.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1354
Replies: 12
Voters 0
No one has voted for it yet.