Recommended Posts

Hello fellow neowinians.

 

I have trouble with my router, because it's a provider sample and it's dumb as ********. It's slow and really dumb.

Is there anyway to access devices outside my domain? By factory default router was 192.168.1.1 and since it didn't see devices only some I've changed it, but now I don't see the once which where there when 1.1. This stupid router makes me nuts, is there anyway to access that device without screwing up the currently recognized 192.168.0.X devices? I have to access 1 NAS which is currently stuck in the 192.168.1.X subnet.

 

Pinging not possible, due to I don't know the IP of the NAS. Prev setting was by default dynamic, always set the static IP in router setting. Currently half of the static IP's are correct by router, still executes rules which are not even there in the setting, but had it once.

 

Thanks for helping, probably this is basic IPv4 knowledge, but I really don't know how to make it work, without destroying the current setup.

 

BTW, my network is simple. NET > ROUTER (CABLE+WIFI) > GB SWITCH > 1PC + 4NAS

Link to comment
https://www.neowin.net/forum/topic/1326316-ipv4-basic-network-setup/
Share on other sites

What is the make/model of the router you now have?

 

If DHCP is enabled on the router and also the clients, then it shouldn't matter what IP range (192.168.0.x or 192.168.1.x) as all your devices will work automatically. That said, as you haven't set a static IP on the devices, you should be able to log into the router's web interface and view the connected IP addresses. That will give you the currently assigned addresses. Once you have that info, I would highly recommend setting a static IP on the devices themselves, if you want to ensure they always have the same IP.

 

I'd also consider waiting to hear what @BudManhas to say, as he is very good with networking issues.

 

Yes.

 

Brand is proximus. :p ...but what I can tell the ethernet hardware is "Sagemcom Broadband". But the problem is the firmware, because I have only user access to it and it's a custom one by provider. DHCP enabled ofcourse. Here is the screenshot of current settings:

 

Do i have to change the subnet mask maybe? to 255.255.0.0? And the device missing I cannot see here either. I really haven't experienced anything like this before, not even with cheap routers from TPlink or Dlink.

DHCPv4.PNG

  On 27/03/2017 at 08:25, Class said:

Yes.

 

Brand is proximus. :p ...but what I can tell the ethernet hardware is "Sagemcom Broadband". But the problem is the firmware, because I have only user access to it and it's a custom one by provider. DHCP enabled ofcourse. Here is the screenshot of current settings:

 

Do i have to change the subnet mask maybe? to 255.255.0.0?

DHCPv4.PNG

Expand  

The scroll bar on the right makes it look like there are more options if you scroll down that page? Is there anything useful?

 

Leave the subnet as 255.255.255.0, otherwise you'll enter a whole new world of problems!

 

So it sounds like your devices will have received an address somewhere between 192.168.0.2 and 192.168.0.63. Without having access to the DHCP table, I think you have two options (well, two quick options).

 

1) If you are on Windows, you can use the network discovery feature to find any local devices on your network. Then you can find the IP address and connect to the device to set a static IP

2) Manually try to browse to; 192.168.0.2, 192.168.0.3, 192.168.0.4, etc from your web browser until 192.168.0.63. You should eventually stumble across your devices.

Only the static IP settings are there unfortunately, nothing else

 

I already scanned the network with FING and no, the router did not give an IP to the this particular NAS. Before switching the router to 0.1 i had the NAS statistic router to 192.168.1.58, but erased the line and re-added to give it 192.168.0.3, but it's not being executed. Should I maybe delete the line again, in hope it will pop up in the network. The DHCP of this router is just so baaad. One of my QNAP's I had also this issue, but solved by using the other ethernet slot which was not used before and after 3rd reboot and other ethernet also popped up in the list.

 

What if simply exclude the network and connect the NAS directly into my PC, just to check if dinamic is still corrently set would work?

  On 27/03/2017 at 08:48, Class said:

What if simply exclude the network and connect the NAS directly into my PC, just to check if dinamic is still corrently set would work?

Expand  

Unlikely, as you'd still need to know the address of the NAS to connect to it from the PC.

 

Did you try Window's built-in network discovery?

Yes, did try.

 

I'm not excluding the fact the it could be because of Zyxel firmware (NSA310) is not the most stabil little device, but I restarted many times. Anyway, will to connect it directly and see if I can find the device which the network scanning.

Ok. I am not exactly sure what you are getting at. 

 

I am guessing on the network you have 192.168.1.x and 192.168.0.x. 

 

The 1.x has a router/gateway (your modem) the 0.x has no router/gateway to handle the request to go over to the 1.x network

 

you have to either re ip the network or get a router that can handle other subnets and a switch that can handle what is known as vlans (a layer 2switch).  

 

If your router understands this, technically you could put your subnet mask at 255.255.254.0 (all computers would have to have this mask as well) and then you would see the 0.x and the 1.x addresses. But keep in mind, there is no separation, it is just one big network where the network id is 192.168.0.0 and broadcast is 192.168.1.255. 

If you want to change your network from 192.168.1/24 to 192.168.0/24 and you had devices that were setup static on your network as 192.168.1 - just change them to be on the 192.168.0 network.

 

Either directly on the device.  Or set your machine to be on the 192.168.1 network and access them and change them to 192.168.0 or dhcp.. Then set your machine back to dhcp or 192.168.0 network.

  On 27/03/2017 at 11:12, sc302 said:

Ok. I am not exactly sure what you are getting at. 

 

I am guessing on the network you have 192.168.1.x and 192.168.0.x. 

 

The 1.x has a router/gateway (your modem) the 0.x has no router/gateway to handle the request to go over to the 1.x network

 

you have to either re ip the network or get a router that can handle other subnets and a switch that can handle what is known as vlans (a layer 2switch).  

 

If your router understands this, technically you could put your subnet mask at 255.255.254.0 (all computers would have to have this mask as well) and then you would see the 0.x and the 1.x addresses. But keep in mind, there is no separation, it is just one big network where the network id is 192.168.0.0 and broadcast is 192.168.1.255. 

Expand  

 

  On 27/03/2017 at 12:47, BudMan said:

If you want to change your network from 192.168.1/24 to 192.168.0/24 and you had devices that were setup static on your network as 192.168.1 - just change them to be on the 192.168.0 network.

 

Either directly on the device.  Or set your machine to be on the 192.168.1 network and access them and change them to 192.168.0 or dhcp.. Then set your machine back to dhcp or 192.168.0 network.

Expand  

Today I've played around. And I just cannot figure out what's the issue.

 

I've change back the router to 192.168.1.1 and now I have access to the other NAS, but not the other. It's either one or the other. Checked setting on Zyxel NAS, both are dynamic. And they just simply won't work. One is working if router is set to 192.168.0.1 and the other is working when 192.168.1.1. It's just a complete #WTF moment for me. I cannot think of anything else to check. Restarted the previously accessible NAS, it's just won't show up under 1.1. I'm running out of ideas what can be the problem, and I can only think of 1, the router cannot make a difference between 2 NAS of same type. Both are identical Zyxel NSA310S. Probably thinks MAC information is for noobs and recognizes only 1.

NASv4.PNG

NASv4_11.PNG

If DHCP is refusing to play ball, as a quick fix, decide which network you want to use, let's assume you pick 192.168.1.x, switch your router to 192.168.0.1, renew your DHCP on your pc so you can connect to that network, login to the NAS on that network, and give it a static IP address on the 192.168.1.x network, make a note of what you set it to (and dont set it to something that will be within the DHCP scope of the router). Once that's applied (reboot the NAS if needed, you should lose access to it on the 192.168.0.x network, then change the router back to 192.168.1.x, and renew your lease again to move your PC back, now you should be able to access the reconfigured NAS using the static IP you gave it, and the other NAS via whichever IP it picked up via DHCP. Maybe set that one static and outside of the DHCP scope too, so you always know what IP it will be on, without needing to login to the router to check.

  On 27/03/2017 at 22:50, sc302 said:

One nas is on 0.x and one is on 1.x. One of the two need to be reconfigured on the network.  Assign dhcp to the 0.x one. 

Expand  

 

  On 27/03/2017 at 22:55, DaveLegg said:

If DHCP is refusing to play ball, as a quick fix, decide which network you want to use, let's assume you pick 192.168.1.x, switch your router to 192.168.0.1, renew your DHCP on your pc so you can connect to that network, login to the NAS on that network, and give it a static IP address on the 192.168.1.x network, make a note of what you set it to (and dont set it to something that will be within the DHCP scope of the router). Once that's applied (reboot the NAS if needed, you should lose access to it on the 192.168.0.x network, then change the router back to 192.168.1.x, and renew your lease again to move your PC back, now you should be able to access the reconfigured NAS using the static IP you gave it, and the other NAS via whichever IP it picked up via DHCP. Maybe set that one static and outside of the DHCP scope too, so you always know what IP it will be on, without needing to login to the router to check.

Expand  

Yeah, you just tell the basic thing. Not helping. I did this yesterday. I'm not kidding when I tell, I don't have the goddamn thing. I tried both, letting DHCP give "ball" and "fix ball" I don't have both. I will today swap back to 0.1 and check out once again the other NAS not that I missed any settings.

 

I'm thinking now, could it be the switch who doesn't play along with the router's DHCP?

  On 28/03/2017 at 04:28, Class said:

 

Yeah, you just tell the basic thing. Not helping. I did this yesterday. I'm not kidding when I tell, I don't have the goddamn thing. I tried both, letting DHCP give "ball" and "fix ball" I don't have both. I will today swap back to 0.1 and check out once again the other NAS not that I missed any settings.

 

I'm thinking now, could it be the switch who doesn't play along with the router's DHCP?

Expand  

If you're setting static IPs, then DHCP has nothing to do with it. I'm guessing you just have a dumb switch, so no, that's not going to be interfering with the DHCP from the router. Take some screenshots of the settings page of your NAS when you're in there.

  On 28/03/2017 at 04:28, Class said:

 

Yeah, you just tell the basic thing. Not helping. I did this yesterday. I'm not kidding when I tell, I don't have the goddamn thing. I tried both, letting DHCP give "ball" and "fix ball" I don't have both. I will today swap back to 0.1 and check out once again the other NAS not that I missed any settings.

 

I'm thinking now, could it be the switch who doesn't play along with the router's DHCP?

Expand  

You do know that sometimes you have to reboot the equipment ( in this case the nas) for changes like this to take effect. 

  On 28/03/2017 at 11:21, sc302 said:

You do know that sometimes you have to reboot the equipment ( in this case the nas) for changes like this to take effect. 

Expand  

Reboot counter for device is currently between 20-30 times the last 2 days.

 

  On 28/03/2017 at 07:56, DaveLegg said:

If you're setting static IPs, then DHCP has nothing to do with it. I'm guessing you just have a dumb switch, so no, that's not going to be interfering with the DHCP from the router. Take some screenshots of the settings page of your NAS when you're in there.

Expand  

There is no static routing currently. That what I try to tell. I tried static, I tried dinamic, I tried 0.1 and 1.1. Currently the diagnose is still the SAME. 1 NAS active here, other is active there. So for no one can understand this, not even me.

  1. cables √
  2. switch √
  3. router DHCP dynamic √
  4. router DHCP static √
  5. FING √
  6. zyxel nas setting √

I cannot think anything else anymore. Here is the proof, this is still yesterday setting as 1.1. "CLASS-ZYX" is one nas, and "CLASS-ZYQ" is the one nas. Same type, different name.

IMG_20170328_155306.jpg

Try setting the IP on the NAS itself to a static IP, not on the router. Login to the NAS's control panel, and give it a static IP address on whichever network you intend to use. While you're there, take a screenshot of the network settings applied to the NAS.

  On 28/03/2017 at 14:26, DaveLegg said:

Try setting the IP on the NAS itself to a static IP, not on the router. Login to the NAS's control panel, and give it a static IP address on whichever network you intend to use. While you're there, take a screenshot of the network settings applied to the NAS.

Expand  

I tried that I think on the initial 1st install, but sure, can do and try. But it should work in dynamic routing anyway. BTW, screenshot of NAS is the in one of the previous post.

  On 28/03/2017 at 18:05, Class said:

But it should work in dynamic routing anyway

Expand  

Huh??

 

Your router is not going to to do any dynamic or static routing.. I have read through this thread a few times now and just can get what your issue is..

 

Put your freaking NAS on the same network PERIOD!! 

 

If your your network is 192.168.1/24 or 192.168.0/24 then your 2 nases need to be on the same network as your other devices.  This is as simple as letting them use dhcp or set them static..

 

Do you have your other old router on the network still running its dhcp server?

This topic is now closed to further replies.
  • Posts

    • PornHub commits to age checks for UK users by 25 July by Paul Hill Ofcom, the UK’s digital regulator, has announced that PornHub and several other porn sites have agreed to put robust age checks in place by the deadline next month on 25 July. The confirmations to Ofcom will likely be used by the regulator against the companies if they fail to comply by the deadline as justification for a fine. The companies that have publicly stated they’re going to have safeguards in place by the deadline are PornHub, BoyfriendTV, Cam4, FrolicMe, inxxx, Jerkmate, LiveHDCams, MyDirtyHobby, RedTube, Streamate, Stripchat, Tube8, and YouPorn. There may be other companies that are preparing, these are just the ones that were happy to be named. Ofcom has been given the task of making sure porn sites comply with age check rules. If companies don’t follow the rules, Ofcom has the power to impose fines and even apply for a court order to ban websites or apps from being available in the UK. These rules are part of the wider Online Safety Act, which aims, in part, to keep children safe online. So far, it has launched investigations into four porn providers for failing to comply with its requests. Oliver Griffiths, Ofcom Group Director of Online Safety said: “Society has long protected youngsters from products that aren’t suitable for them, from alcohol to smoking or gambling. But for too long children have been only a click away from harmful pornography online. “Now, change is happening. These age checks will bring pornography into line with how we treat adult services in the real world, without compromising access and privacy for over-18s.” The new age verification methods come in various shapes and sizes (pun intended) including credit card checks, open banking, and facial age estimation. While these may not keep all kids from accessing porn, they’ll act as a significant hurdle. For adults concerned about handing over information to access porn sites, Ofcom said that the measures do not harm your privacy. All of the age assurance methods are subject to the requirements of UK privacy laws, including on processing personal data. The Information Commissioner’s Office (ICO) is overseeing this area to ensure companies comply. Ofcom’s own studies have found that 3% of 8-9 year-olds have been exposed to online pornography at some point. This highlights how easy it is to find this content and clearly something has to be done. It’ll be interesting to see how these measures actually play out when they get rolled out.
    • Looks like MS is officially extending Windows 10 support while stopping just short of officially changing the end date. I teased in the last article that the process for gaining free support was a little invasive, but this is basically just giving it out for free, so I guess I'm taking back those words.
    • Microsoft shares Windows 10 ESU key guide for office PCs that don't support Windows 11 by Sayan Sen Recently, the Indian government issued a caution about the upcoming end of support for Windows 10 which is about four months away. Interestingly, on that very day, Microsoft made a major announcement regarding this as the tech giant debuted free enrollment options wherein support would be extended for another year at no extra cost. Microsoft is also trying to make it easy to set up Extended Security Updates (ESU) with a new tool. You can see in the image below: New ESU enroll wizard Following that, today, the company has shared a new guide on how to activate ESU via Intune in the case of Windows 10 office PCs that are not supported on Windows 11. First up, Microsoft has reminded users of the prerequisites of Windows 10 ESU: The system needs to be on Windows 10 22H2 with KB5046613 (November 2024 Patch Tuesday) or newer. The device needs access to the network endpoints required for client activation. The process that is used for activation needs administrative privileges on the device. The guide contains several PowerShell scripts and are meant for IT admins and system admins. One of those is a validation script "Check-Win10ESUPrereq.ps1" that Microsoft has published to help "verify a device has the required version and patch level for Windows and it can communicate to the required network endpoints." Essentially, it checks if the aforementioned requirements are satisfied and can be used for troubleshooting against those prerequisites. After the "validation," Microsoft says there are two ways to proceed with the ESU key activation. First. it can be done by either Remediation through: Detection Script (Win10ESUActivation-detect.ps1) and Remediation Script (Win10ESUActivation-remediate.ps1). And second, by Win32 Application with Win32 Install Script (Win10ESU-install.ps1) and Win32 Detection Script (Win10ESU-detection.ps1). In the case of Remediations, Microsoft mentions "some licensing considerations" due to which "some smaller companies may not have that option." Finally, Microsoft has also shared some Activation IDs for manual verification via Slmgr VB script for obtaining volume activation information: Win10 ESU Year1: f520e45e-7413-4a34-a497-d2765967d094 Win10 ESU Year2: 1043add5-23b1-4afb-9a0f-64343c8f3f8d Win10 ESU Year3: 83d49986-add3-41d7-ba33-87c7bfb5c0fb You can check the full guide and the details here on Microsoft's official Tech Community website.
    • It blows me away how overpriced Synology is. $600+ for a 3+ year old SATA NAS with only gigabit networking!! Even for 2022 that is pretty low-end hardware. Yes, the Synology software is fantastic, but if we say this hardware is worth $300 max (and that is even giving a generous premium to the fact that it is made by a respected OEM), their software is NOT worth an additional $300, especially considering it is locked to the hardware it shipped on and you have to pay that premium again for your next device. Important correction to the specs table above. Saying Disk Capacity is 72TB and even going further to detail that is 4x18, strongly implies it comes with those disks, which it does not. I would rather see it say "Max Capacity: 72TB (disks not included)."
    • well again if w11 adoption its so high there's no reason why they try to explain us why is "better" to move to w11. If they are so right about their downgraded UI, why they add some of their UI elements back things like never combine and now small icons. Last time i check majority is still on 10 over 11 so yeah millions of users that did not upgrade to w11
  • Recent Achievements

    • Conversation Starter
      Kavin25 earned a badge
      Conversation Starter
    • One Month Later
      Leonard grant earned a badge
      One Month Later
    • Week One Done
      pcdoctorsnet earned a badge
      Week One Done
    • Rising Star
      Phillip0web went up a rank
      Rising Star
    • One Month Later
      Epaminombas earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      529
    2. 2
      ATLien_0
      207
    3. 3
      +FloatingFatMan
      169
    4. 4
      Michael Scrip
      149
    5. 5
      Steven P.
      123
  • Tell a friend

    Love Neowin? Tell a friend!