The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Rio suddenly can't find server


  • Subject: RE: Rio suddenly can't find server
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Thu, 27 Jan 2005 06:35:17 -0000


> However, today when I turned it on, it
> just sat on the Rio "searching for server" screen for about
> 30 seconds and then displayed a default (169.254...) IP
> address.

For some reason it's not seeing the dhcp server

> The service is running. One thing that I noticed is that
> dhcp.xml shows nothing where the server IP address, etc.
> should be. That is, instead of "192.168.08", I just see
"".

I assume you mean 192.168.0.8, rather than 192.168.08?

This entry has to be the full ip address that xplrionet is running on (i.e.
same as in xplrionet.xml)

> If I enter the info manually, as soon as I turn on the Rio
> and it fails to find the server, the dhcp.xml file is reset to
"".

You can only edit these files with the service stopped.

Also, although xplrionet does rewrite the dhcp.xml file - at no time does
it
change the value it read for ip address (unless some massive error is
occuring resulting in all variables being cleared).

> Short of a bad cable, which is unlikely, is there anything
> else I should be looking for?

Ensure service is stopped, edit file with full ip, restart service. Stop
service, and check ip is intact. Restart service and boot rio.

Regards
Tony



xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx

xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.