Reply to thread

Message

<blockquote data-quote="Mr Whippy" data-source="post: 1260245" data-attributes="member: 164120">I'm running a server/client machine (which worked ok until I detached the server) on Win7, and a separate machine with a client install on Win10.&quot;Search for servers&quot; results in a message saying there are currently no MP2 servers available in the network on both machines.The service monitor is showing &quot;connected to server&quot; on the Win7 machine, and &quot;disconnected from server&quot; on the Win10 machine.I have set both clients to look to the IP (using IP address bindings) of the server via the client config.I have default inbound firewall rules, and open outbound firewall on both machines (totally default fresh install on the Win10 machine, so assuming it's my server Win7 machine that's at fault)My Win7 machine firewall notifier isn't flagging up any blocked I/O connections so I assume everything is communicating as required.I'm connecting everything via WiFi, but the client/server machine ran ok with standard loopback on 127.0.0.1What network adaptor protcols should I be using for the connection? I currently just have IPV4 on the server.Can't these settings be made explicitly anywhere? Should what I have set with the IP address bindings be sufficient?Assuming you throw a server on a Win7 server box, and media on a NAS, then clients on Win10 connecting just to the server for TV, and NAS for media/timeshift/recordings, then you don't need anything else in the network protocols except IPV4?Just getting a client to connect to the server IP over IPV4 clearly isn't enough.Thanks for any adviceDave</blockquote>

[QUOTE="Mr Whippy, post: 1260245, member: 164120"] I'm running a server/client machine (which worked ok until I detached the server) on Win7, and a separate machine with a client install on Win10. "Search for servers" results in a message saying there are currently no MP2 servers available in the network on both machines. The service monitor is showing "connected to server" on the Win7 machine, and "disconnected from server" on the Win10 machine. I have set both clients to look to the IP (using IP address bindings) of the server via the client config. I have default inbound firewall rules, and open outbound firewall on both machines (totally default fresh install on the Win10 machine, so assuming it's my server Win7 machine that's at fault) My Win7 machine firewall notifier isn't flagging up any blocked I/O connections so I assume everything is communicating as required. I'm connecting everything via WiFi, but the client/server machine ran ok with standard loopback on 127.0.0.1 What network adaptor protcols should I be using for the connection? I currently just have IPV4 on the server. Can't these settings be made explicitly anywhere? Should what I have set with the IP address bindings be sufficient? Assuming you throw a server on a Win7 server box, and media on a NAS, then clients on Win10 connecting just to the server for TV, and NAS for media/timeshift/recordings, then you don't need anything else in the network protocols except IPV4? Just getting a client to connect to the server IP over IPV4 clearly isn't enough. Thanks for any advice Dave [/QUOTE]

Verification