LAN issues with Q5 pro

[jeps]

[Phil181]

I would recommend allocating the Q5 Pro a fixed IP address in your network.

This was always a complaint for years with the WD TV's and was easily fixed for most users. 
Windows networking always works more reliably with fixed IP's allocated for peripherals like printers, media players, NAS, Seagate Centrals, AVR, TV etc.

[jeps]

Okay, should have mentioned that the box already had/has fixed IP address.

Strange that Kodi and the box have different IP's, is that a problem?

Really hope someone can come up with some leads.

[jeps]

For some strange reason the SMB protocol stops working but NFS still works.

I have Hanewin installed and my previous mediaplayer used NFS without problems.
My Q% is able to connect to my NAS but not my Windows server.

Can anybody provide settings for Hanewin that will work with Q5 pro?

[jeps]

I'll answer my own thread once again 

I have tried changing patch cable, no luck
I have tried a different port on the switch, no luck
I have tried a different switch, no luck.
I have tried a fixed IP-address, no luck

On the WiFi connection everything works according to specs'.
But WiFi and 4K movies is a bad combination.

So it looks like a RMA to me.
Does anybody have a link to information on how you make a RMA?

[futeko.com]

It sounds like a problem with your network setup. Exactly what is difficult to diagnose remotely but it seems something (your NAS would be prime suspect) is blocking Q5 Pro access to SMB after a set amount of time. Is there nothing in your NAS setup relating to this? It might be a security feature.

Kodi and the Q5 Pro will report different IP addresses, this is normal.

It's unlikely that LAN disconnecting after a certain period is a hardware problem. Especially when this is not the experience of other Q5/Q10 Pro users.

RMA / warranty info is linked to in the footer of our site/forum. http://www.futeko.com/navpage/questions-warranty.php

[jeps]

What I have done is replacing my Mede8ter mediaplayer with my Q5 Pro.
Same User account on both server and NAS, same patch cable, same port on switch etc.
It  has worked for 3-4 years with my Mede8ter without any issues.

The mediaplayer connects to my Windows server and my NAS.
When the disconnection occurs both Kodi and the player it self is unable to browse/contact any PC on my LAN.
(Including the NAS and my server)

The disconnection is sometimes only short (2-10 seconds) sometimes much longer (I give up waiting).
This can happen during playback or in idle.

How you come to your diagnose eludes me.
I would say (with out having opened the casing) it sounds like bad soldering on the board.

[futeko.com]

It just doesn't sound like a hardware problem, especially since you say you're still able to browse the internet. That implies that the LAN port is OK.

But, as you say, it's very difficult to diagnose remotely.

You are welcome to return and we'll have a look at it.

[jeps]

The WiFi connection has now been up and running for more than 24 hours straight.
That is more that the summarized uptime of the wired connection.

The connections use the same account on both my NAS and my Windows server.
So to me it is clear that something is wrong with the wired connection in my Q5 Pro.

I will find the best period for the repair. 4 weeks or more without the player is serious business.

[daredevil]

What I have done is replacing my Mede8ter mediaplayer with my Q5 Pro.
Same User account on both server and NAS, same patch cable, same port on switch etc.
It  has worked for 3-4 years with my Mede8ter without any issues.

The mediaplayer connects to my Windows server and my NAS.
When the disconnection occurs both Kodi and the player it self is unable to browse/contact any PC on my LAN.
(Including the NAS and my server)

The disconnection is sometimes only short (2-10 seconds) sometimes much longer (I give up waiting).
This can happen during playback or in idle.

How you come to your diagnose eludes me.
I would say (with out having opened the casing) it sounds like bad soldering on the board.

I too come across the same problem nowadays. The lan does not sometimes recognise the windows or nas servers. May be after several reboot it make find one time. With my Mede8er 600X3D in line, i have no problem for the past 3 to 4 years and even in the loop now.
Please some one can suggest any remedy.

[Nice Monkey]

Android boxes in general don't like wired and wireless to be active concurrently. Just as a remark.

[jeps]

I too come across the same problem nowadays. The lan does not sometimes recognise the windows or nas servers. May be after several reboot it make find one time. With my Mede8er 600X3D in line, i have no problem for the past 3 to 4 years and even in the loop now.
Please some one can suggest any remedy.

:-) , so we both have the same 2 players.

I ended up getting NFS to work.
(my Mede8ter worked already, but with my Q5 it was necessary to disable the firewall on my Windows server).
NFS works so much better than SMB.

[Eriol]

Q5 Pro owner reporting in. I don't  have any LAN issues: I have static IP address and wlan disabled on the device. I connect through a gigabit switch to my media store using SMB. I hardly turned off my device since I bought it and never experienced connectivity issues.

I may have a wild guess here: I have experience with a few ethernet switches that has build-in "green" features like turning off (or switch to low power state) ports that has idle for a certain amount off time. In the other hand I have experience network cards that has problem with these green features and just loosing connectivity when a green feature kicks in. You can try the following if your device goes offline again:

• Look on your switch if the device port has any LED confirmation (maybe looks different then the otter devices?) about the Q5Pro's state
• Try to disconnect/reconnect the LAN cable on the device
• Try to restart the network switch (power off/on)