Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Zero] Vu zero Ethernet won't connect to internet

  • Thread starter Thread starter buckman
  • Start date Start date
B

buckman

Guest
Hi guys,
Just setting up a new install of Vic 4.2.005 on a vu+zero, I have a Ethernet wired connection but when I try to connect via the wizard it keeps saying not connected to the internet, network test shows - Lan connected,local disconnected, DHCP enabled, ip add unconfirmed, nameserver unconfirmed

Stuck as what to do to get connected.
Thanks in advance
 
Try different cable and reboot both box and router.
 
strange i am having the same issue, just came on here to download the latest version and re flash.

tried rebooting network and box many times.
 
I have now got this box working with a wifi dongle from my box but can't get it to work with Ethernet at all ??
 
It can only be a dodgy ethernet cable or dodgy ethernet connector on box.
Are you connecting it direct to your router?
 
Connection via home plugs but my vu dou works fine so cable is ok, strange if it's the Ethernet connection as zero is quite new and was fine until upgrading
 
Have you tried rebooting the home plug at both ends?
 
after a reflash i still could not establish a connection via ethernet. i had to revert to wireless. all my other ethernet devices are working fine, which is strange. i will try another cable later to see if that is the issue.
 
4.2 seems to have a lot of issues that the vix team are reluctant to address.
Ive had to go back to 3.2 to fix picture problems.
Now i cant access plugins.

Ill probably get slated for this, but this is a support forum and nobody seems to answer questions, but the facts stand out for themselves....a simple script fixes my problems in 4.2 and i have no problem with 3.2....so it must be image related. But because this doesnt happen on a certian box the issue isnt looked into

Sorry again..but its true and i would like to update a box i brought from WOS.
 
Last edited:
turns out that my issue is due to a fault with the ethernet port on my router. the other port and ethernet devices work fine.

the cable to my vu+ duo2 is fine too as i tested it with the working port on the router.
 
4.2 seems to have a lot of issues that the vix team are reluctant to address.
Many of those issues seem to be specific to individual set-ups.

Ill probably get slated for this, but this is a support forum and nobody seems to answer questions, but the facts stand out for themselves....a simple script fixes my problems in 4.2 and i have no problem with 3.2....so it must be image related.
As was noted in the post that contained the script - it seems to be a driver issue.

But because this doesnt happen on a certian box the issue isnt looked into
So where did the script come from?

If you put that script into /etc/rcS.d/, make it executable and put "S10" at the start of the name it will get run at each start-up, which should at least be a work-around.

And you'll notice that the issue in this thread is nothing to do with Vix itself.
 
Many of those issues seem to be specific to individual set-ups.

As was noted in the post that contained the script - it seems to be a driver issue.

So where did the script come from?

If you put that script into /etc/rcS.d/, make it executable and put "S10" at the start of the name it will get run at each start-up, which should at least be a work-around.

And you'll notice that the issue in this thread is nothing to do with Vix itself.

I was more relating to post #8 and things not working after updating.
I wont go into my problems in this thread, but if you want to comment in my thread you might get a better understanding.

And thanks for the last bit of advice but unfortunately running the script from boot wont really help as the problem re-occurs when bringing the box out of standby.
I have no problem with vix...im wise enough to know not everything is perfect, but the lack of enthusiasm into filling customers confidence of a future fix that is clearly image related is poor
 
another variable if using powerline plugs is when the recieving powerline adapter is plugged into a power extension like a 4 way. This issue caught me out for hours (after rotating all different powerline adapters) and i realised it was the 4-way socket.
 
I have no problem with vix...im wise enough to know not everything is perfect, but the lack of enthusiasm into filling customers confidence of a future fix that is clearly image related is poor

The general consensus seems to indicate a vendor box issue, but why don,t you flash a different image from the OE-A and see what happens?
 
The general consensus seems to indicate a vendor box issue

As in the driver? i was told this area had not been changed and there was no driver updates by xtrend.

So if the same driver is/was being used from 3.2 then it cant be the driver because 3.2 runs fine.

But as suggested ill try a different image.
 
Last edited:
As in the driver? i was told this area had not been changed and there was no driver updates by xtrend.

So if the same driver is/was being used from 3.2 then it cant be the driver because 3.2 runs fine.

But as suggested ill try a different image.
... and if you still have the issue then its vendor/OE-A but then it rules out some of the discussions:)
Last driver on ET8000 was April & May 2016, well after 3.2 finished
 
Last edited:
As in the driver? i was told this area had not been changed and there was no driver updates by xtrend.

So if the same driver is/was being used from 3.2 then it cant be the driver because 3.2 runs fine.
Just because a driver hasn't been changed doesn't exclude it from having bugs which manifest themselves in future releases of vix.
 
but the lack of enthusiasm into filling customers confidence of a future fix that is clearly image related is poor

So if this is a vix issue how come there aren't countless other reports?

The team spends many hours fixing bugs and issues in their own time and free of charge. Last couple of weeks I wasted so much time and money trying to get gets feeds / plugin server running back up to speed, reading your posts makes me wonder why we bother!

It's too easy to blame vix image.....


Sent from my iPhone using Tapatalk
 

OpenViX Feeds Status

Back
Top