remote access difficulties

[RussM]

The SB5101 is purely a modem... not a router. I've seen this before. Try this:

1. Shut off the router and modem
2. Wait 5 minutes
3. Power up the modem
4. Wait a minute or two until the ONLINE light stops flashing (is on steady)
5. Power up the router.
6. Check the router's WAN IP address.... it should be the same as shown by whatismyip.com

 

[sowellj]

Hey Russ,

This is along the lines of what I was trying, however, when I power cycled the router the phone went dead ... you can figure out what happened from here. Bit of a 'senior moment' for me. Signal path was cable to modem to digital phone to router. the digital phone box was not visible .... and, as the saying goes, out of sigh out of mind.

I plugged the router straight into the modem and the IP addresses match. So now, it is just a matter of splitting the signal, setting the voice device up to pass through, or running the voice after the router. Thanks all for your continued help. I owe you virtual beers.

The SB5101 is purely a modem... not a router. I've seen this before. Try this:

1. Shut off the router and modem
2. Wait 5 minutes
3. Power up the modem
4. Wait a minute or two until the ONLINE light stops flashing (is on steady)
5. Power up the router.
6. Check the router's WAN IP address.... it should be the same as shown by whatismyip.com

 

[sowellj]

Well, the IP addresses match now, but I am still getting port not open from portforward.com. Back to cisco I guess?

 

[Ycore]

Post a screenshot of your port forward configuration from your linksys router

 

[sowellj]

will do ... I had to run back to the office for a bit. I'll put it up in a few hours.

 

[RussM]

Ah-ha! That phone device must have a DHCP server, whcih explains why the IP address received by the router wasn't the usual 192.168.100.x issued by the SurfBoard for management purposes. Yep, you are on the right track, I think, with putting the phone gizmo inside (connected to a LAN port on the router. Out of curiousity, what is the VoIP device?

 

[sowellj]

Hope these come out ok.

[/IMG]

[/IMG]

Those should show the port forwarding page, as well as the external IP address.

 

[RussM]

I get no response on the public IP shown in the first image (64.234.106.247). Also, sowellapex.is-a-geek.com still resolves to 64.234.51.80 (the address you had yesterday), so DDNS is not current.

Port forwarding looks fine, but you should try a nonstandard port for the external port. Despite what tech support says about not blocking anything, they might actually be doing so. Try changing the external port in the port forwarding rule to any 4-digit number > 1026.

Also, verify that the Apex's IP address is 192.168.1.199, and that the default gateway/default router value in the Apex is the same as the router's LAN IP address (probably 192.168.1.1)

 

[sowellj]

I tried switching ports and that was not successful. Also, when I go to a spot to scan ports, all ports come back as closed for my IP. I think I have the gateway, netmask, etc. entered correctly.

[/IMG]

Here is a capture of the routers netmask settings.

[/IMG]

Thanks

 

[sowellj]

Second image does not seem to have worked. I'll try again.

 

[sowellj]

note the port 8080 in the above picture was/is not correct. I was just playing around w/changing ports. However, when I went to dyndns and changed the IP associated w/my host name I (hoping) think I got things to work. Is there anything wrong w/using port 80? Also, I thought that the whole point of setting up a hostname there was that the name would stay fixed but would still associate with the changing IP addresses.

 

[RussM]

With your router, there is no need to change the http port in the Apex from its default of 80. Some routers have a more primitive port forwarding ability, which limits them to being able to forward only to the same port in the LAN - luckily, your router has the more advanced port translation features.

Did you enable & configure dyndns support in your router? Without that (or a software DDNS updater running on a PC), there is no way for dyndns to know your public IP address has changed.
BTW... it's working now... I just got the Apex login prompt :bounce3:

 

[sowellj]

I also had someone try and login and they were successful. Problem almost solved. I try to figure out how to configure ddsn in the router.

 

[sowellj]

Look OK?

 

[RussM]

I try to figure out how to configure ddsn in the router.

Setup->DDNS. Choose dyndns.org from the dropdown, then enter the same username and password you used to create your DynDNS.com account. [dyndns.com & dyndns.org are the same service]

In the hostname field, put in 'sowellapex.is-a-geek.com'; do not put http:// in there. Leave the Type set to 'Dynamic'. Disregard the mail items. Leave Wildcard disabled. Click Update; after that is done, Save Changes.

 

[RussM]

Perfect!

 

[RussM]

Now that the Apex is exposed to the Internet, if you have not already done so, change the username and password from the default values.... or at least change the password.

 

[sowellj]

Thanks everyone for your help. This eases my mind a bit about going out of town for business/vacation. PM me if you ever have chemistry questions and maybe I can repay the favor.