Solved 192.168.1.1 problem configuring engenius 5611n Access Point

December 16, 2011 at 06:34:10
Specs: Windows 7
I try to configure to Engenius 5611p´s, one as Access Point, the other as Client Bridge. In order to do so one has to connect the 5611p to the Ethernet connection of the PC, assign a static ip address for it (192.168.1.1)(submask 255.255.255.0) and then log in through the webbrowser typing 192.168.1.1

This all worked fine when I started but later it appeared that some settings should be changed in the Access Point. The problem I have is that I cannot possible reach either of the 5611p's anymore. When I give 192.168.1.1 in the browser I am getting a request for a user name and password, I guess from my router. Engenius technical support are friendly but say they cannot help me if they can't reach the 5611p through the internet.

I have tried to identify the problems through ipconfig/all; through sending a ping, by restoring my PC to an earlier condition and by attempting to reset the setting to a DCHP modus. All to no avail.

Once I plug the ethernetwire going to the Engenius in the PC I get the message: Unidentified network; no internet access (I am on W7).

Would be grateful for any hints, spent some 2 full days sofar.

Henk


See More: 192.168.1.1 problem configuring engenius 5611n Access Point

Report •

#1
December 16, 2011 at 07:23:33
✔ Best Answer
First I need some info. On the computer you're attempting to connect to the EnGenius equipment from do the following:

Open a command prompt window (ie: Start >> Run >> type cmd and hit Enter) and perform the following command:

ipconfig /all

Once you've finished, copy/paste the output into a response on here so we can have a look.

For info on how to copy/paste from a command prompt window click on my name above and read my "how-to" guide titled, "Post the output of ipconfig (version 2)"

I suspect there's an IP addressing issue and the above info will help me ascertain if that's the case.

It's worth noting, good documentation can be helpful. I have a document that details the important info on all AP's in my environment. That includes, IP Address, MAC Address, and Channel the unit is operating on. You might want to make one of these up.

All my AP's also require authentication to connect to the management interface. I use the same username and password on all of them. You might want to consider doing that too.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
December 16, 2011 at 10:46:16
Dear Curt,

Here the readings from the ipconfig/all prompt (this time from an XP computer, I have stored the W7 Laptop).

C:\>ipconfig/all

Windows-IP-Konfiguration

Hostname. . . . . . . . . . . . . : thuis
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein

Ethernetadapter LAN-Verbindung:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Realtek RTL8139-Familie-PCI-Fast Eth
ernet-NIC
Physikalische Adresse . . . . . . : 00-13-D3-B9-F2-85
DHCP aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.1.21
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :

Ethernetadapter Drahtlose Netzwerkverbindung 3:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Linksys Wireless-G PCI Adapter
Physikalische Adresse . . . . . . : 00-1C-10-6E-C7-30
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 192.168.200.102
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.200.1
DHCP-Server . . . . . . . . . . . : 192.168.200.1
DNS-Server. . . . . . . . . . . . : 192.168.200.1
Lease erhalten. . . . . . . . . . : Friday, December 16, 2011 12:04:13 P
M
Lease läuft ab. . . . . . . . . . : Friday, December 23, 2011 12:04:13 P
M


As for your remarks on usernames and passwords: I too try to standardize these. However, from time to time one of my sons feels that his problem is of such extreme urgency that he may bypass my request ONLY to work on his own PC.

If you need any other info please inform me, it is a privilege that you are willing to spend time on a problem of mine, a complete stranger.

Best regards, Henk


Report •

#3
December 16, 2011 at 12:55:54
In your initial post you mention connecting to the management interface of the AP using the following IP address: 192.168.1.1

The output of your ipconfig /all commad shows the following IP address: 192.168.200.1 as your default gateway IP address.

The default gateway IP should be the LAN IP of your router. All other devices connected to that router should have IP's in the 192.168.200.0/24 range in order to communicate properly with the rest of the devices on the network.

You don't mention if you changed the AP's IP address to one in your subnet. If you didn't, that's definitely going to be a problem since they won't be able to communicate with anything else....or anything else with them.

If you did change the IP of the AP's to something in your subnet (ie: 192.168.200.0/24) then you'll have to enter that IP address in the web browser of your computer in order to connect to the AP's management interface.

If you didn't give them an IP then you're going to have to reconfigure them. I'd recommend you start by first connecting to your router and verifying your DHCP scope as you'll want to use IP's that are not in the DHCP Scope. A typical default DHCP scope on a SOHO Router is usually .100 t0 .199 In the case of your subnet it would look as follows:

192.168.200.100 to 192.168.200.199

Once you know your scope, pick two IP's to use to statically assign to your AP's. In keeping with your subnet and the above example scope I would use the following:
AP1 = 192.168.200.21
AP2 = 192.168.200.22

Then, connect directly to your AP's (one at a time) and if necessary, reset them to the factory defaults and reconfigure the TCP/IP settings to reflect the correct IP (192.168.200.21 or .22) and the correct subnet mask (255.255.255.0) and default gateway (192.168.200.1)

Once they are correctly configured you can then plug them in to the network and they should work.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
December 17, 2011 at 14:31:29
Dear Curt,

Thank you for your reply, I first made today a map of all IP addresses etc. of the apparatus in our house. However, the basic problem proved to be completely different. My youngest son deleted all coockies in my PC and then it appeared that the window asking me for a password and username did not crop up anymore. Then the remaining problems were quickly resolved. I hope that I describe it correctly.

Thank you very much for your help, I will remember you whenever I will check my new file with IP addresses etc.

Best regards, Henk


Report •

Ask Question