Topic: windows server R2008 and MC18 DLNA server (Read 5967 times)

petrossa · « **on:** October 29, 2012, 08:11:25 am »

Having installed MC18 on my mediaserver computer running Windows R2008 Server i cnq only connect through the local network, not via internet. When first started MC18 made changes to Firewall, and after that told me it was not reachable via internet

The other computers on the network on the same internet router with MC18 installed ARE reachable via internet, so its not a router issue, what to do?

bob · « **Reply #1 on:** October 29, 2012, 08:48:18 am »

Quote from: petrossa on October 29, 2012, 08:11:25 am

Having installed MC18 on my mediaserver computer running Windows R2008 Server i can only connect through the local network, not via internet. When first started MC18 made changes to Firewall, and after that told me it was not reachable via internet

The other computers on the network on the same internet router with MC18 installed ARE reachable via internet, so its not a router issue, what to do?

I assume you have port forwarding setup on the internet router? (52199 most likely).
Has the PC's address changed?
The current version of MC18 will ask to open the firewall for it's server incoming access port if it detects it's blocked, that sounds like what you reported.
In Media Network Options, try clicking on the access key menu and doing "test connection".

petrossa · « **Reply #2 on:** November 01, 2012, 02:18:51 am »

Yes 52199 is forwarded in the router, all computers use the same router. They all work, except the Windows Server one. I disabled the firewall and tried again to avail. If i do test connection it tells me my firewall or router blocks access. Which is kinda weird, firewall being deactivated. Could it be something in Windows Server that blocks? Security policies?

bob · « **Reply #3 on:** November 01, 2012, 09:50:03 am »

Quote from: petrossa on November 01, 2012, 02:18:51 am

Yes 52199 is forwarded in the router, all computers use the same router. They all work, except the Windows Server one. I disabled the firewall and tried again to avail. If i do test connection it tells me my firewall or router blocks access. Which is kinda weird, firewall being deactivated. Could it be something in Windows Server that blocks? Security policies?

So you have multiple machines with MC on them inside the router that you want to access from the outside?
Then you are using a port other than 52199 for the others since you can only forward 52199 from the router to one computer.
I haven't tried this before but it'd be something like:
computer A uses port 52197
computer B uses port 52198
computer C uses port 52199
And therefore you have 3 forwarding entries on the router, one for each.
Also, you statically assign the DHCP leases for A,B and C on the router?
You could check to see what the webremote key server thinks about your keys:
http://wr.jriver.com/libraryserver/lookup/your-key
or
http://wr.jriver.com/your-key?format=html

petrossa · « **Reply #4 on:** November 03, 2012, 02:39:30 pm »

The DNLA server doesn't startup up see http://yabb.jriver.com/interact/index.php?topic=75456.0
(forgot i posted this, getting old

)

JimH · « **Reply #5 on:** November 03, 2012, 02:47:49 pm »

Maybe another server is running on the same port? MC17 and MC18, for example.

petrossa · « **Reply #6 on:** November 03, 2012, 04:28:24 pm »

Nope, Uninstalled mc17,tried different port, but only the media server changes port, not this one. Always 52199

bob · « **Reply #7 on:** November 05, 2012, 10:35:34 am »

Quote from: petrossa on November 03, 2012, 04:28:24 pm

Nope, Uninstalled mc17,tried different port, but only the media server changes port, not this one. Always 52199

Just replied to your other thread, however I see here that you tried a different port (on the windows 2008 server?). I just set mine to 53199 (under Media Network->Advanced) and it switched right away, you can see it in the netstat.

petrossa · « **Reply #8 on:** November 05, 2012, 10:37:30 am »

Quote from: bob on November 01, 2012, 09:50:03 am

You could check to see what the webremote key server thinks about your keys:
http://wr.jriver.com/libraryserver/lookup/your-key
or
http://wr.jriver.com/your-key?format=html

It hates it:

MC18 IS running

bob · « **Reply #9 on:** November 05, 2012, 10:39:09 am »

It can't register the key I suppose since the Media Network won't start since it can't bind to the listener port.

petrossa · « **Reply #10 on:** November 05, 2012, 10:41:54 am »

Quote from: bob on November 05, 2012, 10:35:34 am

Just replied to your other thread, however I see here that you tried a different port (on the windows 2008 server?). I just set mine to 53199 (under Media Network->Advanced) and it switched right away, you can see it in the netstat.

WORKS!!!!! YEAH

tnx

petrossa · « **Reply #11 on:** November 05, 2012, 10:42:40 am »

And now it doesnt anymore ?

petrossa · « **Reply #12 on:** November 05, 2012, 10:45:18 am »

For a moment it seemed to work but then it got back the server not started.

bob · « **Reply #13 on:** November 05, 2012, 10:49:52 am »

Hang on, why is it still showing 52199? Mine doesn't!

petrossa · « **Reply #14 on:** November 05, 2012, 11:00:17 am »

exactly that has me confused as well. As you can see the other port is set 53199. As i stated before the dlna subscription server hangs on to 52199. I'll do an uninstall and reboot see what that gives.

bob · « **Reply #15 on:** November 05, 2012, 11:08:30 am »

Quote from: petrossa on November 05, 2012, 11:00:17 am

exactly that has me confused as well. As you can see the other port is set 53199. As i stated before the dlna subscription server hangs on to 52199. I'll do an uninstall and reboot see what that gives.

Wait a sec.
First make sure MC 17 isn't around (if Media Server from MC 17 was running as the same time as you try to run MC 18 that would cause trouble). Then delete your DLNA server and re-add it. I see one small bug in that if the DLNA server couldn't get a open port starting at 52100 it would try one port at a time all the way up to 52199 to try and get one (it should stop at 52198). I don't know why that would be the case but it's good to check.

bob · « **Reply #16 on:** November 05, 2012, 11:11:08 am »

Also, you didn't have MC 17 or 18 running as another user and/or tried to run media server under another user or in ring0?

petrossa · « **Reply #17 on:** November 05, 2012, 11:16:09 am »

I had Uninstalled everything before installing mc17. There is another dlna server running to service my cabledvr. I am now reinstalling mc18, see what happens.

petrossa · « **Reply #18 on:** November 05, 2012, 11:24:09 am »

This happens: (note, firewall is standard Windows with mc18 added with full access across the board)

petrossa · « **Reply #19 on:** November 05, 2012, 11:27:01 am »

Weirder and weirder

petrossa · « **Reply #20 on:** November 05, 2012, 11:28:38 am »

Weirdest but i'm glad

bob · « **Reply #21 on:** November 05, 2012, 11:36:59 am »

You changed it to 53179 and it works??
I'm really not getting this...
What do you have under
Options->Startup->Windows Startup ?

petrossa · « **Reply #22 on:** November 05, 2012, 11:40:23 am »

I have set my router to the port and also internet connection works now.

bob · « **Reply #23 on:** November 05, 2012, 12:22:52 pm »

Congratulations but I sure wish I could understand what was going on...

petrossa · « **Reply #24 on:** November 05, 2012, 01:16:40 pm »

Ours not to wonder why but just to do and die.

Another thing, MC18 really hates it when the server goes down. My connected computers which run MC18 and take their files from the central server via a direct path crash after the server gets rebooted.
MC18 tries to reconnect when you try to open a file, it goes a bit funny, and then it just hangs and needs to be shutdown using taskmanager.

INTERACT FORUM

Author Topic: windows server R2008 and MC18 DLNA server (Read 5967 times)