Receptor Remote Control - time-out delay?

[swanzoid]

Hi - does anyone else see this happening ont their units? When I launch the .exe application on my WinXP PC, the "Receptor Remote Control" panel window appears fine but seems to "freeze" for several minutes. Eventually it appears to time out and subsequently presents me with the "Find Receptor" drop-down prompt, wherein I type the Receptor's IP address (since nothing shows in the drop-down list) and then connect right away with no problem. If I exit and restart the remote control I have to go through the same long delay again. Did I do something wrong when I set this up? I've tried this on two different PC's and get the same result on both. Also same result when going through a router or using a crossover cable. Thanks.

-Rob

[Robert Karasek]

prompt, wherein I type the Receptor's IP address (since nothing shows in the drop-down list) .

-Rob

I have the same problem here, too. in the drop down menu nothing is select-able... ?!

greetz
rob

[jcdawson]

Same problem here, using a crossover for Receptor, along with a wireless internet connection.
Has anyone found a workaround?

System:
Windows XP Pro SP2
AMD 64 Turion 64 Mobile
1 GB Ram

[pianodano]

Same problem here, using a crossover for Receptor, along with a wireless internet connection.
Has anyone found a workaround?

System:
Windows XP Pro SP2
AMD 64 Turion 64 Mobile
1 GB Ram

I haven't found any solution either. Same thing since I bought it back in November. Sometimes it just takes forever to show up and sometimes typing in the name dosen't work at all even after going outside and taking a break to allow time for polling (according to Muse). Fastest way I have found is to use repair metwork connection for the Receptor. I plan to give up on using the remote and just get a LCD and keyboard for it. It takes up way to much screen real estate anyway.

[thesoundsmith]

Have you given the Receptor a specific IP address, rather than asking it to fond one for itself? Mine works perfectly along with 5 other PCs and 2 Macs.

[jcdawson]

[quote="thesoundsmith"]Have you given the Receptor a specific IP address, rather than asking it to fond one for itself? Mine works perfectly along with 5 other PCs and 2 Macs.[/quote]

Thanks for your responses.

I'm having this problem using a crossover cable. I don't think DHCP comes into play here (but I may be wrong). I tried assigning an IP in the setup screen over remote control, but with the connection type set to crossover, Receptor ignores my entry and reverts back to 192.168.254.253.

Since my remote control login dropdown doesn't store ip addresses, I wonder if I'm missing some sort of config file or a registry entry where this data would normally be persisted.

[gregh1]

I use a manual IP (e.g. address like 192.168.0.40). My network cable has to be plugged into Receptor before powering up, otherwise Receptor will revert to 192.168.254.253. I've used crossover cables directly connected, and a hub with non-crossed cables successfully, but never used Receptor's "crossover mode".

For readability, I added a line to my HOSTS and LMHOSTS file (in windows/system32/drivers/etc):

192.168.0.40 myreceptor

Then, my desktop shortcut to the Remote Control program can be like this:

"C:\Program Files\Receptor Remote Control.exe" -shared MyReceptor:1

You could also just put the Receptor IP address in the shortcut, instead of "MyReceptor", and skip the HOSTS/LMHOSTS part.

[jcdawson]

Thanks, gregh1. After setting up the shortcut as you suggest, Remote Control links up immediately on launch.

Have a good one,

-jcd

[Hybernation]

I use a manual IP (e.g. address like 192.168.0.40). My network cable has to be plugged into Receptor before powering up, otherwise Receptor will revert to 192.168.254.253. I've used crossover cables directly connected, and a hub with non-crossed cables successfully, but never used Receptor's "crossover mode".

For readability, I added a line to my HOSTS and LMHOSTS file (in windows/system32/drivers/etc):

192.168.0.40 myreceptor

Then, my desktop shortcut to the Remote Control program can be like this:

"C:\Program Files\Receptor Remote Control.exe" -shared MyReceptor:1

You could also just put the Receptor IP address in the shortcut, instead of "MyReceptor", and skip the HOSTS/LMHOSTS part.

Wow. I've been living with a 2-3 minute startup since November, thinking it was normal. Used the tip above adding -shared and my fixed ip, and now I have an INSTANTANEOUS launch.

THANKS FOR THIS TIP!!

[gregh1]

I created the shortcut in March 2005 - very sorry I didn't post it sooner! (But, then again, I wasn't a member back then...)