NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
readynas 314 cant access via network places
hi all, i hope someone can help as ive spent a lot of time trying to figure this out and not getting any success basically, in windows > network places, i can see the nas (Mysight-cloud) but when...
thanks Stephen, i have now bonded the NIC's using ALB, that's working perfectly now, have access to 192.168.1.245 and \\mysight-cloud\.
it did break the vpn, i told the vpn to use bond0 - didn't work, then told it to use eth0, still didn't work, but then told it to use eth1 and It works,
thanks very much for your help, if its still working in a few days then i know i have definitely cracked it
Think I might have found the problem. I have it set to static for both cables that are plugged in. So eth0 is 192.168.1.245
Eth1 is 192.168.1.246
Been playing and it seems to be the router being the issue. I think. It is showing both in the list of connected devices. But if I click on the one that's eth0. It says 245 dhcp.
Other one eth1 says 246 static.
So under eth0 on my router it says always use same IP. I tick it and Apply. And then the IP address completely changes to something like 65 not 245 like the nas is static to. So I'm correctly contacting the provider of our router. It's a technicolor router. Not really keen on this router at tho mo.
I'll let you know if I manage to fix it. Or if any one has any info on this with this type of router then feel free to let me know.
Eth1 is 192.168.1.246
Been playing and it seems to be the router being the issue. I think. It is showing both in the list of connected devices. But if I click on the one that's eth0. It says 245 dhcp.
Other one eth1 says 246 static.
So under eth0 on my router it says always use same IP. I tick it and Apply. And then the IP address completely changes to something like 65 not 245 like the nas is static to. So I'm correctly contacting the provider of our router. It's a technicolor router. Not really keen on this router at tho mo.
I'll let you know if I manage to fix it. Or if any one has any info on this with this type of router then feel free to let me know.
alanh-mysight wrote:
Think I might have found the problem. I have it set to static for both cables that are plugged in. So eth0 is 192.168.1.245Start by disconnecting the second cable for now. After you get reliable connectivity we can talk about NIC bonding.
You might need to reboot the router and then reboot the NAS to get the DHCP binding to stick.
think ive fixed it, thanks stephen, i did start with just the one cable to begin with
if only one cable connected, then IP or hostname works so network places does find it, brilll, but breaks VPN connection
the way that seems to work is
eth0 is set to static 192.168.1.245
eth1 is set to dynamic - currently 192.168.1.82
VPN is set to use eth1
all seems to work, router accepts eth0 now being static, bit werid but if both are set to static my router doesnt like it.
i have had a look at the bond settings but if i do it it seems to break the vpn, im using the vpn server app the uses softether.
biggest test, im about to turn it all off, then back on and see if it all can work normal
yippee, the whole thing is working
dont really understand what actually fixed it but it workes so that's good enough for me.
feel free to shed some light on it for me. before working at this charity ive never touched a network (apart from the typical home network). its definitly been a ride, networks are a lot harder then they look, ain't as simple as just plug it in.
thanks for all your help guys, much appreciated.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
