• State Not Answered
  • Date
    ewomack
  • Date
  • Replies 4 replies
  • Subscribers 185 subscribers
  • Views 3899 views
  • Users 0 members are here

Connecting by a wireless access point to the Gio

I have a GIo connected to it's own non etc network.  the Client software connects fine through all of the hardwire connections.  I would like to connect by wireless for focus and trouble shooting.

 

I am using a Linksys WAP54g access point.  I can ping in both directions but the laptop and desk will not sync over wireless.

 

Can anyone help?

  • 0

    When you say "non-ETC network, what do you mean"? How is the wireless access point connected - directly to the back of the Gio or via another switch? What is the IP addresses and subnet masks of the laptop and console?

    Depending on the strength and integrity of the wireless signal, you may find there are problems with full clients establishing and maintaining a connection.

    Luke

  • 0 in reply to luke.delwiche

    The Gio is set to 169.254.216.133.  The access point is set to 169.254.216.140.  The laptop was set to 169.254.216.148.  All three machines had the subnet mask of 255.255.0.0.  I changed the subnet masks to 255.255.255.0 and the connection was made.  The biggest issue I have right now is the the WAP54g is very slow.  I am waiting on a gigabit access point.  That should speed the connection up very much.  The network is a closed lighting network with no outside connections.

  • 0 in reply to ewomack

    169.x.x.x ip addresses get assigned to a (windows ?) computer, when it's supposed to get an IP address from a DHCP server but doesn't find one. your laptop might be trying to find said DHCP server once in a while which could explain why the connection is dropped?

    these are the default IP addresses for ETC consoles: http://community.etcconnect.com/wikis/products/knowledgebase-etc-network-ip-addresses.aspx

     

  • 0 in reply to ueliriegg

    As ueliriegg said, 169.254.x.x IPs are auto-chosen if you have set the console to look for a DHCP address and there is no DHCP server on the network.
    This will make life much more difficult.

    Your consoles should all have Static IPs.
    - It is recommended to use the ETC default IP addresses, as given above, unless you have a good reason not to!

    Usually, one of the consoles will be your DHCP address server and give an IP to Gateways, your router, your laptop etc.
    - If you are using the defaults, you can simply tick "DHCP Address Server" in the Network Services section and things will work.

    If you aren't sure, use the defaults.

    Using DHCP-assigned IPs for the console is highly discouraged as it makes a lot of things rather more complex, as the IPs can and will change. This is particularly confusing when configuring the aRFR and iRFR!
    Don't do it unless you are absolutely, 100% certain that you absolutely must.

Related

www.etcconnect.com