INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: bwanagreg on February 21, 2006, 09:58:58 am
-
I have a new Dell Axim X51V (Windows Mobile 5) and installed Activesync 4.1 and an eval of MC11 (latest build from last night) on my server (XP Pro). I set up another XP Pro machine on my home network as a MC client (same version of MC).
When the Axim is plugged in to its cradle (on the server machine), I can't get the playlists to update on the client. The client machine seems to find the server, waits for 15-20 seconds "connecting", but then stops with no song lists appearing.
When I remove the Axim from the cradle, it works fine.
Any idea what the problem is? I want to install NetRemote, but not until I get the basic library server functionality working.
-
What's the log on the server say?
j
-
Axim unplugged:
02/21/06 11:24:21 - JRiver Library Server Version 1.0.31 starting...
02/21/06 11:24:21 - Trying Port 80
02/21/06 11:24:21 - Starting Auto Detect beacon
02/21/06 11:24:21 - Running on Port 80
02/21/06 11:25:13 - Received request for version
02/21/06 11:25:13 - Sending version
02/21/06 11:25:13 - Received request for library
02/21/06 11:25:14 - Sending library
02/21/06 11:27:07 - Received request for a file: E:/Music/APE/Assorted/...(edited)
Then, I plug Axim in and try to start client: no mesages in log show up at all.
OK, then I unplug it and start the client:
02/21/06 11:34:15 - Received request for version
02/21/06 11:34:15 - Sending version
02/21/06 11:34:15 - Received request for library
02/21/06 11:34:15 - Sending library
Probably not too helpful I'm guessing.
-
Somehow the Axim's messing up the networking.
Try running Library Server on a different port...
j
-
I tried a few random port numbers last night - 81 and 20000 if I recall - without luck. Do you have any specific suggestions for ports to try?
-
81 and 20000 should be fine. It was a long shot.
I have no idea what's going on here. If you get ethereal (www.ethereal.com) and do a sniff, it should indicate what's happening to the packets.
From both the client machine and the server machine, try opening a browser
and entering:
http://192.168.0.1:80/GetVersion
where you put in the server IP address instead of 192.168.0.1, and the
actual port instead of 80. See what you get back if anything...
-
Thanks for the suggestions John. I'll try them tonight.
-
Any developments?
Dr. C