This question was originally titled "How to gather information about suspicious wireless access point?" but then this topic has been moved to another question, leaving here discussion of connection problem.

I cannot connect via my network socket - DHCP gives me wrong settings. My guess is that someone in the LAN took my IP address. This is exactly what happened about half-year ago. ISP told that it was their problem, but it took about a week for them to come and fix it. The situation is pretty the same - my socket is not working, but ohter guys seem to be fine. Let me explain the setup and the symptoms:

  1. Our ISP is the main provider in the area where we live. They installed hardware in the buildings and other providers will use it if we want to switch to them. Moreover, by contract with the landlord we have pay to both the main ISP, and to whatever ISP we want to switch to.

  2. Everyone has one socket per apartment and one IP address provided via DHCP. I have lived in several apartments in the area, and there is always an issue with assigning IP - it takes several days before a new device is given the correct settings via DHCP. Everyone experiences this and I have tried to tell this to ISP - no reaction.

  3. Since we have more than one device to connect to internet, I had to buy a wireless AP and I have chosen a cheep DWL-G700AP of not very high quality as you can see from this wizard emulator. It is not a router, so it assigns an IP in the LAN using ISP's DHCP.

  4. I live in a student area and I believe quite many guys use such cheep AP w/o routing. Since the ISP's settings are quite old, I suspect that the mask of doesn't correspond to the reality when almost every household has about 5 devices requiring own IP address.

  5. Sometimes I loose internet connection via my AP. It can be several times per day, or once per week. The solution I came up to is to turn off/on my D-Link.

  6. This suspicious AP, which I am using now instead of my AP, has also 54Mbps but it works few times faster. I am impressed.

  7. And yes, no surprise, that we loose the connection right when we need it so mad - just before course examinations or project deadlines.

  • 6
    Rather than using a suspicious WiFi AP which isn't yours, why not try to troubleshoot why it is your network jack isn't working? What is your network environment - is this a corporate office, a home network, or what? Who manages the DHCP server? Have you tried contacting them? – nhinkle Sep 3 '10 at 22:16
  • +1 @nhinkle - we can help with the lan issue perhaps. – JNK Sep 4 '10 at 0:10
  • 1
    Given how this evolved: what about renaming this question to "How to troubleshoot DHCP problems?", and create a new question for "How to gather information about suspicious wireless access point?" with something like There is a number of wireless access points in my building, and one of them is connectable with no password and encryption, called "default". This looks very suspicious too me, so I would like to know as much as I can about this AP. Like: 1. How can I find out the IP address of the wireless AP I am connected to? 2. Is there a way to see who else is connected to the same AP? – Arjan Sep 4 '10 at 12:34
  • @Arjan, good point! I will try to do this, but I have a screaming baby in my hands so it goes slow :) – Jack Sep 4 '10 at 13:53

As for the IP address: things like whatismyip.com might help.

You're using the ISP's DHCP, so you're getting multiple addresses from the ISP, which I doubt will be fixed then. Hence, what if your computer or AP is actually dropping the connection, or trying to use it after the "lease" has expired? Then "your" IP address can indeed be handed to someone else, and if the number of available addresses is limited then there's nothing new to connect to. So, do you still get a new IP address when this happens? Are you sure you did not manually set IP addresses somewhere?

And what if you plugin one device into the LAN socket -- does the connection still drop if you wait a long time?

You're saying:

It is not a router, so it assigns an IP in the LAN using ISP's DHCP.

Those are two different things. I doubt it's not a router. And page 15 of the AP's manual shows it can surely act as a DHCP server as well, hence creating your own private network which is surely to be preferred anyhow. What if you try that? (Be sure to set LAN to dynamic, to make your IP get one IP address from the provider.)

Finally: anything interesting in the AP's log?

| improve this answer | |
  • Yes, my IP (.70) is static. But I am curious about IP of the AP ("default"), which I still don't know. Yes, I use automatic IP from DHCP, not manual. Even if I connect by cable (i.e. directly w/o AP) to my socket, then DHCP fails, and OSX sets completely different settings. I have failed to make a private network with the D-Link AP, so I was using ISP's DHCP and yes, it was dynamic. And BTW, I cannot see the log, because since a while ago I cannot connect to the AP even by cable - something went very wrong and I cannot reset it anymore. I guess I need a new AP, huh? :) – Jack Sep 4 '10 at 9:18
  • 2
    I think your IP should not be static: you yourself have connected multiple devices, hence are using multiple IP addresses. Does your ISP reserve static IP addresses for all devices folks ever plugin? But even if it is static, then the DHCP will take care of that. Hence, again, are you sure you did not manually set IP addresses somewhere? Maybe even within your AP, but if the AP cannot even be put back to the factory settings using that reset switch, then it's probably time for a new one indeed. Can you ping "your" IP address from another computer when your Mac is switched off? – Arjan Sep 4 '10 at 9:27
  • 1
    @Jack, so both computers fail simultaneously? If not, then it might be interesting to see if you can somehow "ping" your IP address using your wife's computer after your Mac has been kicked of the network. I know you already tried a normal "ping" without success, so maybe we can prepare for the next failure by figuring out why. Or a way to get the MAC address given an IP address, and see if that changes. – Arjan Sep 4 '10 at 12:05
  • 2
    And as for DHCP failing: I know of ISPs who only allow one device, hence require earlier DHCP leases to expire before another device can get a new lease. (In such cases, using ones own DHCP server prevents a lot of issues.) This is clearly not the case with your ISP, but I could imagine that something gets messed up when connecting some device through some ethernet socket (through the "default" AP), and then suddenly using the same device on some other socket (in your own house, with or without your own AP). But: just guessing, really. – Arjan Sep 4 '10 at 12:09
  • 1
    @Jack, if the AP is not running as a DHCP server itself, then it might not need any IP address itself either. So, it should operate even without any ISP, right? And to wirelessly find it, it shouldn't even be required to connect its ethernet cable into the socket, right? So, to summarize, maybe: 1) your AP is faulty, and 2) your ISP's router/DHCP does not like you connecting some device to different sockets in a short period of time (and hence all testing is very difficult and giving us false clues)? (Again: just guessing!) – Arjan Sep 4 '10 at 12:24

Never ever ever ever ever use a wireless AP you don't know and/or explicitly trust. There are indeed some that are set up to lure unsuspecting people to join the network.

Personally I think there is no way to trust it, no matter what utilities you use. There is no program that will tell you the intent of other users on the network.

You are better off focusing your energy on the LAN issue and getting that resolved.

| improve this answer | |

I'd recommend Wireshark if you have the time to learn. Else, you can shell out about $50 and get some VPN access so you don't have to worry at all about tampering and sniffing.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.