Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Eithernet connection problems


  • Please log in to reply
17 replies to this topic

#1 LlanoLonghorn

LlanoLonghorn

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 18 January 2017 - 07:36 AM

VIZIO E60OI-B3 TV with an exede UT2_10504 Wi-Fi modem

 

The TV will not connect to modem via Ethernet but will via Wi-Fi, but Win 10 desktop PC computer will. 

Anybody have any ideas why.

Thanks



BC AdBot (Login to Remove)

 


#2 LlanoLonghorn

LlanoLonghorn
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 18 January 2017 - 08:03 AM

Update: If I daisy chain my old TP-Link Wi-Fi router via Ethernet to the new exede modem and plug the TV into a port on the old router the TV connects.  

 

However if I daisy chain a NEW TP-Link Switch via Ethernet to the new exede modem and plug the TV into a port on the NEW switch the TV does NOT connect. 


Edited by LlanoLonghorn, 18 January 2017 - 08:09 AM.


#3 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 18 January 2017 - 11:02 AM

Can you plug the Windows 10 desktop into the router via ethernet, same port the TV was plugged into, and then run Minitoolbox? Choose "List content of hosts" and "List IP Configuration" and then run and post the logs.


Edited by Trikein, 18 January 2017 - 11:30 AM.


#4 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:07:44 AM

Posted 18 January 2017 - 11:19 AM

Sounds like you aren't getting a ip address when connected via Ethernet.

 

Call your satellite provider and have them troubleshoot the wifi router.



#5 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 18 January 2017 - 11:30 AM

I agree, I was just troubleshooting it a bit further. I have heard some gateways that will bridge the ethernet connection but not the wireless connection. So the wireless interface gets the public IP and internet, but then there are no IP to assign devices trying to connect via ethernet. I couldn't find mention of it in the manual, but it's only a setup manual and not complete.



#6 LlanoLonghorn

LlanoLonghorn
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 18 January 2017 - 01:19 PM

Trikein here is the results:

 

========================= IP Configuration: ================================

Realtek PCIe GBE Family Controller = Ethernet 2 (Connected)
TAP-Windows Adapter V9 = Ethernet (Media disconnected)


# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset
set global defaultcurhoplimit=64 icmpredirects=enabled taskoffload=disabled
set interface interface="Wi-Fi" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Local Area Connection* 1" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="ethernet_4" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="ethernet_3" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="ethernet_7" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="wireless_0" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="wireless_6" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_0" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_421" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_385" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_358" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_322" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_295" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_234" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="other_88" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Ethernet" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Ethernet 2" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled


popd
# End of IPv4 configuration



Windows IP Configuration

   Host Name . . . . . . . . . . . . : Win10
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ViaSatDomain

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . : ViaSatDomain
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : D4-3D-7E-37-24-41
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::21d0:ed4c:db71:4744%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.105(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, January 18, 2017 12:14:38 PM
   Lease Expires . . . . . . . . . . : Thursday, January 19, 2017 12:14:38 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 282344830
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-50-B3-24-D4-3D-7E-37-24-41
   DNS Servers . . . . . . . . . . . : 99.196.99.99
                                       99.197.99.99
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-4D-9F-36-24
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Server:  UnKnown
Address:  99.196.99.99

Name:    google.com
Addresses:  2607:f8b0:4007:80c::200e
      172.217.5.78


Pinging google.com [172.217.5.78] with 32 bytes of data:
Reply from 172.217.5.78: bytes=32 time=583ms TTL=53
Reply from 172.217.5.78: bytes=32 time=591ms TTL=53

Ping statistics for 172.217.5.78:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 583ms, Maximum = 591ms, Average = 587ms
Server:  UnKnown
Address:  99.196.99.99

Name:    yahoo.com
Addresses:  2001:4998:c:a06::2:4008
      2001:4998:58:c02::a9
      2001:4998:44:204::a7
      98.138.253.109
      206.190.36.45
      98.139.183.24


Pinging yahoo.com [206.190.36.45] with 32 bytes of data:
Reply from 206.190.36.45: bytes=32 time=623ms TTL=51
Reply from 206.190.36.45: bytes=32 time=623ms TTL=51

Ping statistics for 206.190.36.45:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 623ms, Maximum = 623ms, Average = 623ms

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
 13...d4 3d 7e 37 24 41 ......Realtek PCIe GBE Family Controller
  5...00 ff 4d 9f 36 24 ......TAP-Windows Adapter V9
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.105     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.1.0    255.255.255.0         On-link     192.168.1.105    281
    192.168.1.105  255.255.255.255         On-link     192.168.1.105    281
    192.168.1.255  255.255.255.255         On-link     192.168.1.105    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link     192.168.1.105    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link     192.168.1.105    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
 13    281 fe80::/64                On-link
 13    281 fe80::21d0:ed4c:db71:4744/128
                                    On-link
  1    331 ff00::/8                 On-link
 13    281 ff00::/8                 On-link
====================================================



#7 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 18 January 2017 - 01:31 PM

Couple odd things I see. First, you have a VPN adapter turned off. Do you run a VPN server (not client) on your network? Second, I see rules that look to forward the ethernet connection to your wireless connection, but I don't see a wireless adapter installed. Is the desktop a normal computer or does it perform some kind of server function on your network?

 

Also, if the PC is getting a valid IP, then the question is why the TV can't. Do you have the connection method set to DHCP/Automatic as found on page 34 of manual? Is there a way of seeing the connection status of the TV, or the error message you get when you try to connect via ethernet?

 

Last, you have 500-600ms latency to even Google. I wonder if the TV is trying to connect to a service of some type, but can't because the connection times out. Is that normal latency for your ISP?


Edited by Trikein, 18 January 2017 - 01:34 PM.


#8 LlanoLonghorn

LlanoLonghorn
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 18 January 2017 - 03:58 PM

I have PLEX installed on the desktop to serve local video. The PC is connected via Ethernet and not Wi-Fi. Yes the connection is set to DHCP/Auto.And the 500-600ms latency is normal for excede sat service.



#9 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 18 January 2017 - 04:15 PM

Then can you tell us more about how the TV fails to get the ethernet connection? Does it see the physical connection at all? Does it give a error message? Does it get a invalid IP like 169.x.x.x or all 0.0.0.0? Could you take a picture of the TV screen with the network status or error?

 

So far, if a PC can get a valid internet connection, but the TV can't on the same ethernet, then the I think the issue is some how related to the TV. Either a malfunction of a configuration issue.



#10 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:07:44 AM

Posted 18 January 2017 - 06:53 PM

ignore


Edited by Wand3r3r, 18 January 2017 - 07:05 PM.


#11 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 18 January 2017 - 07:16 PM

The reason you are getting weird info on the DNS is because ViaSat, owner of Exede, bought out WildBlue. See here for more info.

 

With that said, good catch on noticing they don't work. I have found posts online of people who use Exede and have used those DNS server as recently as 2014. It's possible the DNS servers may have changed, but it is also possible those DNS servers are only accessible from their network. I know because my ISP was Cox Business once and they did the same thing.

 

::Edit:: Thinking it over some more, I think we can make some assumptions. First, OP said they can get online with the desktop, so we can assume those DNS servers work for the OP.  If you want to check; Start > CMD > nslookup google.com 99.196.99.99.  However, we can also assume the DNS servers are set to static on the desktop, while the TV is trying to acquire them through DHCP. It's possible DNS via DHCP isn't working with the router. Have you tried setting the DNS on the TV to 99.196.99.99 as well?

 

Even if that works, it creates a problem. By setting your DNS as static, the devices are sending the DNS requests direct to those servers. When you set your DNS to DHCP it will relay the DNS queries through the router's cache first. Since you have a Sat. ISP, upload bandwidth is a major concerns. A DNS query that has to go into space, back down to earth and to the DNS server, then back up into space then back down to your router is going to take a LOT longer then one that can be answered directly by your router. Not only does it cause DNS, something that should happen almost instantly, to take a lot longer but it also it uses up your bandwidth. 


Edited by Trikein, 18 January 2017 - 07:57 PM.


#12 LlanoLonghorn

LlanoLonghorn
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 19 January 2017 - 01:39 PM

Trikenin, Did you see my updated post yesterday?

 

Update: If I daisy chain my old TP-Link Wi-Fi router via Ethernet to the new exede modem and plug the TV into a port on the old router the TV connects.  

 

However if I daisy chain a NEW TP-Link Switch via Ethernet to the new exede modem and plug the TV into a port on the NEW switch the TV does NOT connect.



#13 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 19 January 2017 - 01:54 PM

Yes, I read your post. Are you saying that is a acceptable work around? Daisy chaining a second router lowers performance and makes your network double NAT. If acceptable, then ignore below. If not, read on. 

 

I do think that work around does somewhat confirm the problem. The problem seems the Exede modem/gateway can't give out DNS via DHCP on ethernet. PC works on ethernet because it has static DNS, so doesn't need DHCP to aquire them. Wireless works for some unknown reason. Connecting the TV to a different router also works because it's DHCP (including DNS) is not effected by the same issue/bug. The reason a switch does NOT work is because a switch doesn't have a DHCP server, but bridges the one the switch is connected to. 

 

You still haven't answered why you are using static DNS. I think it is the core of your problem. What ever reason you require to set your PC to static DNS is causing the TV not to get it. DNS is like 411 for the internet. Without it it still has a connection, it just doesn't know how to use it.


Edited by Trikein, 19 January 2017 - 01:56 PM.


#14 LlanoLonghorn

LlanoLonghorn
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:08:44 AM

Posted 19 January 2017 - 03:13 PM

I took these pictures of the settings of the exede modem while the PC was connected to the old TP-Link Wi-Fi router via Ethernet while being daisy chained to the exede modem. Can you tell if any settings should be changed?

Attached Files

  • Attached File  1.jpg   76.5KB   0 downloads
  • Attached File  2.jpg   99.31KB   0 downloads
  • Attached File  3.jpg   45.7KB   0 downloads
  • Attached File  4.jpg   90.66KB   0 downloads
  • Attached File  5.jpg   148.89KB   0 downloads
  • Attached File  6.jpg   66.82KB   0 downloads
  • Attached File  7.jpg   77.42KB   0 downloads
  • Attached File  8.jpg   78.45KB   0 downloads


#15 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:44 AM

Posted 19 January 2017 - 03:38 PM

I think I am going to give someone else a crack at this thread. I feel I made some headway but my way of communicating is confusing you. Also, I don't know what your router settings should be because I don't have experience with Sat. ISP. If I come up with any other ideas I will post them.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users