REMOTE ISSUES: Need original remote
-
- KVRist
- 35 posts since 3 May, 2007
I have Receptor Rev. C with system version 1.6.20070717 . I can easily see that it is connecting to my windows 7 laptop, and has been assigned an ip address and windows is sending and receiving data. Bottom line is that the remote will not recognize the receptor on the network. Due to the fact that this is an older Receptor, some threads have said that i will need the original remote. I dont have the remote and it seems that Muse isnt providing them. Anyway... does anyone have a link to the original remote 1.? not sure what version number it is. Please help.
-
- KVRist
- 197 posts since 23 Jan, 2006 from Ontario, Canada
You can use TightVNC from tightvnc.com
Download the "Self-installing package for Windows" and install the viewer only.
To connect to your Receptor, specify the name and then the password is probably "Receptor" even if you've renamed your Receptor.
Download the "Self-installing package for Windows" and install the viewer only.
To connect to your Receptor, specify the name and then the password is probably "Receptor" even if you've renamed your Receptor.
Greg Holmes
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
Retailer: Acoustic Image, BassLab, Muse Receptor, MIDIjet, Rayzoon Jamstix, and more...
http://www.ghservices.com/
http://www.gregholmes.com/
-
- KVRist
- Topic Starter
- 35 posts since 3 May, 2007
Thanks for the suggestion, and I gave it a try, yet I am still having problems. Here is what I did.
I connected the Receptor to my Windows 7 64bit laptop with a crossover cable. I set it to Crossover and said yes to the update. I then powered down the Receptor and the Laptop. With the two still connected vie crossover cable, I then fired up the laptop and waited for it to completely load, then powered up the Receptor. I looked in windows network center details, and it seemed like it hadn't fully setup everything. Just the same, I tried the Tight Vnc. No Go. Unplugged the crossover cable, and reconnected. This time it seemed to assign addresses... and was shoing that data was both sent to and received from the connect. It looked like this.
NETWORK CONNECTION DETAILS
Physical address: 00-26-B9-11-B4-23
DHCP Enabled: yes
IPv4 Address: 192.168.254.254
IPv4 Subnet Mask: 255.255.255.252
Lease Obtained: Friday, April 29,2011 11:25:06 AM
Lease Expires: Friday, April 29, 2011 11:26:06 AM
IPv4 Default Gateway : (this field has no info listed)
IPv4: Server: 192.168.254.253
IPv4 DNS server: (this field has no info listed)
IPv4 WINS Server: 192.168.254.253
NetBios over Tcip Enabled: Yes
Link-local IP6c Address: fe80:70c2:a13a:3be2:27b%11
IPv6 Default Gateway: (no info listed in this field)
Ipv6 DNS Server: fec0:0:0:ffff.:1%1
fec0:0:0:ffff.:2%1
fec0:0:0:ffff.:3%1
Fired up VNC and still no go. Once again, though already in crossover mode, i initiated it again, and shut it down, then shut the computer off. Booted it all up again in order, still connected via crossover cable, but still no go with VNC Viewer. Noticed that the Network details where still the same as listed about after I rebooted.
Is it possible that this isnt a crossover cable? I have checked and rechecked everything and I am pretty certain this is a crossover cable, but i dont know what else to do to get this working.
I connected the Receptor to my Windows 7 64bit laptop with a crossover cable. I set it to Crossover and said yes to the update. I then powered down the Receptor and the Laptop. With the two still connected vie crossover cable, I then fired up the laptop and waited for it to completely load, then powered up the Receptor. I looked in windows network center details, and it seemed like it hadn't fully setup everything. Just the same, I tried the Tight Vnc. No Go. Unplugged the crossover cable, and reconnected. This time it seemed to assign addresses... and was shoing that data was both sent to and received from the connect. It looked like this.
NETWORK CONNECTION DETAILS
Physical address: 00-26-B9-11-B4-23
DHCP Enabled: yes
IPv4 Address: 192.168.254.254
IPv4 Subnet Mask: 255.255.255.252
Lease Obtained: Friday, April 29,2011 11:25:06 AM
Lease Expires: Friday, April 29, 2011 11:26:06 AM
IPv4 Default Gateway : (this field has no info listed)
IPv4: Server: 192.168.254.253
IPv4 DNS server: (this field has no info listed)
IPv4 WINS Server: 192.168.254.253
NetBios over Tcip Enabled: Yes
Link-local IP6c Address: fe80:70c2:a13a:3be2:27b%11
IPv6 Default Gateway: (no info listed in this field)
Ipv6 DNS Server: fec0:0:0:ffff.:1%1
fec0:0:0:ffff.:2%1
fec0:0:0:ffff.:3%1
Fired up VNC and still no go. Once again, though already in crossover mode, i initiated it again, and shut it down, then shut the computer off. Booted it all up again in order, still connected via crossover cable, but still no go with VNC Viewer. Noticed that the Network details where still the same as listed about after I rebooted.
Is it possible that this isnt a crossover cable? I have checked and rechecked everything and I am pretty certain this is a crossover cable, but i dont know what else to do to get this working.
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
If the cable is ok and is crossover, connectivity/activity leds should be coming on your Laptop and the Receptor network connector sockets. Is Windows Firewall disabled?
-
- KVRist
- Topic Starter
- 35 posts since 3 May, 2007
Ya, network lights blinking, and all the data on the receptor matches the data on the windows network details page. Its connected to the network, but I dont know how to make VNC connect... and the firewall is off. Is it a port forwarding thing or something like that?