| Author |
Message |
cmpenney
New Forum Member


Joined: Jul 03, 2006
Posts: 4
Location: Reading, MI
|
I have a motorola 2442 ATA and although it works well for me the setup and config information available is horrible.
I want to turn on remote Web Access to configure some port forwarding and test it ( since you can't actually test it from inside the network) and I can not for the life of me figure out how to get this working.
The thing that has me baffled is the requirement of a remote IP and netmask? Does this mean you need to have the IP you will be connecting remotely to the ATA from? If so that would make this feature almost completely useless.
Leaving the setting at the default of 0.0.0.0 doesn't seem to work either. Does anyone know how to configure this correctly? |
|
|
|
|
 |
Ron_1999
New Forum Member


Joined: Jun 28, 2006
Posts: 7
|
The IP netmask 0.0.0.0 means any remote IP address is acceptable.
Good luck getting it to work! I had no luck what so ever, despite being able to do that on a SMC router.
I did get once piece of advice (not tested yet); make sure you test your forwarding from a different IP on the internet. I heard that if you just use the router's WAN IP while in the same network, the forward won't work. |
Last edited by Ron_1999 on Mon Jul 03, 2006 9:29 pm; edited 1 time in total |
|
|
|
 |
arcking
Vonage Forum Evangelist


Joined: Apr 29, 2005
Posts: 493
|
| Ron_1999 wrote: |
| make sure you test your forwarding from a different IP on the internet. I heard that if you just use the router's WAN IP while in the same network, the forward won't work. |
You can always try using a proxy. |
_________________ Comcast Cable > SB4100 > WRT54GL (Tomato) > RT31P2
Vonage customer since March 2005 |
|
|
|
 |
cmpenney
New Forum Member


Joined: Jul 03, 2006
Posts: 4
Location: Reading, MI
|
That is what I though with regard to the IP although the user guide doesn't say it.
Yeah I'm testing from work to avoind teh problem you stated and this is also why you can't test port forwarding from inside the network as well. Which is my whole reason for doing this.
The port I'm trying to set is 96 so that shouldn't be an issue for me. I tried the default 8080 but my cable company blocks some incoming standard ports such as 80 and a few others to keep people from hosting there own sites. It's possible that 8080 is being blocked as well since it is an Alt Http port so I tried 96. |
|
|
|
|
 |
cmpenney
New Forum Member


Joined: Jul 03, 2006
Posts: 4
Location: Reading, MI
|
| arcking wrote: |
| You can always try using a proxy. |
such as??? |
|
|
|
|
 |
arcking
Vonage Forum Evangelist


Joined: Apr 29, 2005
Posts: 493
|
| cmpenney wrote: |
| arcking wrote: |
| You can always try using a proxy. |
such as??? |
The Beauty of Google |
_________________ Comcast Cable > SB4100 > WRT54GL (Tomato) > RT31P2
Vonage customer since March 2005 |
|
|
|
 |
cmpenney
New Forum Member


Joined: Jul 03, 2006
Posts: 4
Location: Reading, MI
|
Thanks.. That should fix my port forwarding testing problem. I'll have teo give that a try tonight when I get home.
But it would still be nice to get the remote web access running. Any ideas for that? |
|
|
|
|
 |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum |
All times are GMT - 5 Hours | |