INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: anothergene on July 06, 2003, 09:19:18 am
-
Afternoon!
I can't seem to connect my media server. I've got my main pc running the media server. I'm trying to connect to it with my lap top and I keep getting the following error
Failed to cenntec to a server
Reason: Page not found.
URL http//192.168.1.100:81/GetLibrary
this is the address of my main pc. I've tried changing ports, stil the same thing.
any ideas?
-
Which version?
Same on both sides?
Are you sure you've got the port right?
Are you sure you've got the same port on both sides?
Does "Media Server - 192.168.1.100:81" show in the Media Server title bar?
Anything in the Media Server log?
What happens if you use a regular web browser and browse to "http//192.168.1.100:81/"
Did it ever work or is this the first time you've tried it?
-
Here is the info.
Media Center Registered 9.0.180 -- C:\Program Files\J River\Media Center\
Microsoft Windows 2000 Workstation 5.0 Service Pack 3 (Build 2195)
Intel Pentium 4 1994 MHz MMX / Memory: Total - 523 MB, Free - 377 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.81 / Shlwapi.dll: 6.00.2800.1106 / Shell32.dll: 5.00.3502.6144 / wnaspi32.dll: N/A
Ripping / Drive D: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: No / Play sound after ripping: No
Burning / No burners found.
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None
Same version on both sides. Yes that ip addreess is correct. I've tried in the defauly port 80, but that didn't work. that's why I tried moving it to port 81.
It's never worked... well it did work a long time ago, I can't remember what version it was, but I havn't been able to get it to work for a while.
If I go to it with a web browser I get a page not found. I'm not telling it to go that pc specifically, I just tell it to automatically find media servers and it seems to find it on the right port no matter what I change it to, but I can't seem to get past that.
-
If you run MC on the machine that is serving files, does it work?
-
nope. tried the loopback address(127.0.0.1:81) too, but no dice.
Also I can connect to and map drives on to that machine so I seriously doubt it's a conectivity issue.
g
-
Hi, That message "page not found" is not a media server error message.
Are you running a web server on that machine too?
j
-
No web server here. that's why I tried some different ports then the regular port 80 one just in case.
-
Make sure Media Server isn't running, then from a command prompt type "netstat -an" and look for any entries that end in ":81". If you find one, then something else is listening on port 81. If not, then start just the media server and again do a netstat.
You don't have the WebRemote plugin running do you?
-
Using a normal web browser, enter
<ip>:<port>
and see what you get back.
j
-
I also hat problems with Media Server this morning.
On one PC I run the newest Beta as server, on the other I ran the stable 9.0.180 version (and the official 9.0 release before).
When it searched for Remote libraries it displayed only the local library. Clicking OK crashed MC9 with some severe error I do not remember now.
Upgrading to the newest beta, so that both sides run the same version made it work again.
But the issue is, I would like to keep on one pc an official MC9 version and do beta upgrades only on the second one (my working pc). So I feel that it should be a requirement that Media Server works even if we run different MC9 versions. Or if there are major reworks, it should do a version check and say if the opposite version is outdated. That would be a graceful fallback.
-
Jaguu,
I don't think the problem was the beta vs. the non-beta, they should work fine together (in this case, may not be true for earlier versions).
j
-
Using a normal web browser, enter
<ip>:<port>
and see what you get back.
I get nothing. Well I get the page cannot be displayed.
sorry for the delay in trying it.. life's gone and gotten all busy on me!
-
Also I threw a packet sniffer on the line to see what I could see...
The client does a broadcast looking for media servers.
The server reply's to it.
I promptly get the error on the client... no more traffic even trying to talk it to it.... just an error.
I can run this on both computers with just the regular license I've purchased right? There both at home... not work involved.
-
One license will work for both if you've installed it on both.
Make sure you have the same version on both PC's.
Firewall blocking the port? Try running the server on 80 which is usually open, just to see.
-
Same problem here.
-=Tim=-
-
Version of MC? Both sides?
-
Here's the status info on the Media Server machine (this one).
07/20/03 20:23:12 - sharing thread started
07/20/03 20:23:12 - expected GET
07/20/03 20:23:12 - read_http_request failed
In the title bar it says "Media Server - 192.168.1.100:80"
I have the same MC versions on both machines, on this machine the actual info is:
Media Center Registered 9.1.218 -- C:\Program Files\J River\Media Center\
Microsoft Windows XP 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 2400 MHz MMX / Memory: Total - 523 MB, Free - 130 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1106 (xpsp1.020828-1920) / Shell32.dll: 6.00.2800.1233 (xpsp2.030604-1804) / wnaspi32.dll: N/A
Ripping / Drive E: Copy mode:ModeSecure CD Type:Auto Read speed:Max
Drive F: Copy mode:ModeSecure CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: No / Play sound after ripping: No
Burning / Drive F: AOPEN CD-RW CRW4048 Addr: 1:1:0 Speed:12 MaxSpeed:40 Use MJ Engine:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: Yes / Normalization: None
-
If you're trying to connect from another PC on the same network, and it has the same version of MC, if it fails, it must be a firewall problem or perhaps another application using the same port.
-
If you're trying to connect from another PC on the same network, and it has the same version of MC, if it fails, it must be a firewall problem or perhaps another application using the same port.
How can I diagnose either of these issues? :)
-=Tim=-
-
Hi anothergene,
Doublecheck your networking on the client computer. The IP/Port combo should return a web page. Describe your network config here.
Hi TimB,
Try the IP/Port test mentioned here and see what happens. Describe your network config including any firewalls you are running.
j
-
Hi anothergene,
Doublecheck your networking on the client computer. The IP/Port combo should return a web page. Describe your network config here.
Hi TimB,
Try the IP/Port test mentioned here and see what happens. Describe your network config including any firewalls you are running.
j
This test?
What happens if you use a regular web browser and browse to "http//192.168.1.100:81/"
Weird, when I paste in that address Mozilla Firebird took me to http://www.ttpcom.com/ttpcom/index.html. Edited out when I corrected the port to my actual port. See post below.
Firewall-wise I did add Zonealarm yesterday but the problem preexisted that. Other than that I've got my Linksys router's built-in firewall but nothing else as far as I can remember.
Network is:
2 wired PC's (1 XP (where Media Server is running), 1 98SE) connected to a Linksys Router.
1 Linksys WAP connected to a Linksys Router, the Laptop that I'm trying to connect to Media Server is coming into this WAP.
Router to Cable Modem.
Not sure what else to tell you, I'm no Network ace. ;)
Only other "weird" thing I've recently added is an m-audio Audiophile 2496 sound card. I am a software twiddler (is that illegal? ;) ) so not sure what else I might have done.
MC appears to find Media Server as it starts up but then I get the message.
-=Tim=-
-
WAIT!
Now I get this with that address:
You are not using a standard Music01 protocol to access this server.
The one I pasted in was the other person's Media Server address, mine is port 80.
-=Tim=-
-
Close - you got the address wrong. It should be:
http://192.168.1.100:81
(note the : before the //) and make sure that the IP address and port are correct for your media server.
j
-
The message, from the computer trying to contact Media Server, is:
Window Title: JRReader
Failed to connect to a server.
Reason: page not found
URL: http://192.168.1.100:80/GetLibrary
-
Close - you got the address wrong. It should be:
http://192.168.1.100:81
(note the : before the //) and make sure that the IP address and port are correct for your media server.
j
If I use this address it won't be correct for my media server. Mine reports (Window Title in Media Server) as 192.168.1.100:80
I've got the http:// right. :)
-=Tim=-
-
Sorry for all the posts folks.
If I navigate (via Mozilla Firebird) to http://192.168.1.100:80/GetLibrary I get "File Not Found"
-=Tim=-
-
Sorry for all the posts folks.
If I navigate (via Mozilla Firebird) to http://192.168.1.100:80/GetLibrary I get "File Not Found"
-=Tim=-
Sounds like you are running something else on port 80. Try switching Media Server to 81 or 39456 or something.
j
-
would port forwarding be required?
also if your using windows XP you may need to turn off windows Xp firewall not sure if windows 2000 has a built in firewall but it sure caused me problems over here when trying to setup a FTP and HTTP server.
-
Sounds like you are running something else on port 80. Try switching Media Server to 81 or 39456 or something.
j
It works! You're a smart man Mr Gateley. :)
How can I find what I have running on port 80?
-=Tim=-
-
Good. You can try to figure it out from the task manager. You can run a network sniffer and examine the reply packet closely. It'll usually have a header identifying the software. You can try to fake this by typing:
telnet 192.168.100.1 80
(note the space between the IP and 80), and then typing in a line like:
GET / HTTP/1.1
You'll probably get an error message back, but it should tell you a little about what is running.
j