Disable the "Enable Automatic IPv6 Address Assignment:" box?I would start with "3" and disable IPv6.
Once IPv6 is disabled then all other relevant configuration settings with respect to IPv6 become moot.
Okay... I turned off Enable Automatic IPv6 Address Assignment and it seems to be on still...? Also yes, IPV4 is still enabled View: https://imgur.com/a/Z4viiu9Yes.
Be sure to keep track of what you change , where you make the change, along with the original and new value.
One change at a time.
Also, looking back at your "ipconfig /all" results - ensure that IPv4 is enabled.
oh, i just moved to mobile for bed, but I will do a scan soon when I can... Also, my stepdad has ordered yet another router, should I reset the settings on the D-link one before this arrives?? It hasn't arrived yet, but this is what he ordered https://www.amazon.com/dp/B08KTXG8Q5?ref=ppx_yo2ov_dt_b_fed_asin_title is it good?Run and post the full results of "ipconfig /all" again without redacting any private IP addresses.
(Reference the Lifewire links for further explanation.)
IP addresses (along with macs) are a key part of network troubleshooting. There could be any number of mismatches due to router and/or other network configuration errors.
And if you do not have full admin rights to the router or any given network device you may not be able to make any network related configuration changes.
Take a screenshot of the IPv4 "Internet" screen along with the IPv4 settings. Post accordingly.
Hi, sorry for the late reply again... We got the router the other day, and the internet works like normal, minus the calling issue still being there... I haven't changed any of the router's settings so farThe first and foremost question is whether or not that NetGear Router is supported by your ISP?
I would hope so but you/he should check the ISP's website list before doing anything.
And I believe that more investigating and troubleshooting is necessary to discover what the current problems may be.
At this time it is going to take a great deal of methodical and planned effort to figure things out. Still unsure about the extent of the full network, its' devices, and corresponding configuration settings.
Especially if the problems are configuration related. A "good" router of any make and model will be problematic if the router and other network devices are not correctly setup and configured.
As for resetting the D-Link: same difference. A reset simply returns that router to its' default/factory configuration. Any devices not set to match that configuration will not or no longer be able to join the network and/or obtain internet access. Things may get worse.
Besides "ipconfig /all" run "arp -a" as well via the Command Prompt. Post both results.
(Redact personal name information.)
You need to know (not necessarily to post) each network device, its' name, the IP address it is using, its' mac, and how the device is connected to the network (wired, wireless).
Also google something like "How to set up a home network" to look for tutorials etc.. Limit to the last year or so.
Read through or watch any that you feel comfortable with.
Objective simply to help you and your stepdad gain sense of the "big picture" and all that you must understand and do when managing your own home private network.
Hi again, sorry for my late reply 🙇♀️ ... I haven't changed any settings, alsoDifficult to determine much at all.
You redacted out the private network IP addresses and MACs.
And the current DNS Server IP addresses.
Suggestions:
Ensure that no other devices are using the same IP address.
= = = =
All other devices working and communicating as expected and required - correct?
If so - leave roaming agressiveness alone...
If it is only the tablet (confirm which tablet) being funky then look at that tablet's configuration and compare that configuration to other devices where all is working.
UDP is going out of my comfort zones with respect to many of the details, etc..
FYI:
https://www.geeksforgeeks.org/user-datagram-protocol-udp/
Just for some background information.
There are various ways to check and test UDP.
Ideally targeting the tablet of concern.
I read through most of it, I didn't understand it entirely, but I did google one thing to do when having a double NAT is that some people like to enable Access Mode on their router (or AP mode in my case) ...That was a huge mistake... I basically got entirely booted offline and had to factory reset everything 😵😵😵😵😵😵NAT - more than I can explain or type...
Start here:
https://computer.howstuffworks.com/nat.htm
As a general observation the problem(s) could be due to "double NAT".
https://www.nextiva.com/support/articles/what-is-double-nat.html
Reading back, my thought is that you are now likely have a far better understanding of your network, its's devices, and general configuration.
The two links above may help you understand more about what might be happening and, more importantly, find and fix the problem.
And there are many other similar explanations and tutorials online.
Just do not be tempted into downloading any apps etc. claiming to find and fix the problem.
Likewise, stay out of the registry.
Ahh, okay... just to make sure, can you tell me which of these to censor exactly on the MAC? I'm more of a visual learner.. (Which of the example 9s would be censored)Unfortunately, such things happen and you and/or your actions are not necessarily to blame.
There is a considerable amount of misinformation on the internet and in some cases is based on the general and not the specific.
Overall, it can still be sorted out To do that you need an accurate and fuller understanding of your network and the all of the network devices - wired and wireless.
The only way that I know to do that is with some sketch or diagram presenting the devices, their respective IP addresses, and to some extent the device macs. (macs may or may not be critical at first).
My suggestion is to to get all devices turned on, wait awhile so all can get connected (if they do) and then capture the Nighthawk settings as you did in your post #110.
Do not delete/redact the device IP addresses. Those IP addresses are all (or should be) in one of the private IP address ranges used by thousands of small network. Your Nighthawk router uses the commonly used default value of 192.168.1.1 as does my Linksys router. All of my devices are between 192.168.1.1 and 192.168.1.254. I use selected IP addresses for static devices and a limited range for DHCP devices. Be any given device wired or wireless.
All connected devices must be using IP addresses between 192.168.1.2 and 192.168.1.255 (subnet 255.255.255.0) 192.168.1.0 and 192.168.1.255 should not be being used (non-routable).
FYI from Lifewire:
https://www.lifewire.com/what-is-a-public-ip-address-2625974
https://www.lifewire.com/what-is-a-private-ip-address-2625970
Both links are excellent explanations and tutorials with respect to private IP addresses.
You can easily find other similar links.
PRIVACY:
What you do not want to reveal is your public IP address. Nor do you want to show the full name of any device on the network if that name could potentially reveal someone's identify., MACs are a concern for some folks but that can be mitigated by redacting the first three hexidecimal pairs of the mac address.
You can use "What is my IP" to learn your Public IP address. Generally stays the same but can change.
More homework:
https://www.howtogeek.com/764868/what-is-a-mac-address-and-how-does-it-work/
You need to ensure that on your network there are no devices using the same IP address. Most devices wanting to join the network will request a DHCP IP address from the router (and there should only be one router) and be provided a DHCP IP address from the DHCP IP address range allowed to the router.
End users can control that range of addresses plus use other IP addresses outside of that range for devices that need or require a static (does not change) IP address. Printers, NAS, scanners, Access Points, etc..
Without explicitly knowing what was done when you attempted to enable Access mode not much can be said about what happened. However it is very likely that you changed, deleted, or duplicated some IP address and the router/network got confused. When you reset everything all went back to factory defaults and there were, for example, no duplicate IP addresses and/or macs.
Factory resets are a ready way to recover a "confused" network. Trade-off being that unless you specifically went back to the router and changed the admin name and password your network may be wide open to others who know those default values and how to use them to gain network access.
Another thing: Change the DNS Server IP addreses to Google 8.8.8.8 and 8.8.4.4. There are other options but Google is commonly used. Sometimes the DNS is the ISP, sometimes the network router. Varies.
I use Google.
What also can prove helpful is to disable IPv6.
Unless there are specific and known reasons for changing MAC's leave them alone. Duplicate macs on a network cause problems.
Take some time to regroup. Read the links and use the Nighthawk's device list or even your own sketch to show your network.
For each device ensure that you know its's IP address be it a static IP address or a DHCP IP address (which can and will change with each time the device joins the network.
I have stayed out this thread mostly because this is likely something related to the application you are running and not a gernic VoIP issue. Many things that carry voice over IP do not use the standards in VoIP.Ahh, okay... just to make sure, can you tell me which of these to censor exactly on the MAC? I'm more of a visual learner.. (Which of the example 9s would be censored)
View: https://imgur.com/xSqfciA
No, it's under the same internet. Like whenever the internet went out, so would that router's connection in the garageIn agreement with @bill001g.
= = = =
This new posting:
"The router in the garage is another network and uses a different password but is still on the same ISP obviously."
Are you actually paying for two services? Or has someone attempted to connect the two networks (House and Garage) in some manner?
Not uncommon for end users to mistakely attempt to create a separate network of some sort for guests, tenants, their own dedicated gaming connection, personal business reasons, etc. and create problems.
Plus likely running afoul of their ISP End User agreements/contracts.
As for a different password: May be moot if the password is the name of a pet or some other word that can easily be figured out by those who know you. (E.g. "Strawberry" or "Cookie" may be good guesses.)
And if the router or routers have been reset then the router defaults back to the factory admin and password settings which are well-published and well known. Anyone with physical access to a router can reset the router (or perhaps modem/router). Default values for admin and password may even be printed on the router's labling.
Or worse, if indeed were changed, then taped on the device by the admin person. So if either router (make and models?) was reset and no one changed the default login values then the network is wide open.
And if the wireless security configuration is weak then people could get on to the network without much of a problem.
= = = =
lf there are indeed two separate networks then any devices in the "House" network should not appear in the "Garage" network. And vice versa. If there is network (House) and a subnet (Garage) then there should only be one router for most home network environments. And all must be properly configured.
And you certainly should look for some physical connection paths(s). People often believe that they can simply plug into some existing network and create their own network. They use network switches, coax splitters, etc. to create a physical path between the networks. Often in some roundabout manner either via physical connections and/or pretense (spoofing). Conflicts and problems result. Even network loops. [Port to port connections must be checked.]
You would do some sort of discovery to determine if any such sharing or overlaps exist. Looking for duplicate IP addresses and macs is one way of working out what devices are on any given network.
However that discovery processes is weakened if, as posted above (#117), there are legitimate mac duplications, mac and IP address spoofing, etc.. either in place or were attempted in the past.
I find macs most useful as a means to discover the manufacturer/nature of unidentified devices using the following link (there are others):
https://macvendors.com/
[Note: Does not always provide meaningful information. I know of a network with two 2.4 wireless devices that continually appear/reappear as being on the network per the router's graphical display. There is not any other supporting data that the devices are actually on the network and mac searches result in effectively being "No manufacturer". More will be done in an attempt to figure what those devices may be or some other reason for the reappearances.]
Again, I must stress the need for a full network diagram or sketch to help you understand your "House" network.
Knowing the physical connections, the wireless connections, the host names, device IP addresses (DHCP and Static) and subnet masks, and the macs are simply tools that can be used to help you underestand your network. Now that you have "networks" - "House" and "Garage". All the more problematic.
Lastly (per @bill001g) :
"I have stayed out this thread mostly because this is likely something related to the application you are running and not a gernic VoIP issue. Many things that carry voice over IP do not use the standards in VoIP."
Once you (Strawberry) understand more about your network and have a sense of all of the legitimately connected and properly configured devices of any sort it become fairly straight forward to discover the offending device by elimination or other means. Then, after that, discover the offending application being run by that device. Consider that the device owner/user may not even be aware that that application is even running....
With more information and background about the network then it becomes more likely that someone (such as @bill001g and others) will spot something. And post accordingly.
This thread is continuing to grow and very few will be willing to go back and read all of the preceding posts.
The immediate objective is to narrow this down to some simply stated problem: for example - "all works unless Device X is connected" Which is inherently a likely over-simplication in itself....