- Sep 16, 2015
- 3
- 0
- 4,510
This is a problem I've been trying to fix for the past 3-4 hours straight, I'm no expert, but I am most definitely not incompetent with tech related issues. Regardless, this one has stumped me. If you have any questions about any of my hardware or my current settings within my network, ask away and I'll try to answer them as fast as I can.
I am now at the point where I have tried a little bit of everything from various websites answer others questions that aren't exactly in the same situation. (Yes, the problem gets worse and more complicated as this article goes on.)
I have an Arris TG862 router as my primary wifi source, and the access point router (AP) is an EnGenius EAP 350. This has always and is still being tinkered with on a Windows 8 PC.
The problem I'm having is that the I can no longer access the AP router's settings. For example: if I typed in the default ip address into the HTML bar and hit enter, it would eventually say that it can't connect due to taking too long to connect.
When I first decided to alter this AP's settings, I simply gave it a password, so that no one nearby could leach the internet off of it. After that I gave it and my computer that I was editing everything on a static IP address, for some reason or another. It's been awhile since then though, I'm not entirely sure if I gave the AP a static IP or not, but I've come to the assumption that I have from using nmap to ping connected networks, and from using the arp -a command.
At my first few attempts simply trying to connect to the AP router, I was fairly certain that I had set a static IP address for the it, and so I tried connecting to the settings of the AP using many differnet IP addresses that I thought may have been the correct IP. Eventually after getting to one of the many fixes that I attempted, I found 2 distinct IP addresses that "rejected" my search query. One of these IP addresses was my IPv4's "preferred" address when I was connected to the AP. This made me assume that the address was the static IP I had once set on the AP router, but as mentioned earlier, it was "rejected".
Another thing to note is that one of the fixes that came across my head was to restore the AP to factory settings, and I eventually tried doing this by holding down the reset button on the AP itself for 10 seconds like it says in the manual. This seems to have successfully reset the router to factory settings, because it no longer has a password that is required to access it. Bad news for me is that it still won't connect to any of the IP addresses that I tried entering into the HTML bar. Now I have an access point with no password protection and an huge wifi range. This is a problem. (No kidding) I have unplugged the ethernet cable that attached it to the main router's ethernet port so it no longer is giving the neighborhood internet.
For now I must patiently await a response from someone unfortunate enough to want to help with this big of a problem. Although I may have been over thinking many simple things that could easily fix this, I have spent enough time toying around with it to understand that I'm not quite savvy enough regarding networking to fix this myself, or even with the help of other people answering even more other people on the internet.
As mentioned at the beginning, if you have any questions about my network settings, or hardware, etc. ask away and I'll do my best to answer them with as much detail as you need.
I am now at the point where I have tried a little bit of everything from various websites answer others questions that aren't exactly in the same situation. (Yes, the problem gets worse and more complicated as this article goes on.)
I have an Arris TG862 router as my primary wifi source, and the access point router (AP) is an EnGenius EAP 350. This has always and is still being tinkered with on a Windows 8 PC.
The problem I'm having is that the I can no longer access the AP router's settings. For example: if I typed in the default ip address into the HTML bar and hit enter, it would eventually say that it can't connect due to taking too long to connect.
When I first decided to alter this AP's settings, I simply gave it a password, so that no one nearby could leach the internet off of it. After that I gave it and my computer that I was editing everything on a static IP address, for some reason or another. It's been awhile since then though, I'm not entirely sure if I gave the AP a static IP or not, but I've come to the assumption that I have from using nmap to ping connected networks, and from using the arp -a command.
At my first few attempts simply trying to connect to the AP router, I was fairly certain that I had set a static IP address for the it, and so I tried connecting to the settings of the AP using many differnet IP addresses that I thought may have been the correct IP. Eventually after getting to one of the many fixes that I attempted, I found 2 distinct IP addresses that "rejected" my search query. One of these IP addresses was my IPv4's "preferred" address when I was connected to the AP. This made me assume that the address was the static IP I had once set on the AP router, but as mentioned earlier, it was "rejected".
Another thing to note is that one of the fixes that came across my head was to restore the AP to factory settings, and I eventually tried doing this by holding down the reset button on the AP itself for 10 seconds like it says in the manual. This seems to have successfully reset the router to factory settings, because it no longer has a password that is required to access it. Bad news for me is that it still won't connect to any of the IP addresses that I tried entering into the HTML bar. Now I have an access point with no password protection and an huge wifi range. This is a problem. (No kidding) I have unplugged the ethernet cable that attached it to the main router's ethernet port so it no longer is giving the neighborhood internet.
For now I must patiently await a response from someone unfortunate enough to want to help with this big of a problem. Although I may have been over thinking many simple things that could easily fix this, I have spent enough time toying around with it to understand that I'm not quite savvy enough regarding networking to fix this myself, or even with the help of other people answering even more other people on the internet.
As mentioned at the beginning, if you have any questions about my network settings, or hardware, etc. ask away and I'll do my best to answer them with as much detail as you need.
Facebook
Twitter
Instagram