SatSig topic:

iDirect Lock problems need urgent help

(Read 7964 times)

Jul 4^th, 2008 at 7:17am

Dear All,

I was on iDirect version 6.0.9 software and everything was okay. Recently, my hub did an upgade to 7.0.7 software and my modem tells me that the remote cannot operate in this network. The rlock command returns remote locked to a specific network. On contacting the modem resellers, they swore that the sell unlocked modems and that they have been able to change providers from one to the other without any hitch. I am also confused if I was able to change to my provider, why did it happen that when the version was upgraded, the lock issue came?

I am off the air for 1 week and need to get back there. Can anyone assist plz?

Desparate Malachy

Jul 4^th, 2008 at 12:57pm

Trying to understand this. Your modem was 6.0.9 and then upgraded in the same network to 7.0.7 (then you noticed the lock?)?

Remote Locking was not a feature in iDS 6.X. It was offered in 7.X. So, if you bought the modem from an ISP that downgraded the box to use in a 6.x network you probably could have used it with no worries (undetectable) on a 6.X network. However, once your ISP moved to 7.X network (read: upgraded your modem) the lock feature immediately enabled...and became a problem.

If that is the case, you are going to have to sort it out with the ISP who sold you that iDirect unit/modem.

Jul 8^th, 2008 at 8:41am

Hello TDMA Mike,

Thankyou for your advise. I am getting stuck here and the providers are proving to me that the modem is not locked by any means at all costs. I am getting the message " [B2A3] tmp/build-package.remote-phoenix.pkg <target list> ignored" besides the continous messages of this remote cannot operate in this network.

Must this have been caused by my power outage which occured during the process of my upgrade? Because I am also unable to access my modem using new iSite 7.0.7 software?

The modem was on an initial version of 7.1.0 and I personally downgraded it to 6.0.9 and even that time i am told it was not locked.

Desparate Malachy

Jul 8^th, 2008 at 9:51am

The message " [B2A3] tmp/build-package.remote-phoenix.pkg <target list> ignored" is normal and expected. Can you cut and paste the actual 'locked' message you are seeing? You can also login to Falcon and issue the command 'rlock' at the prompt, this will tell you if the satellite router is locked by the service provider.

If the modem is locked it is only the service provider/supplier who locked it than can unlock it for you.

Jul 8^th, 2008 at 9:59am

Mike is correct, from what you are describing the modem has previously been in a network that had the RLOCK feature of the modem enabled.

The message you are seeing "tmp/build-package.remote-phoenix.pkg <target list> ignored", if your remote has Rx lock this is perfectly normal, this is a package being sent from the hub, as your remote is not in the target list of the download it ignores the package. standard for SCPC downstream.

Back to remote lock......there are two ways to unlock this modem. the first is the provider of the modem gives you the password to unlock the modem. the second is iDirect's TAC after establishing the ownership and getting approval from the original purchaser of the unit can provide an unlock for you. this can and will only be done when they have full proof that this modem is allowed to operate outside of the network it was locked to and that it has an "honest" history. You need to go to your reseller and ask them to contact iDirect with proof of ownership etc.

Whatever you do, please don't listen to the nonsense spoken on some forums about going through the recovery procedure to get it unlocked, the Rlock code has nothing to do with image or options files, it is stored elsewhere and cannot be deleted by doing a recovery. This will waste your time and frustrate you further with more downtime. The reason it operates in version 6 is exactly as Mike mentioned, the version 6 software does not check for rlock so even though it was there it did not stop the operation.

Remember an operator has placed the rlock feature on the remote for a reason....they owned the remote, if not and it can be demonstrated that it should not be locked I am sure iDirect will get it sorted for you.

Jul 10^th, 2008 at 3:28am

1. Contact the service provider and check the Hub software version and upgrade/downgrade your remote to same iDS version as hub.
2. Get the new “option file” from Hub installer and upload to your remote.
3. Make sure, your service provider “Activate” your remote at Hub.
4. Make sure, the antenna pointing is correct and P1dB done properly.
5. If you get Tx and Rx LED’s stable “Green” but still “Network” LED is OFF, speak to service provider and adjust the “tx power” of Remote and also check “rx snr” at Remote.
6. If you cannot access the modem at all by iSite, follow the below procedure:
- Connect Remote with your PC by Cisco console cable and turn on the Remote.
- Use Hyper Terminal or other applications and login to Remote.
- Use “ifconfig” command, which will give you the IP Address of the remote.
- Configure your PC LAN IP with same subnet as Remote and connect a “Straight cable”.
- Make sure, you can ping from PC to Remote.
- Use iSite to download package and option file into Remote (hope you know how to use iSite).
7. If the above (Step#6) is not success and no way to communicate with Remote; need to use “remote recovery procedure”. Contact your provider for the procedure.
Hope this helps..!