XMBC Remote Appps Unable to connect to XMBC Server

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
XMBC (Frodo) running on Windows 7

Samsung S4.

Configured the web server and remote control settings on the XMBC on Win 7.

The official XMBC remote app, and also Yatse. Neither are able to connect to the XMBC server.

I have made sure that the Windows firewall does allow XMBC.

Have tried different port numbers in the XMBC web server settings.

On the phone, used a ping app to ping the Win 7 machine. That works.

But from the phone's web browser, http://192.168.1.104 (with or without port number) fails. Also, doing the same thing from another computer on the home network also fails. Pls note the above is the internal IP for XMBC server.

I have no idea what to do. Any help would be appreciated.

Thank you
 

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
Yes I followed that guide, but the phone app just won't connect to the XMBC server.

The phone is on the same home network. I don't know if it is the same subnet, most probably should be.

The router is Linksys E-1200. I did look at the various settings in there, but could not find any isolation setting. Is there something specific I should look for?

Thanks....this is very frustrating. It should work but for some reason it it not...
 

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
Just checked. E-1200 router does not support AP isolation. So that is not the problem then.
 
Oct 16, 1999
10,490
4
0
If the XBMC machine's IP is 192.168.1.x it's on the same subnet. AP isolation might be listed as client isolation or guest mode in your router. I'd make sure you can access a shared folder on the XBMC machine to make sure it's a problem specific to XBMC. I'd also disable the firewall completely to rule it out for now. Sorry but that's probably all the help I can be.
 

poofyhairguy

Lifer
Nov 20, 2005
14,612
318
126
I agree with turning of the Windows 7 firewall completely. I had the same issue on a client until I did.
 

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
Tried with the windows firewall off. Didn't work.

Created a shared folder on the XBMC machine. Unable to access it from another computer. When I type in \\192.168.104 in windows explorer, it does show the shared folder. But unable to actually access the folder. Typing in directly \\192.168.104\sharedfoldername fails.

Have tried various settings in the Advanced Sharing Settings (control panel) - for example, password on/off, but to no avail.
 

DesiPower

Lifer
Nov 22, 2008
15,299
740
126
something tells me its a subnet problem...

For shard folder across two computers, do both of them have some workgroup names? Also, are both computes connected via wireless or both connected through Ethernet, or one wireless one Ethernet?
 

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
I haven't joined all the computers to a workgroup, thinking it is not relevant to the phone.

All the computers and the phone are connected to the same home wifi network.
 

squarecut1

Platinum Member
Nov 1, 2013
2,230
5
46
I have made some progress. Created an OpenELEC live USB stick and booted off it on my laptop (the same one that has Windows 7 on it). Initially the boot screen was freezing but was able to google the issue and resolve it.

Yatse connected fine with this Linux version of XBMC. I don't really care about if it does not connect to Win 7, as that is a temporary arrangement. Impressed with the capabilities of Yatse app.

One question (and I am not able to find the answer to it through google). In XBMC, when there is a window open and you want to exit out of it (clicking the x using the mouse), how do you do that from Yatse? The back button in Yatse does not do that in dialog boxes which require an input, e.g. adding a source and the cursor is on the input source field. I even tried the gesture pad in Yatse but it does not take the cursor to the 'x'.

Thanks for the help guys
 

vshah

Lifer
Sep 20, 2003
19,003
24
81
did you have multiple nics or ethernet + wireless under windows 7? perhaps xbmc was binding to the wrong adapter?