Apex Question - Ethernet Installation

[elfloyd]

Well, I've got the Apex installed with a CAT5 cable running to my wireless router. I've got both the yellow and green lights at the apex end of the cable.

I go to my browser and type in http://apex">http://apex</a> and I end up on an error page. I type in the IP Address: 192.168.1.50 and end up at a Google search results page.

DHCP is still turned on, and I have not changed any of the setting.

Anyone encounter this? Any one have a suggestion?

Thanks,
Larry

 

[jonathan]

What is the internal IP of your PC? Is it on the same 192.168.1.x network as the Apex?

Jonathan

 

[budsreef]

Larry, can you move your controller close enough to your router to plug the cat6 cable that came with the unit directly? Also from the display you can go to network setup and see what the IP and everything else is. Does that have all the correct info? Your PC needs to be within your home intranet to work.

 

[elfloyd]

Thanks guys... a bit more detail:

I have a home wireless network set up from my DSL. Connecting through the wireless router is my home PC and my work PC (wireless cards). I have the apex plugged into one of the rj connectors on the wireless router.

The Apex is mounted about 30' from the router, so I can't use the cable sent with the Apex.

Here are my PC settings: (run&gt;cmd&gt;ipconfig/all

<span style="color: Blue">Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:UsersJudy Larry&gt;ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Larry-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Compact Wireless-G USB Network Adapter with SpeedBooster
Physical Address. . . . . . . . . : 00-18-F8-A9-C9-45
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2495:77cc:ef4f:a3fe%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, October 11, 2009 11:40:27 PM
Lease Expires . . . . . . . . . . : Thursday, November 18, 2145 7:13:47 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 234887416
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controlle
r
Physical Address. . . . . . . . . : 00-18-8B-88-61-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:87f:3437:3f57:fdfd(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::87f:3437:3f57:fdfd%8(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.launchmodem.com
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.2%18(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{B89CF157-A534-4AD2-A8FD-066D73429
C63}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:UsersJudy Larry&gt;</span>

<span style="color: Black">And here is the Apex configuration:

<span style="color: Blue">DHCP: On
IP Address: 192.168.1.50
Netmask: 255.255.255.0
</span></span><span style="color: Blue">Gateway: 192.168.1.1
DNS Server: 192.168.1.1
Alt DNS: 192.168.1.1
HTTP Port: 80
</span>

 

[molson]

Looks like your network is on 192.168.2.x while your Apex is on 192.168.1.50.

My guess is that if you update the Apex IP in the configuration to 192.168.2.50 it should work.

 

[elfloyd]

Thanks Molson. Still no good. http://apex">http://apex</a> takes me to [IMG]http://www.apex.com">www.apex.com</a>, and 192.168.2.4 take me to a Google search results. I have tried with Foxfire and IE. I have listed my router config below... in case that helps.

Apex configuration changed as follows:

IP Address: 192.168.2.4 (Tried .50 but it changed to .4 when I restarted.)
Netmask: 255.255.255.0
Gateway: 192.168.2.1
DNS: 192.168.2.1
ALT DNS: 192.168.2.1


Here's my router configuration:
User ID [IMG]mailto:larry.hand@att.net">larry.hand@att.net</a> DSL Sync Up Device Name Netopia Internet Connection Up Model Number 2210-02 WAN IP Address 68.211.189.57 Serial Number 42918612 Downstream Rate 1504 (Kbits/Sec) Software Version 7.7.3r10 Upstream Rate 256 (Kbits/Sec) DHCP Server On Warranty Date 8/6/2008 Firewall Security Level Low
[B]Home Network Summary[/B]


IP Address / Name MAC Address Connection Status Connection Type 192.168.1.2/ * 00-1f-3a-8b-52-23 Active Ethernet

 

[drnecropolis]

Where does 192.168.2.1 take you?

The reason it changed from .50 is because it didn't accept a static IP

 

[elfloyd]

<u>FoxFire:</u>

The connection has timed out

The server at 192.168.2.1 is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

<u>
Internet Explorer:</u>

alt="" /> Internet Explorer cannot display the webpage

Most likely causes:


<ul>
<li>You are not connected to the Internet.</li>
<li>The website is encountering problems.</li>
<li>There might be a typing error in the address.</li>
</ul>
What you can try:

alt="" /> http://www.atlantareefclub.org/forums/#">Diagnose Connection Problems</a> [/B]

[B] [IMG]http://www.atlantareefclub.org/forums/#">[IMG]http://www.atlantareefclub.org/forums/down.png alt="" /></a>

 

[drnecropolis]

Hmmm just a shot.. That takes me to the router setup page on my belkin.. Don't know.. Network is my weakest point when it comes to pc's

 

[jonathan]

Try to ping 192.168.2.4 from a command prompt (PC) and see if it replies. The gateway IP on each device will only come into play if they were on different networks.

The http://www.apex.com">www.apex.com</a> or apex.com name resolution wont work unless you have an internal resolver.

Jonathan

 

[jonathan]

start---run---cmd--- enter

ping 192.168.2.4--- enter

Request times out or reply from?

 

[elfloyd]

<span style="color: Black">Nope.... timed out.


Ping statistics for 192.168.2.4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% locc).

Plus I confirmed the IP Address on the Apex is still 192.168.2.4 and DHCP is still ON.


</span>

 

[jonathan]

Maybe you need to reboot the apex for the IP changes to take effect.

 

[elfloyd]

Tried that with the Apex restart function. I'll power down the DLS moden, Wireless router, and Apex... wait a minute or two then power them back up one at a time.

 

[elfloyd]

Still no good.

Powered up sequentially... have the "wired" light on the router, have the yellow and green lights on the Apex. Tried pinging again... IT's GOOD!!! Successful ping, but not accessing the Apex through my Browser.

Gotta run for awhile... meeting with my boss... but IMPROVEMENT

 

[molson]

You may also want to set the IP back to 50 and turn DHCP OFF. The reason it reset to 4 is that with DHCP on, it is deferring to your router to supply the address rather than use the preset one. If you ever plan on accessing it remotely you'll want the local IP to be unchanged, otherwise every time your device or router resets it may get a different IP depending on what other devices you have hooked up.

 

[elfloyd]

OK... reset the IP Address back to 192.168.2.50. (rebooted everything too.) When I ping I get varying responses. Four pings are sent: sometimes I get 100% return, most of the time it's 50% or 75% return.

Still no good from my browser.

molson;401990 wrote: You may also want to set the IP back to 50 and turn DHCP OFF. The reason it reset to 4 is that with DHCP on, it is deferring to your router to supply the address rather than use the preset one. If you ever plan on accessing it remotely you'll want the local IP to be unchanged, otherwise every time your device or router resets it may get a different IP depending on what other devices you have hooked up.