Webserver issues.

by **Jay** on Wed Nov 30, 2005 5:39 pm

Webserver (not server) setup on XNET page is Password: none, Port: 8002. Webserver starts at 192.168.1.7

On the XL machine, it loads immediately. I can switch a few screens and trigger perhaps one event, then it hangs and eventually 404s.

Same on a wired client machine, except that it takes around 15 seconds to load. I can switch a few screens and trigger perhaps one event, then it hangs and eventually 404s.

On a wireless machine running Win '98 (laptop is very old), it never does load.

Any ideas? TIA

by **Jay** on Thu Dec 01, 2005 3:43 pm

Solved.

Port contention with VOIP app. Changed XL Webserver port from 8002 to 88.

by **Jay** on Thu Dec 01, 2005 5:24 pm

Oops. It's a lot better and all machines have access now, but Web clients still get dumped. If I F2/XNET and hit the "Start Web Server" button after clients get dumped, I can hear a fair amount of disk activity. After start command, the clients can connect again.

Status:
Web Server: n.n.n.n:88 always shows.

Try more ports?

by **samgreco** on Thu Dec 01, 2005 6:34 pm

Jay,

I would at least try another port or 2. Port 88 is defaulted to Kerberos security. Here's a link to a text file with all of the default port assignments listed.

http://www.iana.org/assignments/port-numbers

Have fun

by **Jay** on Thu Dec 01, 2005 7:16 pm

will do and thanks! That explains (maybe) why I just discovered my old Win 98 wireless lap top is running the WS client rock-solid on 88.

by **Jay** on Thu Dec 01, 2005 9:27 pm

Update. Changing ports DID speed things up. Now using :4 tcp/udp. I have used the server client before and I just started working with the Webserver.

However, I haven't used either since I installed the HomeSeer plugin 2 days ago. Now server clients freeze as well as Webclients. Specifically, I can play music, switch cameras (RS-232) and anything else Except HS2 X-10.

Next step is to see whether HS2 events or BSC (device-level) or both are causing this.

Xl prime is flawless.

by **Jay** on Fri Dec 02, 2005 12:59 pm

doesn't matter whether I issue a BSC or TriggerEvent.

Typically, I'll trigger a X-10 event and all is well. (xAP header reads OK) The next time I try one I'll see on a Webclient like local address:4/map?x,y and it will stay there for a while then 404 (This Page cannot be Displayed). There is no 2nd xAP header as communication is lost between server and client.

As I said, I'm seeing a similar loss with XL server (port 8000) clients.

Could this be a plugin issue?

by **Jay** on Fri Dec 02, 2005 5:00 pm

I promise this will be my last report until if/when I hear anything else from the board

(unless I solve it)

It is definetly the servers that are crashing when I execute a X-10/HS2 event. I even opened up port 4 on the WS to friend on the Net. He could execute any event except that when he tried a X-10, the server locked.

PS; HS2 and XL are on different machines. Thanks for your patience.