Problem with HTPC on 802.11b

[MartinSYD]

Not sure if someone has come across this one: Using NetRemote with PPC/iPAQ, Orinoco Silver. HTPC is an IBM T20 (for now :wink:). HTPC runs Media Jukebox 8 and plugin.
Everything works fine when the T20 is on a wired LAN connection. But switching to wireless LAN (again Orinoco Silver) for some reason does not seem to work. I cen see NetRemote connecting (lots of accepted connections), but no data seems to be flowing back to NetRemote. I have tried different IP addresses and ports and of course MJ is restarted after changing ports and/or IP addresses. No luck. Going back to wired and it works like a charm. But my wife does not let me run a cable through the house....
Any ideas - happy to help with the debugging.
-Martin

[MartinSYD]

O.k. done some more problem elimination. It works in Peer-to-Peer mode. So it's the access point that screws this up. AP is a Linksys WAP11. Not the fastest thing on earth and one of the early ones, but so far it's not been giving me any problems. All protocols run through it, VPN, VNC, all no problem. Not sure why the NetRemote HTTP requests or responses get stuck there....Any ideas are much appreacited.

[brockgr]

I assume the AP hasn't got firewalling turned on? :P

VNC from the iPAQ is TCP. HTTP from the iPAQ is TCP. It must be something port related. I aslo assume this is teh latest NetRemote 0.98?

Gavin

[Ben S]

Hi Martin. Welcome.

Try upping the timeout in the MJB driver within NetRemote. My Access Point introduces what looks like a lot of latency. Upping this value to 10000 (the new default) from 1000 (the old default) has fixed this for me.

Can you use IE to "surf" the MJB WebRemote? (http://[server ip]:[port]). If this works it's definately a timeout issue. If it doesn't, then something evil is going on.

[MartinSYD]

Wow, thanks for the quick response. I changed the timeout parameter one order of magnitude up (100000ms) and now this works also on my access point. Very much appreciate the help! The delay is not really noticable, it for sure doesn't take more than 10 seconds (the default) for the response to get to MJB, but somehow changing the timeout parameter still fixes the problem.
-Martin

[Wilhelm]

Also thanks from me for that thread. I was trying to get it running the hole afternoon. Finally I got it to work with a timeout of 1000000.
Are you sure there isn't something wrong with the timeout setting in the Media Jukebox driver?

Greetings

Wilhelm