Windows direct connection losing Internet connection

Hello folks, as a newbie I'm getting oriented. Today I received my Udoo Neo Full board.

1. I had used Win32 Disk Imager to burn UdooBuntu 2.1.2 to a new microSD card. I'm using the Win7 machine to try things out.
   
2. I followed the quickstart document, after I had the RNDIS driver I noticed that a new network was created (Network3) and that the Win7 machine appears to not be connected to the Internet. I also noticed that the CDC serial driver is not installed.
3. The next time I booted Win7 I first confirmed the Internet connection, then plugged the Neo in and again, I see the CDC serial driver is not installed, there is a second network and the machine does not appear to be connected to the local network

Any pointers, however obvious, will be appreciated.

 

Just tried again and the above repeated. But this time I opened to the device manager and disabled the RNDIS driver, and presto, the machine appears connected to the Internet again... Maybe that's a clue...

 

Hi folks, I tried a few things and got myself into and then out from some trouble. Then I tried one more time, and voila, I can ping the Neo board and also post to forums... I'm not sure what happened, but I guess that's one step forward.

 

I guess the same cause as https://www.udoo.org/forum/threads/neo-usb-connection-to-pc-interrupts-its-connection-to-wifi.6845/

 

After my recent trevails, I noticed that the Win7 machine appeared to have both the ethernet and USB-RNDIS connections active, but the Neo had no connection to the Internet.

So now I'm reading details such as network management and network bridging. My suspicion is that with two network adapters there are a number useful possibilities other than what the OS guesses for us.

 

After rebooting the Win7 machine, I'm back where I started. That is, with the RNDIS network enabled I lose ethernet and I can ping and ssh to the Neo.

Funny thing, now I cannot login using TightVNC. I see a graphical login window and when I enter the usual password, the connection "gracefully exits." I haven't figured out how to forward X-windows through ssh yet.

Next, I tried to bridge the networks and didn't notice any change in behavior, but if I disable the RNDIS, I get ethernet back.

I see in another note that someone is looking into IP tables, so I'll do some more reading.

 

Hi Krista,
Usually you have to do "ssh -X user@ip" in order to use your X with ssh

 

I remember that I set the color depth of the connection. It seems that I had to set it explicitly to true color.

 

Hi Gorgo, I did have some success. For the record I have Cygwin installed, I'm using Cygwin-X along with that terminal. First I checked to make sure the DISPLAY environment variable is set to :0.0

In logging in, using ssh with the -X switch, I didn't have any luck, so I tried the even more powerful ssh -Y switch, and immediately after login:

/usr/bin/xauth: timeout in locking authority file /home/udooer/.Xauthority

Huhh, so I used ls -al to look about and found that .Xauthority was owned by root and its mod date was Dec. 31, 1969. There was also an .Xauthority-c and an .Xauthority-l file owned by udooer. So I moved all the .Xauthority files to a temporary sub-folder.

After logging out and back in using the ssh -Y switch I found:
Last login: Wed Dec 31 19:04:05 1969 from 192.168.7.1
/usr/bin/xauth: file /home/udooer/.Xauthority does not exist

I expected that. Next, geany did start, which is good and there is a new .Xauthority file owned by udooer. BTW, I went back and tried ssh -X without any luck, but using ssh -Y does work.

BTW, the .dbus and .gvfs files are also owned by root, don't know what that's about.

 

Hi Maurice, in getting X to work, I can again use VNC to access the Neo.

 

To install the CDC-Serial driver, follow pretty much the same routine as that for RNDIS. After the "Browse my computer for driver software step," click "Let me pick from a list of device drivers on my computer". The class is Ports (COM &LPT), the manufacturer is Freescale, the Model is OpenSDA - CDC Serial Port. If you don't already have P&E drivers installed, you can get them from the following URL.

http://www.pemicro/opensda

 

Hi folks, took a short break. To summarize things so far, on the upside it's nice to have the CDC-serial driver in place, so that works regardless of the network state.

For a short while when I connected the Neo to my Win7 machine sometimes the Win7 machine would remain connected to the network, but more lately the Win7 machine loses its connection to the larger world. In both cases an isolated secondary RNDIS network is created that I can use to connect directly to the Neo but the Neo is not able to communicate with anything in the Internet. I tried bridging and sharing Win7 network adapters, no luck.

So for now, I can use USB along with another means of communication, either wifi or the ethernet cable. Or I can use the video, mouse, and keyboard. Not so bad for now...