Receptor Remote.

[philosorhymes]

Hi all, does anyones receptor remote sit there for ages blocked and then eventually return without the name of the receptor? When it does return (after about 5-10minutes) I just type in the name of the receptor connected and it is fine. But it takes ages to timeout and let me do this. It suggests to me that some name lookup functionality is not working. Has anybody experienced such problems?

many thanks

Phil

[Curois]

I have the same problems. I can connect to the Receptor just fine typing the name myself, but it doesn't show up in the dropdown list.

Daan

[philosorhymes]

Thanks Curois so at least I know I am not alone. Does anyone know why this happens?

[Watto]

I found all those problems went away when I got a hub - all works effortlessly now

[thesoundsmith]

If Watto's comment has any relevance, then oyou may be connecting using crossover cables, I believe you need a straight-through cable to work correctly. A hub wll reverse the wire reverwal caused by two crossover cables (standard Cat5 cables are crossover style.)

[philosorhymes]

Hi Soundsmith I am indeed using a crossover cable, however, I don't believe this is the issue. I say so because, if you are connecting directly from one computer to another then you must use a crossover cable and the receptor is effectively another node on a network. If it were the cable I'd expect it to not work at all but this is not the case, it does eventually work but it takes so long to time out; when it does eventually timeout I have to manually type the name in and then everything works. It's something software, I just don't know what exactly? Do you experience these problems?

[gregh1]

Have you tried changing your shortcut to the Remote program? I'm using WinXP and this is my "Target" in the shortcut's properties:

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

In other words, I explicitly specify the "ReceptorName" (or IP address) in the command line for the Remote program.

[Curois]

I know that that will work, but it's a bit of a false solution. The point is that Receptor Remote should be able to list the receptor without telling it it's name. Phil and I wanna know why it doesn't work with our Receptors.

Daan

[philosorhymes]

Hi Gregh, thanks very much for your response, that seems like a good work around, although as Curois says there is still really an outstanding issue. Could you kindly explain the syntax to me, I could not get it to work. Many Thanks,

[ajswanson]

What is the chipset of your LAN card? I had an issue with mine (Realtek) where it would not work in crossover mode unless I did some crazy stuff with the settings (changing the duplex, forcing the mode, etc). I had to send the machine (HP) back for repair and they replaced the LAN and it worked perfect.

Is there another PC in the house you can try it with?

[gregh1]

Here's a little summary of Receptor networking:

Receptor Ethernet services are only started and stopped at power up / power down. So you need to plug a network cable in before turning on. If you forget the cable - it's going to need a full power cycle!

I use manual IPs on Receptor and my laptop (e.g. addresses like 192.168.000.040, netmask 255.255.255.000), and specify my Windows workgroup (e.g. HOME), and named the Receptor something like "MyReceptor".

I've used crossover cables directly connected, and a hub with non-crossed cables successfully, but never used Receptor's "crossover mode" (because I don't want it to do DHCP).

The Remote Control program lists my Receptor and my laptop in the drop-down. (These are the only two machines turned on at the moment.) The same two names show up in Windows.

My desktop shortcut to the Remote Control program is like this:
"C:\Program Files\Receptor Remote Control.exe" -shared MyReceptor:1

(For a list of options, run the Remote Control with -help as an option.)

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

You could skip the HOSTS/LMHOSTS part, by just putting the Receptor IP address in the shortcut, instead of "MyReceptor". Then, the shortcut would be:
"C:\Program Files\Receptor Remote Control.exe" -shared 192.168.0.40:1

If you have more than one Receptor, it makes sense to have more than one shortcut to the Remote Control program, each one pointing to a specific Receptor.