What Brand of Router/Modem are You Running Your Neptune Apex Through?

[Snaz]

Originally Posted by medhatreefguy

Neptune Apex Model 1.0, Serial AC4:01687, Software 4.03L_6A10
The router is a model 2700HG-E
Local IP of the Apex is 192.168.1.77
(One of the things I tried is DMZ mode where the router assigns an IP to the Apex in DCHP mode so the Apex is now assigned 199.126.209.19)

The two devices must be in the same subnet. Don't bother with the DMZ.

So if your APEX is 192.168.1.77 then your router and computer must be assigned assigned IPs in the same range. Presumably your subnet is 255.255.255.0 so my suggestion to get started would be to rebuild your network something like this:

192.168.1.1 - Router
192.168.1.2 - Computer
192.168.1.3 - APEX
Subnet Mask 255.255.255.0

The local(LAN) gateway and DNS ip for the computer and APEX is the router so with the above convention the LAN gateway and DNS is 192.168.1.1

Test that the devices can see each other with a PING from the command line. Open a CMD prompt by START-> RUN-> CMD (ENTER). This will open a black DOS box where you can type the following ping commands:

PING 192.168.1.3 (ENTER)

You should see four pings go out and come back successfully like this:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

If you see the above then your computer can "see" the APEX on your local network your almost finished. If you get "request timed out" then you have to look at the network again until you can ping each device.

Once you get the network built so computer can ping router and computer can ping APEX carry on with instructions from APEX. You might have to configure Port Forwarding in the router but try it without first.

[viperfish]

Originally Posted by Snaz

The two devices must be in the same subnet. Don't bother with the DMZ.

So if your APEX is 192.168.1.77 then your APEX must be assigned assigned an IP in the same range. Presumably your subnet is 255.255.255.0 so my suggestion to get started would be to rebuild your network something like this:

192.168.1.1 - Router
192.168.1.2 - Computer
192.168.1.3 - APEX

Test that the devices can see each other with a PING from the command line. Open a CMD prompt by START-> RUN-> CMD (ENTER). This will open a black DOS box where you can type the following ping commands:

PING 192.168.1.3 (ENTER)

You should see four pings go out and come back successfully like this:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

If you see the above then your computer can "see" the APEX on your local network your almost finished. If you get "request timed out" then you have to look at the network again until you can ping each device.

Once you get the network built so computer can ping router and computer can ping APEX carry on with instructions from APEX. You might have to configure Port Forwarding in the router but try it without first.

Hey, thanks. This is some of the most useful info I've received yet! I'll give it a try when I get home.

[PoonTang]

Yes you will have to port forward and also you will need a static ip address.
There is a very good article here on how to get it all working if you havnt seen this yet.
http://reeftech.webs.com/

[viperfish]

Everything Snaz suggested works great. I ping'd the Apex and the Modem and they are all communicating. That's all good because it's on my home network, the problem comes up when I try to access the router from a remote location via the internet. When I do that I'm dead in the water. The router does port forwarding when you enable remote access by applying a domain name which automatically tracks the DCHP mode of the modem much the same way as DynDNS does. In theory once this is all done the 2Wire internet gateway should be accessable from any computer but it appears to me that the built in firewall blocks every attempt to access the Apex. I tried opening pinholes by allowing programs but to no avail. This is definitely not a user friendly modem. There are so many different configurations that it is almost like trying to pick a combination lock by guess.

[PoonTang]

I know with my IPhone I have to have 2 different logins. One for in my house where I access it directly through the wireless network in my house using wifi. And then when I am using 3G I have to use my dyndns name. Why don't you try getting a dyndns domain name and try using it. Also with telus I found that I could not ise the default port 80 for the emails and texts.

[viperfish]

Good things to try, I'm on it! I also sent Neptune an email to see if they could shed some light.

[Snaz]

I Googled around and it looks like Telus has loaded a custom firmware on that modem/router combo which MANY people cannot get the ports to forward correctly.
http://www.google.ca/search?q=port+f...ient=firefox-a

My suggestion is to use your old dlink modem if you still have it or even better a Thompson SpeedTouch 516. Try this, take the device into any telus store and say that it overheats after 20 mins(HOT to the touch, not warm), they will surely replace it. Ask them for a Dlink or ST516, anything other than the Siemens crap. Then goto Future Shop and buy a real router like a Linksys WRT54G.

[viperfish]

Of course I threw my DLink out. I checked Kijiji and there is a DSL-300G for $20, I better grab it. Considering the amount of time I have spent messing around with the 2Wire junk, its a good buy.

[abcha0s]

Originally Posted by medhatreefguy

Of course I threw my DLink out. I checked Kijiji and there is a DSL-300G for $20, I better grab it. Considering the amount of time I have spent messing around with the 2Wire junk, its a good buy.

Don't buy it!! - You get what you pay for. Buy a LinkSys and buy it new.

[viperfish]

Originally Posted by abcha0s

Don't buy it!! - You get what you pay for. Buy a LinkSys and buy it new.

I'm talking Modem and I think you're talking router. I'm still going to go with a Linksys router, I need a Telus compatible ADSL modem and the DLink is the logical choice.