home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
What does MP homeserver detection need at the client end, and what does the server need to transmit?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Mr Whippy" data-source="post: 1260249" data-attributes="member: 164120"><p>In this case I'm running Win7 for my server (where I think the fault is)</p><p></p><p>I've pretty much turned everything for UPnP back on, and defaulted my firewall, with appropriate inbound rules (as per base install of MP2)</p><p></p><p></p><p>Looking at logs, this seems to be a cause for concern:</p><p></p><p>server</p><p>[2019-06-29 20:48:16,570] [422 ] [Main ] [WARN ] - GENAServerController: Could not set IPv4 options</p><p>System.Net.Sockets.SocketException (0x80004005): An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call</p><p> at System.Net.Sockets.Socket.setMulticastOption(SocketOptionName optionName, MulticastOption MR)</p><p> at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Object optionValue)</p><p> at UPnP.Infrastructure.Utils.NetworkHelper.BindAndConfigureSSDPMulticastSocket(Socket socket, IPAddress address)</p><p></p><p>client</p><p>[2019-06-29 20:29:31,266] [536 ] [Main ] [WARN ] - GENAServerController: Could not set IPv4 options</p><p>System.Net.Sockets.SocketException (0x80004005): An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call</p><p> at System.Net.Sockets.Socket.setMulticastOption(SocketOptionName optionName, MulticastOption MR)</p><p> at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Object optionValue)</p><p> at UPnP.Infrastructure.Utils.NetworkHelper.BindAndConfigureSSDPMulticastSocket(Socket socket, IPAddress address)</p><p></p><p>Does anyone know if there are specific networking/UPnP debugs to help figure out where my fault lays?</p><p></p><p></p><p></p><p></p><p>More randomly, looking in the monitor logs, it seems to think the home server is an iPV6 address, despite me saying 'no' to ipv6 in the client config.</p><p></p><p>And more randomly, I set better client names (as I now have two clients, laptop client and desktop client/server), and the desktop client name is now 'mp client desktop', but it's still showing as the default 'mediaportal 2 client'</p><p></p><p></p><p>If I check in the client, the ipv6 is set to off, and the client name is as I've set it... but the server monitor is showing the default name, and the server monitor appears to be showing my client to be looking at an ipv6 address!?</p><p></p><p>I have ipv6 disabled on my win7 machine.</p><p></p><p></p><p>So yeah, pretty stuck here.</p><p></p><p></p><p></p><p>It'd be cool if there were a little EXE you could just run that ran through everything to check it worked as expected, and created logs to say what was/wasn't working.</p><p></p><p>Then at least end users could try fix their own issues. The documentation here is really lacking for MP2. And bothering developers for what might be a Win7 configuration that I can just tweak in 2 minutes, seems silly.</p><p></p><p></p><p>Thanks</p><p></p><p>Dave</p></blockquote><p></p>
[QUOTE="Mr Whippy, post: 1260249, member: 164120"] In this case I'm running Win7 for my server (where I think the fault is) I've pretty much turned everything for UPnP back on, and defaulted my firewall, with appropriate inbound rules (as per base install of MP2) Looking at logs, this seems to be a cause for concern: server [2019-06-29 20:48:16,570] [422 ] [Main ] [WARN ] - GENAServerController: Could not set IPv4 options System.Net.Sockets.SocketException (0x80004005): An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call at System.Net.Sockets.Socket.setMulticastOption(SocketOptionName optionName, MulticastOption MR) at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Object optionValue) at UPnP.Infrastructure.Utils.NetworkHelper.BindAndConfigureSSDPMulticastSocket(Socket socket, IPAddress address) client [2019-06-29 20:29:31,266] [536 ] [Main ] [WARN ] - GENAServerController: Could not set IPv4 options System.Net.Sockets.SocketException (0x80004005): An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call at System.Net.Sockets.Socket.setMulticastOption(SocketOptionName optionName, MulticastOption MR) at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Object optionValue) at UPnP.Infrastructure.Utils.NetworkHelper.BindAndConfigureSSDPMulticastSocket(Socket socket, IPAddress address) Does anyone know if there are specific networking/UPnP debugs to help figure out where my fault lays? More randomly, looking in the monitor logs, it seems to think the home server is an iPV6 address, despite me saying 'no' to ipv6 in the client config. And more randomly, I set better client names (as I now have two clients, laptop client and desktop client/server), and the desktop client name is now 'mp client desktop', but it's still showing as the default 'mediaportal 2 client' If I check in the client, the ipv6 is set to off, and the client name is as I've set it... but the server monitor is showing the default name, and the server monitor appears to be showing my client to be looking at an ipv6 address!? I have ipv6 disabled on my win7 machine. So yeah, pretty stuck here. It'd be cool if there were a little EXE you could just run that ran through everything to check it worked as expected, and created logs to say what was/wasn't working. Then at least end users could try fix their own issues. The documentation here is really lacking for MP2. And bothering developers for what might be a Win7 configuration that I can just tweak in 2 minutes, seems silly. Thanks Dave [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
What does MP homeserver detection need at the client end, and what does the server need to transmit?
Contact us
RSS
Top
Bottom
