Desktop is connected, but does not show up in Router map


Recommended Posts

One of the desktops in our home network has the assigned address 192.168.1.4 and has a name of Cassie-PC, which responds via ping, but I need to setup parental controls on it (it's me niece's) and it does not show up in the network map through the router. I have physically checked the address assigned to the system, and it is clearly set to the .4 address, but it does not show up as an attached device in the router. Why is this, and what can I do to resolve it? For what's it worth I have checked and the cable is plugged directly to the router, prior it was plugged into a dumb switch. The desktop in question is able to access everything on the LAN as well as the internet.

241716340_networkmap.thumb.PNG.ebd479bd7b58ec582f6093898d11f55d.PNG

Hello,

 

I'm not particularly familiar with how Linksys does this, but could it be that the Cassie-PC host computer at 192.168.1.4 has a firewall on it which prevents the router from fingerprinting it?
 

I am thinking that as a work-around, you could try cloning the computer's MAC address, IP address and hostname onto one of the recognized devices, set up filtering for it on the router, and then restore that device's prior settings?  Again, I'm not sure if this would be effective, given that the Linksys router does not see the Cassie-PC computer, but perhaps once you have manually created an entry for it, the router will enforce the parental controls.

 

Just to confirm, you have visited Linksys to ensure you have the latest firmware?

 

Regards,

 

Aryeh Goretsky

  On 22/01/2019 at 02:34, goretsky said:

Hello,

 

I'm not particularly familiar with how Linksys does this, but could it be that the Cassie-PC host computer at 192.168.1.4 has a firewall on it which prevents the router from fingerprinting it?
 

I am thinking that as a work-around, you could try cloning the computer's MAC address, IP address and hostname onto one of the recognized devices, set up filtering for it on the router, and then restore that device's prior settings?  Again, I'm not sure if this would be effective, given that the Linksys router does not see the Cassie-PC computer, but perhaps once you have manually created an entry for it, the router will enforce the parental controls.

 

Just to confirm, you have visited Linksys to ensure you have the latest firmware?

 

Regards,

 

Aryeh Goretsky

Expand  

I will check into the MAC address, the firmware is up to date, as far for firewall, only the windows firewall is installed on that system.

Seems to be common across Linksys routers with this "feature."

 

Try power cycling the router

Try viewing the GUI in a different browser

You can try downgrading to the previous firmware and see if that solves it

 

However, it might be worth your while to look into 3rd party firmware if you cant get this to work fairly soon. Some users have reported to get it working again, only to have the issue pop up again randomly. If you are dead set on the Linksys firmware, you might want to look into other parental control solutions. I don't know of any myself, however I bet others here do.

Why can you not setup a reservation for the device on dhcp so its always .4 or set the device static on the PC... Then set the parental controls based upon the IP address?

 

If you setup a dhcp reservation for the PC mac address, it should be ALWAYS listed!!!

 

 

  On 22/01/2019 at 11:26, BudMan said:

Why can you not setup a reservation for the device on dhcp so its always .4 or set the device static on the PC... Then set the parental controls based upon the IP address?

 

If you setup a dhcp reservation for the PC mac address, it should be ALWAYS listed!!!

 

Expand  

That is the plan now, I was not aware that it was not setup (dhcp reservation) until late last night when I mentioned it to my brother-in-law, then we both realized that we never set her system up that way, we are going to correct the issue today.

OK, so apparently the desktop in question was on the DHCP reservation table, and I went ahead and gave it an assigned IP address of 192.168.1.4, but it still will not show up on the router, and the router has been reset, twice, so what else can I try?

Might be a long shot, but try reinstalling those drivers on the desktop. Or you could try it with a Live Linux CD/USB, and see if it shows up then. If it does, it's the ethernet port driver thats sending out bad info.

 

  On 22/01/2019 at 21:32, Mindovermaster said:

Might be a long shot, but try reinstalling those drivers on the desktop. Or you could try it with a Live Linux CD/USB, and see if it shows up then. If it does, it's the ethernet port driver thats sending out bad info.

 

Expand  

Odd since the system is brand new, but when I get a chance I will try to diagnose it further.

  On 22/01/2019 at 21:46, jnelsoninjax said:

Odd since the system is brand new, but when I get a chance I will try to diagnose it further.

Expand  

Odd is never a word when troubleshooting. The stupidest reason can be the answer... ;) 

  On 22/01/2019 at 21:21, jnelsoninjax said:

OK, so apparently the desktop in question was on the DHCP reservation table, and I went ahead and gave it an assigned IP address of 192.168.1.4, but it still will not show up on the router, and the router has been reset, twice, so what else can I try?

Expand  

You might not ever fix this, it seems like a ###### poor implementation from what I can gather. Search google for something as simple as "Linksys+Network Map+Missing Device" and you'll start seeing the threads I mentioned.

 

Try power cycling the router

Try viewing the GUI in a different browser

You can try downgrading to the previous firmware and see if that solves it

 

If none of that works, contact Linksys as this seems to be a firmware bug (I read this many times on the linksys forums).

Hello,


Oh, did you check to see if the computer is randomizing its MAC address on network connections with DHCP leases?  Perhaps that could interfere with fingerprinting by the router.

 

Regards,

 

Aryeh Goretsky

That their software doesn't allow you to assign policy based upon IP is just plain moronic... Since clearly whatever they are using for discovery of devices is junk..

 

As already mentioned a simple google shows that is a very common problem with their software.. If their discovery of devices on the local network is this flawed - why would you expect their control policies to work any better?

 

What exactly are you wanting to do and can prob point you to actual method that works ;)  Filter a machines internet access based upon what exactly?  No p0rn, no non approved sites? what?

 

Do you know how they discover devices?  Normally this would be done with arp, since even firewalls don't block answering arp.   A reservation for a MAC should force it to be listed.. As mentioned you sure the mac is correct in the dhcpd reservation?  Maybe that was setup for the devices wifi, and now your on wire?

 

Validate the devices mac address currently be used.. Windows simple ipconfig /all will show you this.. And then validate that mac is what is listed in your reservation on your router.

speaking as someone that owns a Linksys WRT1900AC I can tell you that their software and policy control is rather flaky; sometimes things work as expected and other times random features/policies just refuse.

 

I moved over to LEDE (now merged back into OpenWRT) and besides being much more stable I'm able to do more with it than I would have been able to.

I have a hard drive plugged in and shared locally and an Aria2 download server pointed to it running directly on the router now; built in ad blocking; and a few other things

  On 23/01/2019 at 13:59, BudMan said:

That their software doesn't allow you to assign policy based upon IP is just plain moronic... Since clearly whatever they are using for discovery of devices is junk..

 

As already mentioned a simple google shows that is a very common problem with their software.. If their discovery of devices on the local network is this flawed - why would you expect their control policies to work any better?

 

What exactly are you wanting to do and can prob point you to actual method that works ;)  Filter a machines internet access based upon what exactly?  No p0rn, no non approved sites? what?

 

Do you know how they discover devices?  Normally this would be done with arp, since even firewalls don't block answering arp.   A reservation for a MAC should force it to be listed.. As mentioned you sure the mac is correct in the dhcpd reservation?  Maybe that was setup for the devices wifi, and now your on wire?

 

Validate the devices mac address currently be used.. Windows simple ipconfig /all will show you this.. And then validate that mac is what is listed in your reservation on your router.

Expand  

It is setup in the DHCP reservation complete with MAC address filtering:

ShadzStore is the NAS

dhcp.thumb.PNG.8e36f10c6225f4d27702b86aeb8fc01b.PNG

Not sure how that answers my question.. Is the device that is not showing up actually using that mac?

 

That mac for 1.4 just comes back as ASUSTek COMPUTER INC., so is that the wireless or the wired nic?  And how is the device currently connected?

  On 24/01/2019 at 03:55, BudMan said:

Not sure how that answers my question.. Is the device that is not showing up actually using that mac?

 

That mac for 1.4 just comes back as ASUSTek COMPUTER INC., so is that the wireless or the wired nic?  And how is the device currently connected?

Expand  

The device is wired via cat5 to the router and the motherboard is an Asus, it does not show up in the network map, but as I showed, it does show (even MAC address) under DHCP reservations,

@Circaflex I tried to access the GUI via Edge, and it does not work at all (won't even load, no error, just does not connect)

  On 24/01/2019 at 11:47, jnelsoninjax said:

it does show (even MAC address) under DHCP reservations,

Expand  

And you actually validated this on the machine that that is the actual MAC??

 

it HAS to show the mac address on a reservation, since that is how it works!!  But for all we know someone set the static IP on the device to .4 and setup a reservation for wrong mac..   Maybe they setup that reservation for the wireless mac or something.

 

On the machine do a ipconfig /all and what does it show for the mac address?  For the interface currently being used?

 

macaddress.thumb.png.31c70b27cff8646c3b557ebf7924a377.png

 

Or maybe the mac is correct, but device is set static and never pulled the lease so the router doesn't think there a machine there because no lease was ever gotten for its reservation.  Does the device show dhcp is being used.. See I have it OFF on mine and IP is setup static..  

 

Do a ipconfig /release and then renew on the machine so your sure its pulling the lease from the router..

  On 24/01/2019 at 13:54, BudMan said:

And you actually validated this on the machine that that is the actual MAC??

 

it HAS to show the mac address on a reservation, since that is how it works!!  But for all we know someone set the static IP on the device to .4 and setup a reservation for wrong mac..   Maybe they setup that reservation for the wireless mac or something.

 

On the machine do a ipconfig /all and what does it show for the mac address?  For the interface currently being used?

 

macaddress.thumb.png.31c70b27cff8646c3b557ebf7924a377.png

 

Or maybe the mac is correct, but device is set static and never pulled the lease so the router doesn't think there a machine there because no lease was ever gotten for its reservation.  Does the device show dhcp is being used.. See I have it OFF on mine and IP is setup static..  

 

Do a ipconfig /release and then renew on the machine so your sure its pulling the lease from the router..

Expand  

Thanks for the help so far @BudMan, when I get a chance (most likely this weekend) I will look into the issue more. Question: when assigning the system a static IP, is it better to let the router do it, or do it via Windows? Right now I am thinking that the issue might be like you said and I know that the .4 address is set via the network control panel in windows, should I set it to automatic and let the router handle assigning the IP address?

  On 24/01/2019 at 23:51, jnelsoninjax said:

Thanks for the help so far @BudMan, when I get a chance (most likely this weekend) I will look into the issue more. Question: when assigning the system a static IP, is it better to let the router do it, or do it via Windows? Right now I am thinking that the issue might be like you said and I know that the .4 address is set via the network control panel in windows, should I set it to automatic and let the router handle assigning the IP address?

Expand  

Remove the entry from the Windows control panel and use DHCP reservation's on your router.

  On 24/01/2019 at 23:57, Circaflex said:

Remove the entry from the Windows control panel and use DHCP reservation's on your router.

Expand  

OK, that's what I will do, I am not sure why it is set in windows and the router, it was most likely an oversight on my part when I was troubleshooting.

Well if how the system finds your machine is via it grabbing a dhcp lease.. The setting it on the machine is not going to be good for you ;)

 

I normally run dhcp but you see above its static set because haven't gotten around to setting up new reservations as of yet, when I changed out nics and put in 2 so I could do smb3 multichannel.  I only showed the 1 there is another one with .101, but I don't have a gateway set on that interface because I don' want it used for outbound.  Only for talking smb3 multichannel to the NAS which is on the same vlan as my pc.

Hello,

 

This may be a silly question, but I don't think I saw it mentioned, so apologies in advance if this is a duplicate.

 

Have you contacted Linksys' technical support to see if there are any known issues with detecting PCs?  There might be something about the what it fingerprints the computer based on its networking stack or the NIC itself which prevents it from detecting it.

 

Another option might be to look at third-party firmware, as @Circaflex mentioned, or even install parental control software on the PC (which might be a non-starter is the user has administrative access).

 

Regards,

 

Aryeh Goretsky

 

  On 25/01/2019 at 19:38, goretsky said:

Hello,

 

This may be a silly question, but I don't think I saw it mentioned, so apologies in advance if this is a duplicate.

 

Have you contacted Linksys' technical support to see if there are any known issues with detecting PCs?  There might be something about the what it fingerprints the computer based on its networking stack or the NIC itself which prevents it from detecting it.

 

Another option might be to look at third-party firmware, as @Circaflex mentioned, or even install parental control software on the PC (which might be a non-starter is the user has administrative access).

 

Regards,

 

Aryeh Goretsky

Expand  

No, I have not contacted Linksys over this issue, I thought I would try my luck here, first. Regarding 3rd party firmware, I haven't looked into it, but I know that was one of the selling points on this router, and parental control software would not work because she has admin access, her dad st this up for her.

Some of the Linksys routers actually come with OpenWRT on them now, I know the WRT32X does (to my surprise, was wonder what the hell device on my network was running OpenWRT as I didn't install it lol...)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yeah what can you expect in the first 4 years?? Where on your body is the Zune tattoo?
    • Microsoft still tries really hard to convince people about Windows 11. It does not realize, the harder it tries the more people hate it. And it is not people's fault. It is MS that tries violently to own your computing environment without your consent. Cheers MS!
    • I've got a basic black and white laser printer that's connected via USB and doesn't do wifi etc. I think I'm going to be just fine.
    • Edge 138 is out with AI-powered history search and other changes by Taras Buria Microsoft has released Edge 138, the latest major update for the browser. Version 138.0.3351.55 introduces some interesting changes and new features, such as AI-powered history search. There are also several bug fixes and security patches. For regular users, the biggest and most important change in Edge 138 is AI-powered history search. This feature allows you to find sites in your history using synonyms, phrases, or misspelled words. Microsoft uses an on-device model, which does not send your data anywhere. Note that this feature is rolling out gradually, which means it might take a few days or weeks to show up on your system. Another useful change is new performance notifications. Performance and Extensions Detector notifications may appear in the main menu when the browser detects performance dips to help users learn about available performance-optimization tools. Autofill settings received a new consent toggle, which allows Microsoft to improve the autofill capabilities by collecting field names as you browse. This only applies to field names, such as "First Name, "Email," etc. It does not send the data you enter or autofill to Microsoft. Other changes include the following: Use the Primary work profile as the default profile to open external links. With this feature, for Windows, Edge checks if the Primary Work Profile exists and makes it the default profile for opening external links if available. Microsoft 365 Copilot Chat Summarization in Microsoft Edge Context Menu. This feature helps users quickly unpack and ask questions about their open page. Copilot on the Microsoft Edge New Tab Page (NTP). Users may see suggested work and productivity-related Copilot prompts in their search box on the NTP page. Adding support for viewing Sensitivity labels applied to a Microsoft Information Protection (MIP) Protected PDF. Enterprise customers can view sensitivity labels applied to MIP protected PDF to be well informed of the data classification to enable them to handle such sensitive documents. And here is what was fixed: Fixed an issue that caused WebDriver automation to fail in Microsoft Edge versions 133 and later. Fixed an issue where re-enabled textarea elements remained non-editable. This issue affected activating a role assignment in Privileged Identity Management. Finally, Edge 138 patches six security vulnerabilities, three of which were Microsoft Edge-specific, and the remaining three originated from Chromium. You can find details about those fixes here. The next Microsoft Edge update, version 139, is expected in the week of August 7, 2025.
    • “Never trust any statistics that you didn't forge yourself.”
  • Recent Achievements

    • Week One Done
      suprememobiles earned a badge
      Week One Done
    • Week One Done
      Marites earned a badge
      Week One Done
    • One Year In
      runge100 earned a badge
      One Year In
    • One Month Later
      runge100 earned a badge
      One Month Later
    • One Month Later
      jfam earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      564
    2. 2
      +FloatingFatMan
      177
    3. 3
      ATLien_0
      169
    4. 4
      Michael Scrip
      125
    5. 5
      Xenon
      122
  • Tell a friend

    Love Neowin? Tell a friend!