NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to access readyshare drive from LAN ports
The network setup that I have is as follows: Modem --> Orbi --->R6220---> PC |---------> PC |---------> USB Storage The...
> [...] SMB ("\\readyshare") refuses to work if accessed through the LAN
> ports on the R6220. [...]
Have you tried specifying the LAN IP address of the R6220-as-WAP,
instead of "readyshare". An Attached Devices report on the
(unspecified) "Orbi" should reveal that address. (While you're there,
you might also want to reserve some (memorable) address for the
R6220-as-WAP, so that it doesn't wander around (and you won't need to
search for it henceforth).)
> I think [...]
I doubt it. To me, this smells more like a name-resolution problem
than a basic comm problem.
> [...] http is enabled (for readyshare) and can be accessed through
> both wireless and wired devices. [...]
I'd expect a basic comm problem to be protocol-independent. But the
name-resolution scheme used by Windows for file sharing might be more
exotic than that used by a web browser for HTTP(S).
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
It appears that the image failed to appear; link to image: https://imgur.com/a/bYLPZtk
ggarner1995 wrote:
It appears that the image failed to appear; link to image: 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.
You can attach images to messages without any delay. That is safer than expecting people to follow possibly dodgy links to other sites.
> As for name resolution, it's not actually the problem (the broadcast
> is used to resolve the local hostnames), [...]If you say so. That's not obvious to me.
> Have you tried specifying the LAN IP address of the R6220-as-WAP,
> instead of "readyshare". [...]So, that's a "no"?
> I decided to capture the traffic with wireshark [...]
That's nice. And I'm supposed to get what useful info from that
dump?
