Mini PC & Travel Router w/out internet (LAN connection only) random disconnects

[AstroAndy]

Hello folks

While I would describe myself as a mid-level nerd, there is something that has me foxed.

I have an older Win 10 Pro Lenovo Thinkpad (client, control computer ), which I've networked to a Mele Quieter NUC (Server, Win 11Pro, v 21H2).

No problems with the internet, stable connection.

 

In the field, there won't be internet.

 

Now, testing it without the internet, I get more or less frequent random disconnects.

The NUC is connected with an Ethernet cable to the mini router (GL iNet AR300M). The Laptop is wireless, within the correct distance.

Here are the things I have tried (the last one has netted me an acceptable, but not fully fixed solution with very few drops, and quick reconnects)

 

I will not cover the basics, such as router setup, etc, this is all good.

 

On the server side (NUC)

1) In device manager, all the power options for Network adapters as well as universal serial bus controllers have been changed.

2) In the Group policy settings RDP), all the timeouts have been reset to never (including idle and active)

3) In command prompt (admin. mode), pinged the relevant IP

4) In command prompt (admin. mode), checked IP configuration and flushed the DNS cache

5) In the RDP menu, smart cards etc. disabled

7) Similar things on the client side (Lenovo Thinkpad)T440, Win 10

 

And probably some other things supposed to cure that problem I read online

 

What I don't want to do just yet:

Mess around with registry keys and DWORDS (unless I absolutely have to)

Give up looking for a permanent solution

 

The only thing I've had success with is actually supressing (disabling) the Wifi network adapter (on the NUC side).

It's not a big thing, since I can re-enable it back at home / and /or get internet anyway with it being disabled, as the Ethernet adapter connects it to my control pc (T440 Win. 10).

 

I don't have an option to use internet for astrophotography in my home environment, nor the wish (and possibly monetary bandwith to work with a hotspot)

The only desired solution is a Windows Remote Desktop connection that will not fail for 8 hours.

Any ideas what could be the problem and the solution?

That would be awesomely kewl.

-  Andy -

 

PS: As I sit here, my RDP connection with the WIFI adapter disabled, has been working well for about 1 hour now, but there are still random dropouts, which I want to get rid of.

Edited July 25, 2023 by AstroAndy

[ONIKKINEN]

Is the dropout between the client and the server, or does the mini-PC actually stop broadcasting its hotspot through the mini-router causing a dropout?

My mini-router (same as yours, i think) has terrible range and will drop or freeze the connection occasionally but will reconnect back. Simply having the scope between my tablet and the minirouter can cause a freeze. Or a closed car door, or more than 5m with perfect line of sight. These are non issues for me since the mini-pc will keep capturing regardless of connection so have not looked for a solution.

* Just thought of something else, when you are testing this you do have your home wifi turned completely off? Your mini-pc may be trying to connect to your home wifi because the minirouter connection has no internet connection and so windows in its infinite wisdom will keep looking for a better connection.

Edited July 25, 2023 by ONIKKINEN

[StevieDvd]

Could the problem be with the GL iNet AR300M router, rather than the NUC?

I googled for GL iNet AR300M issues and found a few sites mentioning disconnects such as this one

 

[AstroAndy]

@Onikkienen

I tend to think it's with the router. I've tested it with the internet completely off, internet on, at a distance of 6 feet, with different ethernet cables and computers, with the scope always in the same position.

Obviously, with the internet on, one has to be on the same network for the computers to "see" each other, so no problem there. In the field (no internet), the control computer and mini pc automatically go to the minirouter network.

With the internet, it's completely stable, without, I have now gotten to the point where it is satisfactory. I'm ok with it dropping out infrequently, but of course would like to have it to a 100%.

@StevieDvd possibly, I have to check further into that

 

Thanks for your input, guys.

[AstroAndy]

Hi all

Thanks for all your input.

It seems that the things I first did all helped.

Other things I have done is update router firmware (didn't help) check power, cables etc. (the basics).

I've trolled thru a lot of event viewer logs. and these are the things I've been experiencing:

 

RDP ClientActiveX has been disconnected (Reason= 2308)

RDP ClientActiveX has been disconnected (Reason= 263)  0x80004005

RDP ClientActiveX has been disconnected (Reason= 516) 0x80004004

RDP ClientActiveX has been disconnected (Reason= 3) 0x8000ffff
RDP ClientActiveX has been disconnected (Reason= 260) 0x8000ffff

 

From what I understand, reason 263 pertains to the NLA, which can be reset any number of ways (I went with a Group policy edit, NB, one may have to try more and do a RESTART, not a SHUTDOWN and TURN ON of BOTH the machines, server and client).

Basically, you have to make sure that the client computer (ie. the control one), either has suport for NLA, or have NLA disabled on the server (NUC)

While it is workable to go without NLA, I'd rather not.

Reason 516 has to do, as I understand it with the transport protocol (ie. TCP, and more importantly, UDP).

I got around that by forcing a connecting to one ethernet card (on the NUC) only. Works like a charm now.

Haven't  figured out reason 260 yet, but it may be tied in to the others, having solved the other issues, this one doesn't show up anymore, which is good enough for me.

I've tested it on more devices, and loaded up a shedload of programs (apps.), which I normally wouldn't use during an imaging session, as a sort of stress  test. Strangely enough, only Stellarium gets thrown out after a while, so I've checked the Windows Defender Firewall.

 

I can live with how it performs now ( a lot better than before), just some latency, which is to be expected.

 

- Andy -