[Cannot get the Pineapple to Setup]

I can't connect or set up my new Wi-Fi Pineapple. I followed the steps in the guide and online exactly to the best of my knowledge. I don't see why this isn't working. It should be pretty simple, but for whatever reason, it just doesn't want to work. I can provide more details if needed. Please help, thanks!

• Pineapple Hardware Version (ex: Mark III, Mark IV, etc.): Mark IV
  
• Pineapple Software Version (ex: 2.5.0, 2.6.4): Whatever the default firmware it shipped with is (I didn't change it as I can't do anything)
  
• OS used to connect to the pineapple: Windows 7
  
• Network layout of how your setup is connected (including IP information): I connect to the internet with a Wi-Fi connection (Wireless Network Connection). I connected the pineapple to my Ethernet port on my laptop to the pineapple's WAN/LAN port (Local Area Connection). Here is the result from ipconfig: Wireless LAN adapter Wireless Network Connection:
  Connection-specific DNS Suffix . : gateway.pace.com
  Link-local IPv6 Address . . . . . : fe80::e1e5:c468:b293:8a1a%15
  IPv4 Address. . . . . . . . . . . : 192.168.1.67
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.254
  Ethernet adapter Local Area Connection:
  Connection-specific DNS Suffix . :
  Link-local IPv6 Address . . . . . : fe80::9de3:238d:91f7:1c1c%13
  IPv4 Address. . . . . . . . . . . : 172.16.42.42
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . :
  
• All the tools/options that are running on the pineapple when the issue happened: Default
  
• Ping results from computer to pineapple: C:\Users\Dr Dinosaur>ping 172.16.42.42
  Pinging 172.16.42.42 with 32 bytes of data:
  Reply from 172.16.42.42: bytes=32 time<1ms TTL=128
  Reply from 172.16.42.42: bytes=32 time<1ms TTL=128
  Reply from 172.16.42.42: bytes=32 time<1ms TTL=128
  Reply from 172.16.42.42: bytes=32 time<1ms TTL=128
  Ping statistics for 172.16.42.42:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
  Minimum = 0ms, Maximum = 0ms, Average = 0ms
  C:\Users\Dr Dinosaur>ping 172.16.42.1
  Pinging 172.16.42.1 with 32 bytes of data:
  Reply from 172.16.42.42: Destination host unreachable.
  Request timed out.
  Request timed out.
  Request timed out.
  Ping statistics for 172.16.42.1:
  Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
  
• Is the problem repeatable (Yes/No): Yes
  
• Steps taken which created the problem: The initial set up for Windows (on the included book and from http://cloud.wifipin...guidequickstart)
  
• Error Messages: Google Chrome could not connect to ...
  
• Log file information: Not sure where to get this from (if possible with no valid connection).
  
• Anything else that was attempted to 'fix' the problem: Re-tried setup. I also tried to connect to my BT5RC3 VM with no luck.
  

[[Payload] Android Brute Force 4-digit pin]

Will it continue to go deep into the brute forcing even with a different pin lock screen? For example the Galaxy S3 might have a different login screen for PINs than the Nexus because of touchwiz. Does that affect the payload at all? Would it press the wrong numbers or keys because of a different key layout?