Apex Connection

[cmantis]

I was trying to help Zuska last night get his Apex up and running and couldn't get access to it from the web browser.

I had him set static ip and different ports. We checked that the gateway was his router. The only thing that was weird was the subnet was 255.255.240.0 (which means many more possible IPs). It was like this in the router.

I even had him try turning dhcp on to see if it would pick something up I missed. However no matter the ip we set or port it wouldn't connect from his browser.

Any ideas? I am usually really good at getting people up and running. Once I can connect Im sure I can help him with the rest.

 

[Widdy]

I'm assuming you're trying to access the Apex internally? Did you use the same subnet on the Apex as well? (Although DHCP should populate this value for you, assuming it's the correct value)

 

[oh207]

There are too many possibilities why it wouldn't connect. Is that the subnet on the router or the Apex, or both?
Would probably need additional details such as type of router and network config. There is also the possibility that the computer has a different config? Is the computer running dhcp or is it static IP? Confirm the gateway, etc... and lastly, but not likely, there could be a network/firewall application blocking traffic from the computer to the Apex.

 

[cmantis]

Subnet is same on router and apex. Can I change it to 255.255.255.0? Its an apple computer so not really sure how to work those things. Shouldn't really matter if computer is running dhcp or static its still connected to the network ok. Router is a netgear something. I guess firewall could be blocking but why would it block internally and I tried port 80 as well as two different ones I have used to setup multiple people.

 

[oh207]

I should also mention that if the webpages on the Apex is corrupt, or if there was an unsuccessful firmware update (both firmware and webpages), this could sometimes cause the pages not to load.
Can you successfully ping the Apex?

 

[oh207]

Just to confirm, are you able to access the Apex internally?

 

[cmantis]

No cannot access it internally is the problem. I can make changes to the apex and make changes to the router but can't get a computer on the same network to connect to the apex.

 

[Widdy]

Set the Apex to DHCP and on your Netgear configuration page, there should be an Attached Devices pages. See if you see the Apex there.

 

[oh207]

No cannot access it internally is the problem. I can make changes to the apex and make changes to the router but can't get a computer on the same network to connect to the apex.

Got it, then its likely incorrect network config on the Apex. Can you try to ping the Apex from the computer? Or try to telnet to the Apex? If none of this works, then its definitely a network config issue with the Apex. Also try replacing the ethernet cable.
If you have an Android or iPhone, can you use them to try and connect to the Apex?

If you can ping and telnet to the Apex, then the webpages on the Apex could be a problem.

 

[cmantis]

Its an Apple computer not sure how to telnet on that Im a PC guy. He said that he hasn't updated the firmware.

I tried 192.169.1.50 / 192.168.1.11 and it was originally set on 192.168.1.70 (it had been working previously then stopped)

gateway 192.169.1.1 (router)

subnet 255.255.240.0 (same as router)

ports 80 / 1234 / 4321

Set port forwarding to both tcp and udp

Can't connect over brower on computer also on network.

 

[Widdy]

Go to /Applications/Utilities and open Terminal (it may prompt for user password).

From there telnet and/or ping the Apex.

Don't need to mess with port forwarding for internal traffic.

 

[oh207]

I tried 192.169.1.50 / 192.168.1.11 and it was originally set on 192.168.1.70 (it had been working previously then stopped)
gateway 192.169.1.1 (router)

The problem is with the IP Address range you are using. 192.169.x.x are public space IP addresses and should not be used on private networks. Those IPs actually belong to someone on the internet. It is likely that the Apex is trying to resolve to the public IP address.
You will need to change the IP range to something in 192.168.x.x or 10.x.x.x

 

[LowezAkar24]

PM GreenStreet.1, he recently hooked mine up.

 

[Zuska]

Cool i will be back home on monday so i see if i can get him out here to fix it.