• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Cannot ping other devices that are connected to the same ASUS router

Joined
Nov 15, 2013
Messages
143 (0.03/day)
Location
New Zealand
System Name The Beast
Processor Intel Ivy Bridge-E Core i7 4930K 4.4Ghz 12MB LGA2011
Motherboard ASUS Rampage IV Black Edition X79 E-ATX/ Asus B150I Pro
Cooling OVERKILL CUSTOM WATER
Memory 2x Kingston HyperX Beast 32gb 2333mhz (64gb total) / Corsair Vengance 16gb
Video Card(s) 2x GTX 1080ti Poseidon / Evga 780 ti S
Storage 2tb Seagate, 120gb Crucial ssd x2 raid (OS) 3x500gb
Display(s) SAMSUNG LU28D590DS 4K 28" UHD 3840x2160 1ms x3 Resolution 11,520x2160
Case Lian Li DK-02 Desk (ATX & Mini-ATX)
Audio Device(s) Onboard sound, Astro 5.1 headphones and amplifier, THX Surround
Power Supply Corsair HX1000i / Corsair HX750i
Mouse Razer Ouroboros
Keyboard Razor Death stalker ultimate, Razor Orbweaver
Software Windows 10
At a complete wits end. We've got a Asus RT-AX89X router and having issues with connecting to devices via other devices.

I have acouple aquarium controllers i want to control and monitor and have set a fixed ip address. They're connected to the same router as all the other devices. Everything is connected to the internet (wasn't last week but i think that was an issue internally with a silent update overloading the RAM??) ie i can connect to the device via the cloud but not by searching the ip address. When i ping in via command prompt or try find it on my phone its unreachable, however when i ping it through the router its responsive and connected.

Any help on the matter would be greatly appreciated!
 
Wireless separation turned on?
 
Wireless separation turned on?
Sorry not sure where to find that. having a look now :) not the most networking savoy joe-blogs

Wireless separation turned on?
My router has what's called set AP isolated. This use to be on when i had issues but have changed to off. Note- some times it does connect when i search the ip address. very random times however
 
My router has what's called set AP isolated. This use to be on when i had issues but have changed to off. Note- some times it does connect when i search the ip address. very random times however

this is a problem, isolation must be off or the subnets will be seperated.


some times it does connect when i search the ip address. very random times however

and this is because your static addresses are probably set within your DHCP range and you have multiple devices jockying for the same address.

You need to adjust your DHCP range and carve out like a block of 10 or so addresses. Then assign the devices you want to control a static IP within that block.

Then your problems will go away, or we can move onto the device/router firewall which will be its own battle.

First things first you have to figure out connectivity before all those potential problems though.
 
Yes, just a different term for the same thing. AP isolation = wireless separation = security method so that wireless devices cannot see, snoop, or connect to local LAN and router only offers internet connection to each device.
 
This


Page 67

Steps 4 and 5.

You want to leave step 5 alone. The ending address.

Instead. In step 4 the starting address. Is probably something like. 192.168.0.1

You need to change this to something like 192.168.0.11

This will give you addresses 2-10 to do whatever you want with. You need to assign the devices you want to have static addresses for within the .2-.10 range.

This will stop the DHCP server from issuing them to things like TVs and gamboys and you will stop only connecting to them "sometimes".

dont let anyone trick you into doing DHCP "Reservation" thats lazy and causes all sorts of issues.

  • Some DHCP servers dont support mac bonding
  • Some devices dont respect static mac and use methods to bypass
  • Some lazy DHCP servers utilize host names
  • Devices change hostnames

Set a static block in the DHCP server range and move on with life.
 
Last edited:
this is a problem, isolation must be off or the subnets will be seperated.




and this is because your static addresses are probably set within your DHCP range and you have multiple devices jockying for the same address.

You need to adjust your DHCP range and carve out like a block of 10 or so addresses. Then assign the devices you want to control a static IP within that block.

Then your problems will go away, or we can move onto the device/router firewall which will be its own battle.

First things first you have to figure out connectivity before all those potential problems though.
This


Page 67

Steps 4 and 5.

You want to leave step 5 alone. The ending address.

Instead. In step 4 the starting address. Is probably something like. 192.168.0.1

You need to change this to something like 192.168.0.11

This will give you addresses 2-10 to do whatever you want with. You need to assign the devices you want to have static addresses for within the .2-.10 range.

This will stop the DHCP server from issuing them to things like TVs and gamboys and you will stop only connecting to them "sometimes".

dont let anyone trick you into doing DHCP "Reservation" thats lazy and causes all sorts of issues.

  • Some DHCP servers dont support mac bonding
  • Some devices dont respect static mac and use methods to bypass
  • Some lazy DHCP servers utilize host names
  • Devices change hostnames

Set a static block in the DHCP server range and move on with life.
:confused::confused:

Ahh yes the thermal dynamic dingle arm. Sorry im very confused here lol.

So, the DHCP is turned on

Set for a range of 192.168.50.10 - 192.168.50.254
Profilux (device 1) set to 192.168.50.2
Mitras (device 2) set to 192.168.50.3

After the change it has WORKED!. Even though i had already set the ip address as fixed and matched them, the unit is stupid enough to try set the address to another device as the same? assuming when it has a matched ip address at some point it stops the communication locally as its a little scrambled? maybe ? idk. Will keep trying tonight to make sure. Have set the two devices to obtain address automatically. was advised to do this by another fish keeper. Think its a good idea? or static it aswell?

While we are here anything else i should be checking? really appreciate it :)
 
dont let anyone trick you into doing DHCP "Reservation" thats lazy and causes all sorts of issues.
:( Total nonsense!

Lazy? Not even!

Just because something is simple and effective, that does not mean it is the lazy way out. If done correctly, DHCP Reservations is very easy, efficient and trouble-free and is especially advantageous if you prefer to centrally manage your entire network from a single location.

If you have networked printers or a NAS (network attached storage), as examples, that you want all your computers to have access to, "Reserving" an IP address for those devices works great. It is an effective network management solution at your disposal. You can use it to prevent your computers from losing track of those devices after extended power outages that may result in such devices being reassigned a different IP address via DHCP.

Static IP assignment is "old school". It works but is not the only, or always best solution. Network administrators who have an understanding of DHCP, have been using DHCP Reservation solution for years without causing "all sorts of issues". :( In fact,

As an example, if you have (or will have) 10 devices (computers, smart phones, tablets) that may need access to your networked printer, you can set your starting address to something like 192.168.1.10 and your ending address to 192.168.1.19. If you occasionally have visitors (kids, grandkids) come over who need access, you can make your ending address 192.168.1.25. Note this also limits the number of devices that can access your network - like nosey neighbors.

Then you can "reserve" 192.168.1.35 for your printer and set up all your computers to access the printer via that IP address. From that point on, whenever your router sees your printer come on line, it will always assign it the .35 address, and never assign it to any other device.

Note Static IP address assignment, while similar, is different from a DHCP Reservation. With a Static IP, it must be set up individually in the NIC (network interface card) of each computer. Static IP addresses work great in large networks for devices like servers, network managed switches, POS (point of sale) computers. But you have to set the Static IP address within the menu system of each device. This means you have to visit each device, navigate each device's menu system, then set the IP address.

With a Static IP address assignment, the computer says, "give me this address every time".

With DHCP Reservations, everything is done in one central location - the router's admin menu. So, when a device connects, the router says, "I see you and here's your Reserved IP address I have saved just for you."

All you need to setup DHCP Reservations is the MAC address for the device. If the device is already connected to your network, you typically can see the MAC address in the router's admin menu under "Connected devices" (or something similar). If a brand new device, there should be a sticker on the device or its box with the MAC address.

Do note you can use both Static and DHCP Reservations (or neither) on the same network. It is not one or the other.

I recommend everyone setting up a network, regardless of size, and trying to decide whether to use Static or DHCP IP assignment to take the time to learn and understand the advantages (and convenience and efficiencies), and disadvantages to using DHCP Reservations. Here is an excellent article and video (which goes into a little more depth): Static IP vs DHCP Reservation.
 
After the change it has WORKED!. Even though i had already set the ip address as fixed and matched them, the unit is stupid enough to try set the address to another device as the same?
See it wasn’t so bad! Glad you got it working!

the unit is stupid enough to try set the address to another device as the same?
yes while I didn’t read the tangent bill went on about above I spent some of my career doing some networking in environments in the 10’s of thousands. As my bullet points mentioned dhcp reservation can cause issues as it’s a roll of the dice as to how nice the dhcp server or device will play.

No one in professional space uses reservation and that is pretty common across all the companies and industries iv worked in.

Will keep trying tonight to make sure. Have set the two devices to obtain address automatically. was advised to do this by another fish keeper. Think its a good idea? or static it aswell?
Anything you want to be able to talk to because it serves a purpose like a thermostat or in your case controllers should be static and inside that range you cut out for yourself.

glad you got it sorted nice job!
 
:rolleyes: I didn’t read the tangent bill went on about above I spent some of my career doing some networking
Too bad you could not make the effort. You could have learned what you are talking about.

No one in professional space uses reservation
More nonsense. While perhaps not widely used by many old-timers (and I am one too) who, perhaps, may be stuck in their ways, many IT pros are learning it can be very useful and advantageous. The example illustrated in the video with large numbers of wireless APs in a very large warehouse was a perfect example.

in environments in the 10’s of thousands.
And you think the administration of networks with 10s of 1000s of nodes, managed by true IT professionals, scales down to typical home size networks? :rolleyes:

I spent some of my career doing some networking
And that's great! No doubt your 10,000 node networks worked very well. But as seen via the link in my signature, I have a bit of network experience too - enough to know folks in the profession who use DHCP Reservations don't do it because they are "lazy", nor do they experience "all sorts of issues".

@Nossy - I too am glad you got it working. I only ask you keep an open mind about other, viable, efficient, and very effective alternative solutions.
 
Last edited:
Too bad you could not make the effort. You could have learned what you are talking about.


More nonsense. While perhaps not widely used by many old-timers (and I am one too) who, perhaps, may be stuck in their ways, many IT pros are learning it can be very useful and advantageous. The example illustrated in the video with large numbers of wireless APs in a very large warehouse was a perfect example.


And you think the administration of networks with 10s of 1000s of nodes, managed by true IT professionals, scales down to typical home size networks? :rolleyes:


And that's great! No doubt your 10,000 node networks worked very well. But as seen via the link in my signature, I have a bit of network experience too - enough to know folks in the profession who use DHCP Reservations don't do it because they are "lazy", nor do they experience "all sorts of issues".

@Nossy - I too am glad you got it working. I only ask you keep an open mind about other, viable, efficient, and very effective alternative solutions.

Fully all for the open mind. Many ways to skin a cat.

What is the difference between a fixed ip address and a rhcp reservation? Turns out I had to add my ip address and mac address to fix the ip... but since it's under the rhcp menu I suspect its actually a reservation.
 
If by fixed you mean Static, I recommend you check out the link and video from the last line of my post #8 above. Stephen Wagner is a respected Canadian IT consultant and provides a great explanation of the differences, and pros and cons of both solutions.

Also, Google can provide many sources that explain the difference. But the basic difference is, Static IP addresses are configured manually, directly on each client. Reserved IP addresses are configured at and leased from the DHCP server (typically the router), but the given client will always receive the same IP address.
 
Back at it again, the solution of dropping the static ip to lower than the routers automatically addressable range worked for about a month.

Reading over the forum/answer now for another option. I find it odd that it's stopped again. SUPER FRUSTRATING. Will post if I have a fix.
 
Back at it again, the solution of dropping the static ip to lower than the routers automatically addressable range worked for about a month.

Reading over the forum/answer now for another option. I find it odd that it's stopped again. SUPER FRUSTRATING. Will post if I have a fix.
How do you assign static IPs? As there are two ways.
The old way is now obsolete in terms of, it shouldn't be used and that's setting the IP address manually on the device.
Instead, try using IP reservations in the router.
Doing it this way, the DHCP server will never assign that IP address to any other device, as the router will be aware of the devices using the reserved IP addresses.
 
How do you assign static IPs? As there are two ways.
The old way is now obsolete in terms of, it shouldn't be used and that's setting the IP address manually on the device.
Instead, try using IP reservations in the router.
Doing it this way, the DHCP server will never assign that IP address to any other device, as the router will be aware of the devices using the reserved IP addresses.
Yerp this is what I done the first time which worked for approximately a month.

The device is an aquarium controller. 99% of the time I don't have issues with the router connecting to it directly, but I cannot see it via any other device.

It has 3 methods to connect. USB, Direct local via IP (in app or Internet search bar) or cloud. I can ping it via the router, but not via any other device.

This is an issue because I need to be able to configure the unit and it's near on impossible via cloud. ( configure as in program the aquarium, basic changes ie settings and networking are ok)

Yerp this is what I done the first time which worked for approximately a month.

The device is an aquarium controller. 99% of the time I don't have issues with the modem connecting to it directly, but I cannot see it via any other device.

It has 3 methods to connect. USB, Direct local via IP (in app or Internet search bar) or cloud. I can ping it via the modem, but not via any other device.

This is an issue because I need to be able to configure the unit and it's near on impossible via cloud. ( configure as in program the aquarium, basic changes ie settings and networking are ok)
As I check incase I've forgotten something here, thesw are the controller pages.

They align with the modem and they're connected to the Internet.

The first photo is of my router
The second photo is the android app ip settings
The third photo is the controller and it's connected ip address and the two connections
The fourth photo is the actual network settings.

Tia
 

Attachments

  • Screenshot_20230821_005535_Chrome.jpg
    Screenshot_20230821_005535_Chrome.jpg
    359 KB · Views: 190
  • Screenshot_20230821_011025_GHL Connect.jpg
    Screenshot_20230821_011025_GHL Connect.jpg
    141.5 KB · Views: 166
  • Screenshot_20230821_011130_GHL Connect.jpg
    Screenshot_20230821_011130_GHL Connect.jpg
    245.3 KB · Views: 143
  • Screenshot_20230821_011134_GHL Connect.jpg
    Screenshot_20230821_011134_GHL Connect.jpg
    169.6 KB · Views: 147
Last edited:
i like to keep DHCP reservation for my main desktop as i wirelessly transfer files from my camera, phones, tablet etc and many more. Otherwise its a PITA.

and JFC bill you need to keep your replies short. even if you have a good point its really difficult to even want to read it after looking at a wall of text.
 
Reading the thread, it looks like once I upgrade the home router I've got some homework to do :nutkick:
 
Too bad you could not make the effort. You could have learned what you are talking about.


More nonsense. While perhaps not widely used by many old-timers (and I am one too) who, perhaps, may be stuck in their ways, many IT pros are learning it can be very useful and advantageous. The example illustrated in the video with large numbers of wireless APs in a very large warehouse was a perfect example.


And you think the administration of networks with 10s of 1000s of nodes, managed by true IT professionals, scales down to typical home size networks? :rolleyes:


And that's great! No doubt your 10,000 node networks worked very well. But as seen via the link in my signature, I have a bit of network experience too - enough to know folks in the profession who use DHCP Reservations don't do it because they are "lazy", nor do they experience "all sorts of issues".

@Nossy - I too am glad you got it working. I only ask you keep an open mind about other, viable, efficient, and very effective alternative solutions.
Any other ideas Bill?
 
How do you assign static IPs? As there are two ways.
The old way is now obsolete in terms of, it shouldn't be used and that's setting the IP address manually on the device.
Instead, try using IP reservations in the router.
Doing it this way, the DHCP server will never assign that IP address to any other device, as the router will be aware of the devices using the reserved IP addresses.

Just clarifying. Since these guys don't appear to be network engineers (just journalists I guess) for anyone that finds this thread. This advice is literally terrible. Especially for your iphone, macbook, or VM guys since reservation relies on MAC address binding. So the nifty iOS security features or rotating mac addresses of VMs will break these reservations in AD or BIND (which is usually what is running under the hood controlling dhcp on consumer *nix based routers) and really ruin your day (likely why OP said his IP is broken again.

In my experience, it's better if you put them outside of the DHCP IP address pool.
For example, I've had my NAS on 192.168.1.250, the printer on 192.168.1.249 and the DHCP lease pool going from 192.168.1.10 to 192.168.1.100.
192.168.1.1 being the DCHP server/main router and other devices below the lease start being other networking devices.

weird since what is being described is not DHCP reservation :)
 
Last edited:
Just clarifying. Since these guys don't appear to be network engineers (just journalists I guess) for anyone that finds this thread. This advice is literally terrible. Especially for your iphone, macbook, or VM guys since reservation relies on MAC address binding. So the nifty iOS security features or rotating mac addresses of VMs will break these reservations in AD or BIND (which is usually what is running under the hood controlling dhcp on consumer *nix based routers) and really ruin your day (likely why OP said his IP is broken again.



weird since what is being described is not DHCP reservation :)
I originally followed your instruction, but maybe I've missed something or gotten confused along the ole bumpy road. Any tips or advice before I go for a very very long swim in the aquarium?
 
I originally followed your instruction, but maybe I've missed something or gotten confused along the ole bumpy road. Any tips or advice before I go for a very very long swim in the aquarium?

hmmmmmmm on a whim can you reboot those two devices (not the router) and see if they work again? Can you tell me about how long its been since the devices and the router have been powered up?
 
hmmmmmmm on a whim can you reboot those two devices (not the router) and see if they work again? Can you tell me about how long its been since the devices and the router have been powered up?
Unfortunately not atm I can reset them in approximately 4.5 hours.

They would've been powered on since the last fix so 21st of May. After I got it working I power cycled it to ensure it found the correct address again.
 
Unfortunately not atm I can reset them in approximately 4.5 hours.

They would've been powered on since the last fix so 21st of May. After I got it working I power cycled it to ensure it found the correct address again.

hmmmmmmmm if it worked for "about a month" meaning a little over I am curious if resetting the devices fixes it especially if the router can still chat with it, but the device cant chat back. That is not an IP issue if the device can be pinged.

There is an issue, with older SCADA software and devices, that I have ran into. It happens with some from what iv seen old IoT devices (maybe your devices are an unfortunate exception). If the uptime of the device is calculated as a 32bit intiger then there is a magic number of hours, usually over a month and a half where the uptime value will overflow and the device will become unresponsive.

If resetting the device (unplug plug in) with no change to the router fixes it, then its a device firmware problem.

As you said, the router can still communicate with it, so you have done nothing wrong.
 
Just clarifying. Since these guys don't appear to be network engineers (just journalists I guess) for anyone that finds this thread. This advice is literally terrible. Especially for your iphone, macbook, or VM guys since reservation relies on MAC address binding. So the nifty iOS security features or rotating mac addresses of VMs will break these reservations in AD or BIND (which is usually what is running under the hood controlling dhcp on consumer *nix based routers) and really ruin your day (likely why OP said his IP is broken again.



weird since what is being described is not DHCP reservation :)
Just maybe worth a note.

I can connect to it via cloud based connection and there is no issue with the unit being connected to the router. It's simply I cannot locate it via a search from a pc/cellphone from the same network. I think this issues with the lack of connect was an issue with an incorrect set ip.

Thanks again for all your help though. Really appreciate it. Slightly in over my head
 
Just maybe worth a note.

I can connect to it via cloud based connection and there is no issue with the unit being connected to the router. It's simply I cannot locate it via a search from a pc/cellphone from the same network. I think this issues with the lack of connect was an issue with an incorrect set ip.

Thanks again for all your help though. Really appreciate it. Slightly in over my head

there are multiple services driving discovery. I would still be curious if a reset fixes it.

EDIT:: Are you trying to access these devices by name? or by IP from your PC/cell when on the same network?
 
Back
Top