|
Ludek
2017-04-07 19:59
developer
~0047755
Last edited: 2017-04-07 20:01
|
To understand what the 'Automatic' choice means.
'Automatic' selects the IP address corresponding to subnet mask of the client that is accessing the server, i.e. in my case MMA has 192.168.1.101 so it uses 192.168.1.102 for MMW (under the same subnet mask).
If a client from my 'WMware Virtual Ethernet Adapter' would access MMW server then MM would use another IP (192.168.204.1) corresponding to the IP of the MM server under the WMVare subnet.
i.e. as you can see even both the clients can access the MMW server at the same time, but MMW uses different IP (corresponding to the subnet) for each of them. Therefore the 'Automatic' is the right choice in 99% of cases.
You can run command line and write command 'ipconfig /all' to see all your network interfaces and details.
--------------------------
BTW loopback (127.0.0.1) to the DeviceDescription.xml doesn't prove anything. I guess that mostly once the server isn't found by MMA then also requesting IP:Port/DeviceDescription.xml fails from the Android mobile, but doesn't fail once it is used on the MMW's PC.
|
|
|
peke
2017-04-08 15:37
developer
~0047758
Last edited: 2017-04-08 19:28
|
Something is still wrong.
After further tests to create the simplest steps to confirm MMW server is running a number of inconsistency arise if compared to Plex (used as sample app) and other apps.
1. MMW server is not always seen/accessible on refresh where plex is always seen
2. MMW server properties are usually empty and server get unavailable only restart of MMW restore properties (in case of Service it needs to be restarted manually from services or reinstalled within MMW)
3a. Default action for MMW Server is Open Device Web Page which is wrong for MM4.x (should state http://<IP>/DeviceDescription.xml instead just http://<IP>/ and for MM5 it should point to MM5 Web UI
3b. Short term as Device webpage is opening by default we should possibly create MMW server statistic Page for MM4.x showing that server is up and running despite wrong properties in point 2. Same thing for MM5 until WEBUI is made
|
|
|
|
1. Do you mean available in the Windows Explorer? By refresh you mean F5 refresh in Windows Explorer? I guess the refresh shouldn't be needed and server should just show up once it is running. In my case it is working fine, but tested on Win7, going to test on Windows 10
2&3) I will check the default action on Windows 10. Based on my tests (on Windows 7) double-clicking any server just opens Windows Media Player where the servers can be browsed. |
|
|
Ludek
2017-04-10 18:29
developer
~0047768
Last edited: 2017-04-10 19:14
|
3) I would say that "Device Web page" should be undefined (instead of current http://0.0.0.0/). The current 0.0.0.0 causes that IE is opened on Windows 10 (instead of WMP). See attached screenshot "Servers.png" for details.
=> Fixed in 4.1.16.1833
ie. now all the servers (MMW, Plex, Serviio, WMP) have presentation URL unavailable (see https://www.dropbox.com/s/2m1mpxglj4xfop0/Screenshot%202017-04-10%2021.12.47.png?dl=0 ) and thus opens in WMP by default (also in Windows 10)
1&2) Interestingly I see this issue with the others servers (not with MMW server), in my case the Plex or Serviio sometimes isn't seen in Windows Explorer although they are seen by MMW (see https://www.dropbox.com/s/ix20xj0x633z58j/Screenshot%202017-04-10%2021.06.12.png?dl=0 ), so it rather looks like a Windows Explorer refresh issue.
|
|
|
|
3) Verified 1833
1&2) Will check after I finish updating PCs to Creators update |
|
|
|
Verified 1835 |
|
