192.168.7.2 connection timeout error and disappearance of E drive within a few minutes

GoogleGroups
1

Hi, I got BeagleBone Black Wireless. I connected it to my PC running
Windows 10 64-bit. After spending lots of time to find that I needed to
disable Driver Signature Verification, I installed the drivers successfully
from the E drive by running BONE_D64. After installation, I typed
192.168.7.2 under Firefox and got the connection timeout error. Could you
please let me what to do to resolve this issue?

Also, after I pressed the reset button, the 4 LEDs near the microusb
connector blinked. Then, E drive showed up on the screen. However, after a
minute or so, the E drive disappeared from Windows and all those four LEDs
were turned off. Is this normal? Why the E drive disappeared from Windows.
Could it be that the usb cable does not supply enough power to the board?
Should I use a 5VDC 2A to supply power source?

2

Hi User PC,

You did not need to install any drivers that require disabling driver signature verification. As a matter of fact you do not need to install any drivers on Windows 10. The instructions that you probably followed are not 100% correct. I know this because I ran into the same confusion when I first got my BBB a few months ago.

Basically, all you need to do is set your static IP address to 192.168.7.1. The beaglebone black has it’s subnet set up so that the IP address range is 192.168.7.1 through 192.168.7.2. Obviously, with the BBB being “.2”, your PC must be on “.1” Once you to this, try to connect again using firefox, it will go right through. Note that if you are using MAC or LINUX, your static IP should be 192.168.6.1, with the subnet mask on the BBB only allowing IP address ranges of 192.168.6.1 through 192.168.6.2.

When you set up the static IP, make sure you do it for the beaglebone network card that shows up, not your PC’s physical network card. If you installed any drivers, I would remove them. The new BBB boards do not require drivers.

3

On Mon, 19 Aug 2019 15:34:42 -0700 (PDT), user pc
<petercohen8877@gmail.com> declaimed the
following:

from the E drive by running BONE_D64. After installation, I typed
192.168.7.2 under Firefox and got the connection timeout error. Could you
please let me what to do to resolve this issue?

  Don't use Firefox?

  To expand... If you are trying to get to the Cloud9 IDE, you need to
use
    http://192.168.7.2:3000/
Note the :3000 specifying the target PORT. If you leave that off you are
trying to get to the normal HTTP port 80 -- there is NO SERVER LISTENING to
port 80 (I don't get "timeout" I get "Unable to connect" for a BBB)

  Open a command line (on Win10) and enter "ssh debian@192.168.7.2"

"""
C:\Users\Wulfraed>ssh debian@192.168.7.2
debian@192.168.7.2's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Aug 27 12:48:16 2019 from fe80::c932:bd85:577:9922%eth0
debian@beaglebone:~$
"""

Win10 now includes an SSH client (and SFTP, same connection form, just
change ssh to sftp). This can save one from having to first download PuTTY
and installing it, although PuTTY has more features (save connection
information, capture logs, etc.)

  NOTE: unless you have Internet Connection Sharing enabled on the Win10
box, the Beagle will have not internet connection until you set up WiFi to
a router... And once you have that working, you don't need 192.168.7.2 --
you can connect through the router assigned IP number (or, more likely for
Win10, just use the host name "ssh debian@beaglebone" [verify with router
that the hostname is correct]).
  

Also, after I pressed the reset button, the 4 LEDs near the microusb
connector blinked. Then, E drive showed up on the screen. However, after a
minute or so, the E drive disappeared from Windows and all those four LEDs
were turned off. Is this normal? Why the E drive disappeared from Windows.
Could it be that the usb cable does not supply enough power to the board?
Should I use a 5VDC 2A to supply power source?

  Are you sure that wasn't the power(off) button?

4

On Fri, 30 Aug 2019 11:56:17 -0400, Dennis Lee Bieber
<wlfraed@ix.netcom.com> declaimed the following:

Open a command line (on Win10) and enter "ssh debian@192.168.7.2"

  Apologies for how gmane attempt to hide what looks like email addresses
to it...

    ssh debian(at-sign)IP-address

but let...

Win10, just use the host name "ssh debian@beaglebone" [verify with router

through -- the lack of a dotted identifier after the @ probably was taken
to be invalid for a domain.