Search the Community
Showing results for tags '172.16.42.1:1471'.
Hi, I've just received the WiFi Pineapple Nano and everything seemed to work well until I had to connect to 172.16.42.1:1471 to set it up. I am using Windows 7 and my browser (Google Chrome) said that the site can't be reached and that the IP refused to connect. I did look on other forums but all I've seen was uncheck your internet sharing (was already done) and to reset it which didn't change anything. So I would really like some help to get this set up and finally upgrade my pentesting arsenal, thanks.
I received my new Pineapple last week and have not been able to connect to the server. I have done a factory reset (twice), put in a new SD card and followed numerous connection guides on this site and others. The Pineapple is working - green light with flickering orange, blue, red. I am out of ideas - any suggestions please?
I attempted a first boot setup today with no luck. When I try to connect 172.16.42.1:1471 through Firefox, I receive the message "Unable to Connect: Firefox can't establish a connection to the server at 172.16.42.1:1471." I cannot access the pineapple's user interface. Edit: I am attempting to connect to the pineapple solely through an ethernet connection. I am using a Macbook Pro Retina, OS 10.8.5 I insterted the MicroSD card supplied, powered on the pineapple (power cord), waited 6 minutes, and attempted to browse to http://172.16.42.1:1471. No luck. My Macbook ethernet settings: Config
I have just gone through the setup for a new Pineapple, the flash went smoothly and I'm able to ping it, but it is unable to connect to the 172.16.42.1:1471 server. I've tried configuring everything manually as outlined in the manual as well as trying to set it to automatic ip designation. I have tried it on two machines running windows 7 and 8. A few sites that check if webpage are up say that the page is down. Firefox says: The connection has timed out The server at 172.16.42.1 is taking too long to respond" or "Unable to connect Firefox can't establish a connection to the server at 172.16.