0

IP2IR: Falling at the first hurdle

Dominic Young

September 19, 2010 10:16

None

Follow

Hi

I have an IP2IR (I think - although the label on the actual device just says "iTach Ethernet"). And I'm falling at the first hurdle - I can't even see the device on my network. I have launched iHelp from within a Windows virtual machine on my Mac but it just says "searching for units" permanently. I thought the unit worked by picking up a DHCP address from the network, or alternatively via a direct connection on 192.168.1.70. Neither thing seems to work for me (for the latter I connected direct to a computer as my network is 192.168.99.x).

I'd kind of like to get things up and running. The unit is receiving packets according the the lights on the ethernet connector, but I am unable to do anything with it.

 

Thanks

 

Dominic

• Facebook
• Twitter
• LinkedIn

8 comments

• 0
  
  Josh Sherman September 20, 2010 17:38

  Hi Dominic,

  Normally, units connected to a network with DHCP enabled will automatically be assigned an IP address, which could still be happening. I will explain the process I recommend when attempting to set a static IP to a unit via a crossover connection so that it can be reconnected to the network. Attempt the direct (crossover) connection to the unit again. While plugged in (to both power/crossover), default the unit (to be in a known condition), and without disconnecting power or doing anything else to the unit, attempt to browse the embedded web page 192.168.1.70. If you are still unable to view the web page, you will need to assign your PC/Mac a static IP address located within the same subnet 192.168.1.**. From there, view the embedded web page of the unit, and assign a static IP address in the network configuration page.

  Unit's power LEDs will cycle on and off once per second once successfully connected to the network, so if your unit is connected to the network, and the power LED is blinking, the unit has obtained a DHCP address from the server. If your unit is in this state, but you cannot find it, check your router's DHCP table, and the unit's hostname/mac address should show up there. Let me know if you continue to have problems.

  ~Josh

• 0
  
  Dominic Young September 21, 2010 12:23

  Thanks. I'll check everything again. Very odd. Do you think running ihelp from a virtual machine causes any issues?

   

  Dominic

• 0
  
  Dominic Young September 25, 2010 13:16

  Josh

  So the iTach is now on my network and I have allocated it a fixed IP address on my subnet, I can see pages from its internal web server. But iHelp won't discover it and as far as I can tell iHelp is where all the action happens - the inbuilt web page offers little by way of configuration.

  iHelp is running on an instance of Windows 7 running on a Parallels virtual machine on a mac. The Windows virtual machine can also see the iTach web server...

   

  Any ideas most welcome. Apologies for schoolboy questions...

   

  Dominic

• 0
  
  Josh Sherman September 28, 2010 19:05

  There is a possibility that the iHelp utility is not working due to the windows emulation, but my guess would be that the firewall on your computer is blocking UDP traffic to the iHelp program. It sounds as though you are set up on the network and configured properly, so there is little information you would gather from the iHelp discovery utility that you do not already have. I have linked the iTach API as well as a utility called GCScan below. With these, you can begin working out how our hardware communicates and how our command syntax works. Let me know if you have any questions or run into any problems.

  http://www.globalcache.com/files/docs/API-iTach.pdf

  http://www.globalcache.com/files/software/GCScan.exe

  ~Josh

• 0
  
  John Skinner March 29, 2011 03:26

  Dominic, It could be that your virtual Windows guest has it's network set in "shared" or NAT mode and therefore can not see the iTach device. Try looking at the settings for the network connection in whatever virtual program you are using (not from within Windows) and see if you can change it to BRIDGED mode connection..
• 0
  
  Josh Sherman March 29, 2011 16:36

  The link below will take you to the website of the third party developer who created Mac beta utilities. There you will find a Mac iHelp utility beta that you could try using to find your unit.

  http://www.rmartijnr.eu/

• 0
  
  Andris Jaunzemis October 15, 2011 02:52

  I am having a similar problem with the setup of my WF2IR iTach, but on just a Windows 7 PC. I am supplying power to the device (only one LED is lit in back, I don't know if that is a good or bad sign), and the correct network is not appearing in my discover-able networks list. I also tried just connecting straight to the network by entering the correct name and selecting "open" for network security, and still nothing happens when I attempt to access 169.254.1.70. Is there something else I have to do to view ad hoc networks?

  Could this have something to do with my router's security settings? I am currently using a Linksys WRT54GL router (it's a few years old) but I don't want to just start enabling and disabling options in the router settings! I am getting a Linksys E2000 in the mail early next week, but I am hoping to have the iTach up and running before that anyway.

• 0
  
  Andris Jaunzemis October 16, 2011 21:03

  Update: I defaulted the device twice, and it started broadcasting it's network the second time around, so I was able to connect and setup the iTach finally! So it looks like I'm clear for the time being! Kind of interesting that it wasn't broadcasting until it was defaulted multiple times.. But no complaints now!