FAQ  •  Register  •  Login

Two WiFi adapters, Serviio only sees one.

<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Wed Feb 15, 2017 1:34 pm

Two WiFi adapters, Serviio only sees one.

I'm trying to use two WiFi adapters on my PC. One is for a hotspot my ISP provides, and the other is for my internal WiFi that goes through my router and is connected to my cable connection.

I'm doing this so that bit torrent will use the hotspot and not cause lag when streaming 4K video from sources like Netflix... I also want Serviio to use my 5 Ghz adapter so it can handle streaming HD content to my smart TV.

If I enable both adapters, both work on my computer, but Serviio doesn't see my 5 Ghz adapter.

If I enable only one adapter, Serviio will see the adapter - it doesn't matter which adapter is enabled.

I'm unable to get Serviio to see my 5 Ghz adapter when both are enabled.

Here is my ipconfig when both are enabled.

********

Windows IP Configuration


Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Public WiFi:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d17e:c2c0:2bc5:d554%10
IPv4 Address. . . . . . . . . . . : 10.229.88.102
Subnet Mask . . . . . . . . . . . : 255.224.0.0
Default Gateway . . . . . . . . . : 10.224.0.1

Wireless LAN adapter Private WiFi:

Connection-specific DNS Suffix . : hsd1.md.comcast.net.
Link-local IPv6 Address . . . . . : fe80::9cad:77e7:d261:3059%7
IPv4 Address. . . . . . . . . . . : 192.168.1.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter isatap.{84766C47-CAC2-4BE7-81FD-AE3AFB91B61C}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:1f2b:3cc3:3e4e:3f57:fe91
Link-local IPv6 Address . . . . . : fe80::3cc3:3e4e:3f57:fe91%9
Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.hsd1.md.comcast.net.:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.md.comcast.net.

********

Here is what Serviio lists for my adapter if only the 5 Ghz card is enabled.

Image

Here is what Serviio lists for my adapters if both are enabled.

Image

Stopping and restarting Serviio doesn't help.

Any suggestions would be greatly appreciated.

Matt


Sent from my iPhone using Tapatalk
<<

atc98092

User avatar

DLNA master

Posts: 2011

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Wed Feb 15, 2017 4:33 pm

Re: Two WiFi adapters, Serviio only sees one.

That's puzzling, but Zip might have some internal explanation. Perhaps it stops searching for a NIC after it finds an active one. Just curious, have you tried altering which adapter is enabled first? Stranger things have happened. A startup log might provide some answers as well.
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Samsung UN24H4500 TV, Sony BDP-S3500, Insignia Roku TV, Roku 2 XS, 4, Ultra and Stick, Yamaha RX-V679 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

Enable debug logging
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Wed Feb 15, 2017 7:26 pm

Two WiFi adapters, Serviio only sees one.

atc98092 wrote:That's puzzling, but Zip might have some internal explanation. Perhaps it stops searching for a NIC after it finds an active one. Just curious, have you tried altering which adapter is enabled first? Stranger things have happened. A startup log might provide some answers as well.


I was previously using a wired NIC and a wireless NIC... I needed to switch to two wireless because I was previously use a Samsung blu-ray player to stream Serviio, but now I'm using a TV with WiFi. When I was using the wired & wireless, Serviio would see both NICs.

I'm not sure how to specify which adapter would be enabled first on boot up. I know I could use a script to enable the adapters in a specific order, but then I would need to implement a shutdown process that disabled them too.

Tonight I'll see about getting some logs. Both NICs work normally in my system; Serviio just doesn't see both of them.


I'd prefer not to do it, but I'm half tempted to just buy a second 5 Ghz wireless adapter... then it wouldn't matter if Serviio only saw one NIC... I'd just prefer not to spend money unnecessarily... I just bought a TV, a TV stand, a Chromecast Ultra, a 5 Ghz WiFi adapter and a 5 Ghz router.
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Fri Feb 17, 2017 11:37 am

Re: Two WiFi adapters, Serviio only sees one.

The problem is inconsistent. Sometimes both adapters will be listed, sometimes it will list only my broadcom (2.4 Ghz) adapter, and sometimes it will list only my TP-Link adapter (5 Ghz). Here is the log where Serviio found both adapters.

***

2017-02-17 06:28:47,953 DEBUG [PipeManager] Enabling processing Delta scan queue
2017-02-17 06:29:02,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:60504s
2017-02-17 06:29:02,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:02,517 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:02,519 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:60504
2017-02-17 06:29:02,519 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:02,519 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:04,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:60504s
2017-02-17 06:29:04,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:04,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:04,516 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:60504
2017-02-17 06:29:04,516 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:04,517 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:08,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:60504s
2017-02-17 06:29:08,516 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:08,517 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:08,517 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:60504
2017-02-17 06:29:08,517 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:08,517 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:08,568 DEBUG [ServiioHttpService] Incoming request from /192.168.1.129:49971: GET /deviceDescription/07f90c8c-4545-38b0-b145-074673426582 HTTP/1.1, headers = [Host: 192.168.1.129:8895,Accept-Encoding: gzip,Connection: close]]
2017-02-17 06:29:08,568 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.129
2017-02-17 06:29:08,577 DEBUG [DeviceDescriptionRequestHandler] DeviceDescription request received for device 07f90c8c-4545-38b0-b145-074673426582 from 192.168.1.129 (headers = [Host: 192.168.1.129:8895,Accept-Encoding: gzip,Connection: close])
2017-02-17 06:29:08,577 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.129
2017-02-17 06:29:08,577 DEBUG [RendererManager] Looking for a renderer profile for Http headers: [Host: 192.168.1.129:8895,Accept-Encoding: gzip,Connection: close]
2017-02-17 06:29:08,577 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.129
2017-02-17 06:29:08,707 DEBUG [DeviceDescriptionRequestHandler] Sending DeviceDescription XML back using profile 'Generic DLNA profile'
2017-02-17 06:29:14,517 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:60504s
2017-02-17 06:29:14,517 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:14,517 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.129:1900s
2017-02-17 06:29:14,518 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:14,518 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:1900
2017-02-17 06:29:14,518 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.129:60504
2017-02-17 06:29:29,819 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:29:29,820 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:29:29,820 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:29:29,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56407s
2017-02-17 06:29:29,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56407s
2017-02-17 06:29:29,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56407s
2017-02-17 06:29:35,821 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2017-02-17 06:29:43,729 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:29:43,729 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:30:35,862 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:30:35,862 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:30:35,863 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:30:35,863 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:51138s
2017-02-17 06:30:35,863 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:51138s
2017-02-17 06:30:35,863 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:51138s
2017-02-17 06:30:41,864 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2017-02-17 06:30:43,734 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:30:43,734 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:31:34,828 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53899s
2017-02-17 06:31:35,837 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53899s
2017-02-17 06:31:36,838 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53899s
2017-02-17 06:31:37,838 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53899s
2017-02-17 06:31:41,926 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:31:41,927 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:31:41,927 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:31:41,927 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:57160s
2017-02-17 06:31:41,927 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:57160s
2017-02-17 06:31:41,927 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:57160s
2017-02-17 06:31:43,734 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:31:43,734 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:31:47,927 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2017-02-17 06:32:39,703 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:63638s
2017-02-17 06:32:40,705 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:63638s
2017-02-17 06:32:41,146 DEBUG [LicensingManager] Updating license
2017-02-17 06:32:41,146 DEBUG [LicenseValidator] Validating license file (369 bytes)
2017-02-17 06:32:41,705 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:63638s
2017-02-17 06:32:42,706 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:63638s
2017-02-17 06:32:43,083 DEBUG [AccessGroupDAOImpl] Reading all AccessGroups
2017-02-17 06:32:43,104 DEBUG [RendererDAOImpl] Retrieving list of all stored renderers
2017-02-17 06:32:43,149 INFO [PlaybackProgressUpdater] Started playback progress updater
2017-02-17 06:32:43,734 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:32:43,734 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:32:46,555 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:32:47,986 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:32:47,987 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:32:47,987 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:32:47,987 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56244s
2017-02-17 06:32:47,987 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56244s
2017-02-17 06:32:47,987 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:56244s
2017-02-17 06:32:48,112 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:32:48,112 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 07f90c8c-4545-38b0-b145-074673426582
2017-02-17 06:32:50,080 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:03:19 (advertisement duration is 1800 sec.)
2017-02-17 06:32:51,544 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:32:53,987 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2017-02-17 06:32:56,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:01,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:06,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:11,545 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:16,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:21,540 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:26,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:31,541 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:34,828 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53626s
2017-02-17 06:33:35,828 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53626s
2017-02-17 06:33:36,542 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:36,829 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53626s
2017-02-17 06:33:37,829 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:53626s
2017-02-17 06:33:41,543 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:43,734 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:33:43,734 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:33:46,543 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:46,681 DEBUG [PlaylistDAOImpl] Reading all Playlists
2017-02-17 06:33:51,543 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:33:54,046 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:33:54,047 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:33:54,047 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:33:54,047 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:55383s
2017-02-17 06:33:54,047 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:55383s
2017-02-17 06:33:54,047 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:55383s
2017-02-17 06:33:56,550 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:00,047 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2017-02-17 06:34:01,543 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:06,542 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:11,544 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:17,139 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:22,141 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:27,138 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:32,136 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:37,137 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:42,138 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:43,149 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:58632s
2017-02-17 06:34:43,734 DEBUG [FeedUpdaterWorker] Checking for new and expired online resources
2017-02-17 06:34:43,734 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2017-02-17 06:34:44,151 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:58632s
2017-02-17 06:34:45,152 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:58632s
2017-02-17 06:34:46,153 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dial-multiscreen-org:service:dial:1 from address /192.168.1.129:58632s
2017-02-17 06:34:47,137 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:52,137 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:34:57,137 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
2017-02-17 06:35:00,090 DEBUG [RendererSearchSender] Searching for Renderer devices
2017-02-17 06:35:00,090 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface wlan0 (TP-LINK 802.11ac Network Adapter) and address 192.168.1.129, timeout = 0
2017-02-17 06:35:00,090 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2017-02-17 06:35:00,091 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:54956s
2017-02-17 06:35:00,091 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:54956s
2017-02-17 06:35:00,091 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.129:54956s
2017-02-17 06:35:01,540 DEBUG [MediaItemDAOImpl] Getting counts of media items by type
<<

atc98092

User avatar

DLNA master

Posts: 2011

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Fri Feb 17, 2017 2:53 pm

Re: Two WiFi adapters, Serviio only sees one.

I'll have to let Zip evaluate the log information, as he's really the only one that knows what the software is doing and how/why.

However, I do offer a suggestion. I personally would not want to run my DLNA server over wireless. I feel the server itself should be feeding your network via Ethernet, preferably Gigabit. Then let a router/wireless access point (WAP) provide connectivity for any wireless devices. I don't quite follow your reasoning to switch to wireless. If it was because you have no other WAP on the network, then I suggest getting one rather than having the computer be the WAP. It sounds like your have Internet access via wireless, but you also mention a cable connection. Without knowing more specifics, I can't make a more detailed suggestion.

Most routers can be placed into WAP mode, so you don't have to buy a WAP-specific box. Dedicated WAPs seem to cost more than a general router for some reason.
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Samsung UN24H4500 TV, Sony BDP-S3500, Insignia Roku TV, Roku 2 XS, 4, Ultra and Stick, Yamaha RX-V679 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

Enable debug logging
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Fri Feb 17, 2017 4:16 pm

Re: Two WiFi adapters, Serviio only sees one.

I switched to wireless because I bought a new TV with built in wireless that supports 4K streaming. The wireless route I'm going offers 867 Mbps speeds, so it should have more than enough bandwidth to stream much higher quality content that I typically use Serviio for. Currently I'm streaming 1080 content without any lag issues using this wireless solution.

I also don't really like having a wire going across my living room from my computer to my TV.

I'm using two different wireless adapters because I'm tapping into my personal internet connection for streaming 4K content from serves like Amazon Prime and Netflix, but I'm also downloading large files... so I want the large files to be transferred through to free hotspot my ISP offers. I don't want my large downloads to cause my 4K streaming to lag.


Sent from my iPhone using Tapatalk
<<

atc98092

User avatar

DLNA master

Posts: 2011

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Fri Feb 17, 2017 5:57 pm

Re: Two WiFi adapters, Serviio only sees one.

I understand all of that. But you don't need to run a cable across the room. I'm simply saying to use a WAP rather than your computer as the wireless point the TV connects to. Most cable routers offer wireless, as my DSL box does. But I still have two other WAPs in my home for increased coverage. But perhaps my questions below will clear it up more for me.

Assuming your primary Internet comes from your cable company, where is that box physically located? At the TV, or somewhere closer to the computer? Does it have to be there, or can you place it in a more convenient location for connecting the computer? Most homes have TV coax installed in numerous rooms, so relocating the box may or may not be feasible. I'm not saying your solution is bad. Just that there might be a more efficient way of connecting everything.

One additional thought: have you configured your PC to use the ISP hotspot as your default gateway? If not, you aren't using it as I believe you intend. Having two different NICs, both with access to the Internet, could have some issues knowing where to go. Your computer will only use one of the NICs for Internet access, unless you have some very detailing routeing rules configured on the computer. And that's not a simple thing to do.
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Samsung UN24H4500 TV, Sony BDP-S3500, Insignia Roku TV, Roku 2 XS, 4, Ultra and Stick, Yamaha RX-V679 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

Enable debug logging
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Fri Feb 17, 2017 7:34 pm

Re: Two WiFi adapters, Serviio only sees one.

The coax comes into my home in only one place, behind the TV. The computer is across the room from my TV.


Sent from my iPhone using Tapatalk
<<

atc98092

User avatar

DLNA master

Posts: 2011

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Fri Feb 17, 2017 8:57 pm

Re: Two WiFi adapters, Serviio only sees one.

If the cable box has its own wireless, you could configure a router to act as a bridge, connect it wirelessly to the cable box, then use the ports on the router as a switch and connect your computer Ethernet cable to it. Many of the modern routers have a 4 port Gigabit switch built into them.

Just tossing out ideas. We really need Zip to see if there's an answer why Serviio won't recognize two wireless cards, but will recognize a wired and wireless connection.
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Samsung UN24H4500 TV, Sony BDP-S3500, Insignia Roku TV, Roku 2 XS, 4, Ultra and Stick, Yamaha RX-V679 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

Enable debug logging
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Sat Feb 18, 2017 2:18 pm

Re: Two WiFi adapters, Serviio only sees one.

I don't have a cable box. I use Comcast for Internet, but have no TV service. I stream everything I watch on TV through Serviio, Chromecast, Netflix and Amazon Prime. My cable enters my home in one place, is connected to a DLink cable modem I own, which is connected to a Linksys E6350 WiFi router that I also own.

I decided to replace my 2.4 Ghz adapter with a second TP-Link Dual Band PCI Express Adapter. I now have two wireless adapters that are the same exact model number. I was having some minor difficulty making both adapters connect to the appropriate wireless networks automatically. While sorting this out, I saw that both networks were set as "public". I switched the internal network to private and rebooted several times. My boot-up connectivity issue is not occurring anymore and Serviio is also recognizing both adapters.

I don't know if everything is working temporarily, or if the public/private profile thing was causing windows networking issues that may have effected Serviio.

I'll keep monitoring the situation and report back in a few days (or sooner if the problem returns).

Thanks,
Matt
<<

atc98092

User avatar

DLNA master

Posts: 2011

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Sat Feb 18, 2017 5:51 pm

Re: Two WiFi adapters, Serviio only sees one.

The public/private setting never occurred to me, but it certainly might have been an issue. If it's working now, it should continue to work. At least until the next Microsoft update that messes with the firewall again. :lol:
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Samsung UN24H4500 TV, Sony BDP-S3500, Insignia Roku TV, Roku 2 XS, 4, Ultra and Stick, Yamaha RX-V679 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

Enable debug logging
<<

Matt2112

Serviio newbie

Posts: 18

Joined: Wed Feb 15, 2017 1:20 pm

Post Mon Feb 20, 2017 12:25 pm

Re: Two WiFi adapters, Serviio only sees one.

I just wanted to give some followup information about additional steps I took that I think helped.

1) SFC /SCANNOW (it found and corrected some problems for me)
2) Dism /Online /Cleanup-Image /RestoreHealth (It didn't find problems for me, but work trying)
3) I went into device manager, right clicked on my adapters, went into power management and disabled power management for my adapters
4) I added the following registry key:
Run regedit and browse to: HKLM\Software\Policies\Microsoft\Windows\WcmSvc\
See if the GroupPolicy subkey exists, if not with WcmSvc highlighted, right click on WcmSvc and Choose New -> Key and name it GroupPolicy, then click GroupPolicy and then in the right pane, (right-click) and choose New -> DWORD (32-bit) and create value, name it as fMinimizeConnections and Click OK. Now, reboot and test.

Return to Serviio Support & Help

Who is online

Users browsing this forum: No registered users and 3 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.