I can't set the port forwarding ip address on Belkin router
I've just changed my router to a Belkin N+ Wireless Router (F5D8235uk4)
My home network is on the 10.0.0.0 ip address range.
I changed the routers IP address to 10.0.0.2 (same as my last one) and the subnet is set to 255.0.0.0
My problem is that whilst my PC's are in the 10.0.0.10 to 10.0.0.20 range my NAS ip is 10.10.10.10 and when I go into the port forwarding (virtual servers) settings on the router it only let's me set the last octet with the first three octets set to 10.0.0. and these can't be changed so I can't port forward to my nas
Surely the virtual servers should be able to forward to any PC in the subnet, not just those in a 255.255.255.0 subnet?
I don't want to change my nas IP address even though that would fix this issue.
More aboutport forwarding address belkin router
Just had a chat with Belkin and apparently it is by DESIGN that you can't change the first three octets in the virtual servers screen and the DHCP scope...
Apparently this is acceptable because it is not an enterprise device
So my £9 netgear that it replaces was a serious business router as it could do the above
why the hell did u change it to 10.0.0 in the first place? technically any device that starts with ip 10.10.10 cannot connect to a network with ip 10.0.0, so ur nas isnt connected. go to DHCP settings on ur router and set it to run from 10.10.10.5 to 10.10.10.100, change router ip to 10.10.10.4 or something then reassign pot forward
My nas IS connected...it's the router that won't port forward.
Technically a device with Ip 10.0.0.x CAN connect to a device with Ip of 10.10.10.10 as it's the subnet mask that determines what can and can't connect. The default subnet mask for the 10.x.x.x scope is 255.0.0.0 so that is not the problem.
The problem is that the router will only forward to 10.0.0.x and ignores the subnet mask.
A blatant error on Belkins part but hey ho, it's a discontinued device so no chance of them correcting their error.
I'll have to change my IP's...good chance that it's not loads of devices
so you are claiming that any ip address can be assigned in a DHCP that starts with 10.0.0 ?