Unable to access readyshare drive from LAN ports

Question

The network setup that I have is as follows:

Modem --> Orbi --->R6220---> PC

|---------> PC

|---------> USB Storage

The R2220 is configured in AP mode and the wireless is diabled. All devices can access the internet; the wired devices through the R6220 and the wireless devices through the Orbi. The reason the network is setup like this is that it's a home network, and I want NAS but the NAS need not be very high performance, and it's only used occassionally. Rather than use a switch, the R6220 provides an economical switch and integrated NAS (through readyshare).

The problem is this: SMB can be accessed through wireless devices, but not through wired devices. http is enabled (for readyshare) and can be accessed through both wireless and wired devices. However, SMB ("\\readyshare") refuses to work if accessed through the LAN ports on the R6220. I think the wireless devices can access SMB becuase their packets travel into the R6220 through the WAN port. Is this intended behavior, and is there any way I could access SMB from devices plugged into the LAN ports?

antinode · Answer

&gt; [...] SMB ("\readyshare") refuses to work if accessed through the LAN&gt; ports on the R6220. [...]&nbsp;&nbsp;&nbsp; Have you tried specifying the LAN IP address of the R6220-as-WAP,instead of "readyshare".&nbsp; An Attached Devices report on the(unspecified) "Orbi" should reveal that address.&nbsp; (While you're there,you might also want to reserve some (memorable) address for theR6220-as-WAP, so that it doesn't wander around (and you won't need tosearch for it henceforth).)&nbsp;&gt; I think [...]&nbsp;&nbsp;&nbsp; I doubt it.&nbsp; To me, this smells more like a name-resolution problemthan a basic comm problem.&nbsp;&gt; [...] http is enabled (for readyshare) and can be accessed through&gt; both wireless and wired devices. [...]&nbsp;&nbsp;&nbsp; I'd expect a basic comm problem to be protocol-independent.&nbsp; But thename-resolution scheme used by Windows for file sharing might be moreexotic than that used by a web browser for HTTP(S).

ggarner1995 · Answer

I already use the DHCP address reservation to reserve 192.168.1.20 as the address, so the Orbi's DHCP will always assign that address. As for name resolution, it's not actually the problem (the broadcast is used to resolve the local hostnames), but you're correct that this has nothing to do with the wireless ports. It still happened when I connected the computer over the wireless.

I decided to capture the traffic with wireshark and here is what I found (first column time; r6220 is 192.168.1.20, and I'm 192.168.1.9):

Wireshark

ggarner1995 · Answer

It appears that the image failed to appear; link to image:&nbsp;https://imgur.com/a/bYLPZtk

michaelkenward · Answer

&nbsp;
ggarner1995&nbsp;wrote:
It appears that the image failed to appear; link to image:&nbsp;https://imgur.com/a/bYLPZtk

It may be some time before the images land. To ensure that you aren't posting anything naughty, a Netgear moderator has to approve the pictures.
&nbsp;
You can attach images to messages without any delay. That is safer than expecting people to follow possibly dodgy links to other sites.

antinode · Answer

&gt; As for name resolution, it's not actually the problem (the broadcast&gt; is used to resolve the local hostnames), [...]&nbsp;&nbsp;&nbsp; If you say so.&nbsp; That's not obvious to me.&nbsp;&gt; Have you tried specifying the LAN IP address of the R6220-as-WAP,&gt; instead of "readyshare". [...]&nbsp;&nbsp;&nbsp; So, that's a "no"?&nbsp;&gt; I decided to capture the traffic with wireshark [...]&nbsp;&nbsp;&nbsp; That's nice.&nbsp; And I'm supposed to get what useful info from thatdump?

Forum Discussion

Unable to access readyshare drive from LAN ports

5 Replies