"Could not connect" to remote mediaportal clients (1 Viewer)

[adesimone]

Hi - I'm trying iPiMP for the first time and here is my setup:

windows xp 32-bit sp3, mediaportal 1.1.2

one mediaportal server & client
- iPiMP server/client installed here also

two mediaportal clients that connect to server
- iPiMP client plugin installed


All the clients register and appear in the iPiMP server interface. I can only connect/use iPiMP with the main server/client, but every time I try to connect to the other clients, I get 'could not connect'. I verified the server can connect to the clients on port 55667 by doing a 'telnet <client name> 556667'.

Am I doing anything wrong before I post logs?



thanks

 

[cheezey]

Nope, sounds like you're doing everything right.

Try using a browser on your server to browse to the address:

http://<clientip>:55668/mpcc

You should get a response back saying No Data.

For info the MPCC plugin listens on 55667 for TCP comms & 55668 for HTTP comms and iPiMP uses HTTP comms to communicate with it.

If that works too, read the troubleshooting section of the wiki and post some logs.

 

[adesimone]

yes, I get the following when I point to 55668 in a remote web browser

{
"result" : false,
"error" : "No data",
"errorcode" : 2
}

Also, when I go to "now Playing" on the working/local iPiMP interface, it comes back with FUBAR and a bunch of errors.

Does it work correctly with 1.1.2 as the notes seem to indicate only tested up to 1.1.1?

Great app by the way.

thanks

 

[cheezey]

Yes it works with 1.1.2 - I have that version installed.

Could you read the troubleshooting section of the wiki and post some logs.

 

[loadme]

AW: "Could not connect" to remote mediaportal clients

hey,

i read the troubleshooting in your wiki, but dont get a clue.

i have ipimp and mp installed on the same computer.
i changed the webinterface from port 80 to port 55669 during the installation.
for the installation (win7) i also shut down UAC. from that moment, i didnt get any more trouble during install (url reservation and so on worked)

i started MP config. run mpcc from plugins section, checked the port, that is set to 55667 for this client.
i am able to log in the webinterface and log in with admin/admin
there i configured my client, being the same IP.
name: bug
ip: my computers IP (with ipimp and mp1.1.2)
port: left empty
mac: left empty
moving pictures/ tv series: true

i could add the client.
now, when i finally select "media portal client" from the webinterface @safari/iphone
i takes 2 seconds and gets the error msg "could not connect"


for the time, selecting the client from webinterface, my apache log only brings up this:

192.168.178.28 - - [01/Feb/2011:18:59:56 +0100] "GET /iPhone/MPClient/MainMenu.aspx?__async=true&__source=waHome HTTP/1.1" 302 186
192.168.178.28 - - [01/Feb/2011:18:59:56 +0100] "GET /iPhone/MPClient/MPClientMenu.aspx?friendly=bug HTTP/1.1" 200 298

can you tell me, what else i should try?

thank you



edit:
i tried to get MP logs and strange things happened.
i started MP config, enabled debug mode
started MP and waited for it to run

now i rechecked ipimp webinterface from my iphone. it now showed my client and i could connect.
i really dont understand, why it wouldnt work earlier, but for now the problem seems to be solved.


thank you

 

[bigboss97]

Re: AW: "Could not connect" to remote mediaportal clients

hey,
edit:
i tried to get MP logs and strange things happened.
i started MP config, enabled debug mode
started MP and waited for it to run

now i rechecked ipimp webinterface from my iphone. it now showed my client and i could connect.
i really dont understand, why it wouldnt work earlier, but for now the problem seems to be solved.

Same here, iPiMP Setup 5.1.0.755.exe on MP 1.2 XP.
I got "Could not connect" and tried to solve the problem myself. Read through different posts and experimented around until I gave up.
When I followed the troubleshooting I changed MP log level to debug and run ipimp website from firefox. Now the client connection is fine and remote is working.
I changed the debug level back to information. It's still working hahaha...