INTERACT FORUM
More => Old Versions => Media Center 12 (Development Ended) => Topic started by: laufen on June 09, 2007, 10:03:40 am
-
Using 12.253, I can't get the another machine to load the library from another machine's Library Server. I've confirmed the Library Server is running by pulling the file with http://server/GetLibrary in FireFox. That worked fine from both remote machines I tried. MC12 however just gives me the pop up saying it couldn't couldn't load the file.
Also, is there a way to have a machine run 2 different libraries?
Thanks,
Derek
-
Are the client and the server running the same version of MC12?
-
Yep, tested with same version and even an older Library Server (10.?) I have running too. Both cases it fails to load.
My library is a big - 13K songs, 5K images, but the total size of the file is around 2.8MB which isn't much.
Like I said, I can load the file with FireFox, so the server is running. I even see log messages when I do that. What I don't see is any attempts to get the file in the log when I try to get it with MC.
I'm running 253 which I suppose isn't technically released yet. I got it to test a fix with the Tivo server. I suspect bugs were conserved when the Tivo got fixed , the LibServer got broke... ;)
Cheers,
Derek
-
Tried adding userid and password to the server to see if that made a difference. With FF the uid/pw was prompted for. With MC, there was no prompt. It really looks like MC isn't making the connection after the server is discovered.
Derek
-
I'm not sure, I'll take a look at this on monday.
j
-
I just tried, works fine.
Make a very small library and try sharing that. Let me know...
j
-
I have the same problem with the exact same fault decription. I can also pull the library file through a browser with http://server/GetLibrary. My server is running on Vista and the client on XP Pro. I saw some threads about this earlier, but I never found a solution for it.
-
Tested with library of 220 files. Same problem.
-
Please make a small library - less than 10 files, and try that.
j
-
Are y'all using "search for library servers" or did you create a library?
j
-
I've been using the "search for library" to find the servers. That seems to work fine as it finds the servers OK. When I double click the library I want it fails to load.
I tested with a small library - 18 audio files and I get the same response. "Failed to load"
This is all I see in the server window:
06/11/07 16:03:03 - JRiver Library Server Version 1.0.35 starting...
06/11/07 16:03:03 - Starting Auto Detect beacon
06/11/07 16:03:03 - Running on Port 85
Derek
-
Hi Derek - this looks like a firewall issue. It's finding the server, but the server never reports the next step. Check the firewall on the server to make sure it is configured to pass data for Media Center.
j
-
I don't think this is a firewall issue. I have the Windows firewall turned off on both client & server machines. On my server I use Avast, but I have that disabled for the time being. This same config worked fine with MC10 a couple days ago. Both machines are on a simple LAN (same switch).
Also, I can use FireFox or IE to get the file just fine.
As another test, I stopped the MC10 server I had running and now when I try to find the library servers I no longer see the list. The client just skips to the "failed to load" popup.
Other than port 85, what do I need to open up when I do enable a firewall?
Derek
-
I did the small library test, less than 10 files, with the same result. I get a popup window with the error message "Media Center failed to load Search for Library servers and will attempt to load the previously selected library". Same thing happens when I manually try to add and load a library from the library manager.
I have firewalls on both machines disabled.
-
Derek - it may not be a firewall issue, but it seems like one. The "connect" from the client to the server is not being reported on the server status page. This almost for sure means the server is not getting it. So, that leads me to believe it's a firewall type issue, perhaps not a firewall specifically, but something similar. If you can't get anywhere, make a sniff:
http://wiki.jrmediacenter.com/index.php/Sharing_Plug-in_Debugging_Hints
And I'll take a look.
tls62dk: are you running the same version on the client and server?
j
-
Great tool wireshark!. I see what is going on and it seems my server is responding with a strange response on the UDP query. Here is a summary of the payload data.
mc client: iBiE13GetMediaServerAddress
mc server: E8d$eMediaServer:pinot:0.0.0.0:85
The port and host name of the server are correct, but the ip is not right. What is with the nulls?
On another machine I put MC12 and there I do get the proper IP and can load that Lib.
Looking at the old mc 10 server running on another machine..
mc10 server:: E=I),MediaServer:mead:192.168.0.201:80
So, why is MC 12 Lib Server on my server (pinot) not filling in its IP address?
<soapbox> Why is microsoft networking so difficult? </soapbox>
Cheers,
Derek
-
<soapbox> Why is microsoft networking so difficult? </soapbox>
They're still hoping that Lan Manager/NetBios/NetBeui will crush TCP/IP.
Why did they choose to use the term "domain" for something that isn't a domain?
etc. etc.
-
So, why is MC 12 Lib Server on my server (pinot) not filling in its IP address?
Anyone got any ideas? I've tried adding entries in my hosts/lmhosts files. No change.
What API is being used inside MC to synthesize the response packet to the find server broadcast? Maybe from that I can figure out what silly thing is confusing my WinXP networking.
Thanks,
Derek
-
John,
Sorry for the slow response. Yes I run the same version of MC on server and client (12.0.251). Major difference is the OS. Server running Vista and client running XP Pro.
TLS.
-
Hi Y'all - rough day today. I'll take a look at this tomorrow...
j
-
I tried a bunch of different setting on the Window DNS and that didn't change the empty IP address in the response packet.
TLS, are you seeing the same empty IP in the response?
If nothing else, I've learned to love WireShark!
Post the API used for filling out the hostname/IP used in the response packet and I should be able to figure out where windoze is wedged.
Thanks ,
Derek
-
Derek,
I don't really know how to use Wireshark, but I am very interested to hear what you find out, seeing that my error symptoms is so similar to yours.
TLS
-
TLS - wireshark is surprisingly easy to use, It would be interesting to give it a try to see if you are having the same trouble. Just post here if you need some hints about using it.
j
-
Ok, I will give it a try.
Could one of you post a quick step for step guide on how to get the result we are looking for. I have found the application and will give it a try as soon as I have the time.
TLS
-
1) Install WireShark on the same machine as MC server.
2) Shutdown all apps that you can on your server to minimize the traffic
3) Start MC12, make sure the Library server is running
4) Start Wireshark and begin capture
Capture->Interface->start on proper interface
5) On MC running on the client machine initiate a search for libraries
6) Stop capture an look for the servers UDP response in the capture log.
http://tinyurl.com/37kkq6 (http://tinyurl.com/37kkq6)
On the capture above, look at messages 3001 - 3004. These are the request/response packets for MC. I highlighted the one from the problem server so you can see the data in the data window.
It has the right name and port - pinot and 85, but you can see the IP address in the response is 0.0.0.0.
Try the same experiment and post the contents of the server's response packet. It will be a UDP packet sourced on port 5556 like mine.
Cheers,
Derek
-
Hi Y'all,
I've been wrestling with servers for the past 2 days, and it looks like I'm not going to get to this today. Sorry for the delay, and hopefully first thing monday. I can't remember how MC assigns the reply address (you're seeing 0.0.0.0) so I can't even give any hints now.
j
-
Derek,
Thanks for your help with the Wireshark guide. I went through it today and got almost the same result as you. My server is called TLS-PC and is running on port 80, but I do get the same strange IP address of 0.0.0.0.
TLS
-
Okay - good to know. I'll check this first thing tomorrow.
j
-
Very sorry for the delay.
Library Server is getting the address by getting the host name, then getting the address info for the host name. Is it possible that your hostname is wrong?
I'm still checking here, but let me know.
j
-
Also - go to Control Panel->Network Settings. How many network interfaces are there and how many are enabled?
j
-
strange IP address of 0.0.0.0.
FYI: 0.0.0.0 is not strange at all. it means "any" IP address.
if a service running on your PC is not bound to a specific IP address it's 'sort of' bound to 0.0.0.0, i.e. all IP address on all NICs you have
try
netstat -an
from a command prompt and you'll see that
Server side, unless MC sends to clients the IP address to which the service is bound (that's where 0.0.0.0 could come from) I don't think that trying to resolve an hostname can returns 0.0.0.0 (but I've never played with Windows Net API )
-
Nevermind, found it. Turns out Vista returns a lot more information than previous OSs, and the default 1st address is incorrect.
I'll have a fix soon.
FYI: 0.0.0.0 is not strange at all. it means "any" IP address.
Sure, but a hostname should not resolve to "any" IP address. 0.0.0.0 normally occurs when passing an address in to be bound, not when asking for one.
j
-
Hi Y'all, fixed in 12.0.260 or higher. If you would like to try this out and can't get the beta, drop me an email at gateley @ jriver.com
j
-
Great! I have already send you an e-mail. Lookng forward to trying this.
TLS
-
Glad to hear something was found. I still don't understand why one of my XP boxes was working OK and the other returning a null address. I'll test the patch when I get back from my trip. I'm on the road until the end of the month so testing is a bit hard at the moment, but I'm looking forward to the patch.
Cheers,
Derek
-
I still don't understand why one of my XP boxes was working OK and the other returning a null address.
The 0.0.0.0 wasn't a real address, it was a piece of an IPv6 address, so it could have been that one of your XP boxes had IPv6 stuff and the other didn't.
j
-
John,
I got the 12.0.260 beta, thanks!. With that version installed on server and client, everything is now working again.
Thank you for you quick response and all your help.
TLS