Sign up
 Vonage  

       
 
Vonage Forum Menu

Vonage Forums
Vonage VoIP Forum
massrman Posted:
The devices are
available at
different price
margins , please
share your
estimated
...

In The Forum:
Vonage
Topic:
IP PBX for small business
On Sep 30, 2016 at 00:48:03

massrman Posted:
Hi these are most
commonly used SIP
PBX interops and
their
configuration
guides,
...

In The Forum:
Vonage
Topic:
IP PBX for small business
On Sep 30, 2016 at 00:37:45

Sammy00 Posted:
Has anyone setup a
W52p phone for
vonage? I have
a W52p with two
wireless handsets,
...

In The Forum:
Hard Wiring - Installation
Topic:
W52p Setup
On Aug 30, 2016 at 10:38:01

James44 Posted:
Hi, I am
looking for a good
Sip Trunking
provider in
Canada. they
should offer
...

In The Forum:
Vonage
Topic:
A good sip trunking provider
On Jul 17, 2016 at 23:42:46

James44 Posted:
Which network
connection do you
use?
...

In The Forum:
Vonage
Topic:
Wireless Access Point plugged into switch
On Jul 13, 2016 at 22:55:00

jjatsk Posted:
We are renting a
few offices right
next door to our
main building. I
have a wireless
...

In The Forum:
Vonage
Topic:
Wireless Access Point plugged into switch
On Jul 09, 2016 at 12:00:54

Pman Posted:
Hello, While
Vonage has been a
great service over
the years, it is
time to part
...

In The Forum:
LNP – Local Number Portability
Topic:
Cannot port phone number to new carrier - repeated failures
On Jul 05, 2016 at 09:12:07

jbugz67 Posted:
We recently
purchased 5
Polycom VVX 300
phones from
Vonage, and have
regretted
...

In The Forum:
Vonage
Topic:
Nothing but problems with VVX300
On Apr 15, 2016 at 14:58:07

RichardPi Posted:
Hello, does
anybody recollect
how to get into
wifi password from
diggings router?
...

In The Forum:
Hard Wiring - Installation
Topic:
How to arrive at wifi password?
On Mar 31, 2016 at 02:39:07

RichardPi Posted:
Hello, does
anybody know how
to get into wifi
watchword from
home router?
...

In The Forum:
Hard Wiring - Installation
Topic:
How to be noised abroad wifi password?
On Mar 30, 2016 at 18:48:05


Vonage VoIP Forums

Vonage In The News
Vonage Holdings Corp. Reports Fourth Quarter and Full Year 2013 Results

Carolyn Katz Elected to Board of Directors of Vonage Holdings Corp.

Syndication

Vonage Customer Reviews
Vonage vs. Time Warner Cable SoCal
Vonage vs. Time Warner Cable SoCal



Vonage UK Review
Vonage UK Review



Vonage Pros and Cons for 2006
Vonage Pros and Cons for 2006



Vonage, a VT2142 and a RTP300, My Experiences - A Detailed Review
Vonage, a VT2142 and a RTP300, My Experiences - A Detailed Review



Salt Lake City: impressions after several months
Salt Lake City: impressions after several months




Vonage Reviews


Post new topic   Reply to topic  Vonage® VoIP Forum - Vonage News, Reviews And Discussion » Vonage
Author Message
Rolfkip
New Forum Member
New Forum Member


Joined: May 02, 2009
Posts: 3

PostPosted: Sat May 02, 2009 5:21 pm    Post subject: WRT160N and VDV21-VD port forwarding Reply with quote Back to top

I have tried just about everything to be able to forward a port, but have had no success so far. Could anyone explain how I could forward the port 43594 between these two routers please?

Location: Northwest Arkansas
ISP: Cox Cable

Linksys WRT160N:
Connection Type: Automatic Configuration - DHCP
Internet IP Address: 192.168.15.100
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.15.1
DNS1: 68.105.28.11
DNS2: 68.105.29.11
DNS3: 68.105.28.12

Vonage VDV21-VD:

IP address:
192.168.15.100
Subnet Mask:
255.255.255.0
Default Gateway:
70.178.117.1
DNS Servers
68.105.28.11
68.105.29.11
68.105.28.12

Computer:
Static IP: 192.168.1.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1

Webstar DPC2100R2 modem --> Vonage router --> linksys router

If you need any other information please tell.
View user's profile Send private message
VonTechMgr
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ

PostPosted: Sun May 03, 2009 9:35 am    Post subject: Reply with quote Back to top

This is very simple. First thing I want to point out is you must have typed an error as the VDV21 is connected to your modem and you show an IP address of 192.168.15.100 with a Default Gateway of 70.178.117.1. You would never be able to reach the internet because under basic networking principles, your IP address has to be on the same subnet as the Default Gateway so I am sure you just messed up copying the information over to the forum.

If the information is correct for everything else, just do the following.

On the VDV21 configure port forwarding for port 43594 to IP address 192.168.15.100 which is the WRT160N. Since you did not specify the protocol, you would need to use UDP or TCP depending upon what is needed for your application.

On the WRT160N, you would forward port 43594 using the protocol TCP or UDP needed for your application to the IP address of the computer hosting the application. In your example you have 192.168.1.2. If that is the computer IP that has the application running, then that is what you would use.

All your doing is passing the data from the public side of your network which is hitting the WAN port of the VDV21 to the next Local network component which would be the WAN port of the WRT160N which then needs to be passed to the computer's IP.
View user's profile Send private message
Rolfkip
New Forum Member
New Forum Member


Joined: May 02, 2009
Posts: 3

PostPosted: Sun May 03, 2009 12:09 pm    Post subject: Reply with quote Back to top

My default gateway at this point is 70.178.114.1. At least, that's what the VDV is telling me.

Okay, it's still not working. My goal is to be able to host others using a custom-made client with no-ip. By dling the client and typing in my no-ip address and the open port, they would be able to access a server that I have programmed.

WRT160N IP:

WRT160N PF:

WRT160N Status:

VDV21-VD Status:

VDV21-VD PF:

VDV21-VD Other:

Computer IP settings:


If there's anything else you need, please do tell.
View user's profile Send private message
VonTechMgr
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ

PostPosted: Sun May 03, 2009 3:16 pm    Post subject: Reply with quote Back to top

OK so that is not the way your listed the IP addresses in the original e-mail. However, the way you are currently displaying your IP and port forwarding data is correct. Make sure someone else from another Internet connection is testing this as it is not possible to reach your own public IP from behind your own LAN.

What I would do is first make sure your application is listening on that port. Go to start, run, type cmd and enter. At the command prompt type netstat -a Look for your hostname or IP address :43594

or

If you have another PC connected to the WRT160N, run the lcient on the other PC and try to access your server at 192.168.1.2:43594.

If you cannot find port 43594 in netstat or you can't access the server from the LAN, there is no need to investigate the networking portion since your cannot even access the server with a direct LAN connection.

If netstat shows application is Listening on 43594 but you cannot access the server from the LAN, then make sure you do not have windows firewall or any other 3rd party firewall blocking access to this port. You would need to create a rule to allow it through.

If you are able to access it from the LAN, simplify your network. Connect the PC directly to the VDV21 for starters and change the PC's IP to 192.168.15.2 and the Default GW to 192.168.15.1. This way it will mimic the WRT160N address for testing.

If you can't access the server through the Internet, remove the VDV21 from the picture. Put the WRT160N in it's place. Change the internet settings from Static IP to DHCP unless your ISP gives you a static Public IP. Try access the server from the internet now. If this works then the VDV21 is not forwarding the port. If this doesn't work, then something else is wrong. Make sure your no-ip domain has updated to the correct public IP. Have someone try to reach your server using the Public IP instead of the no-ip hostname.
View user's profile Send private message
Rolfkip
New Forum Member
New Forum Member


Joined: May 02, 2009
Posts: 3

PostPosted: Sun May 03, 2009 6:29 pm    Post subject: Reply with quote Back to top

Okay, so first, this is what I got when I typed "netstat -a" in cmd on the computer I am hosting from:
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Ryan>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            Office:0               LISTENING
  TCP    0.0.0.0:445            Office:0               LISTENING
  TCP    0.0.0.0:554            Office:0               LISTENING
  TCP    0.0.0.0:990            Office:0               LISTENING
  TCP    0.0.0.0:2869           Office:0               LISTENING
  TCP    0.0.0.0:5357           Office:0               LISTENING
  TCP    0.0.0.0:10009          Office:0               LISTENING
  TCP    0.0.0.0:10243          Office:0               LISTENING
  TCP    0.0.0.0:43594          Office:0               LISTENING
  TCP    0.0.0.0:49152          Office:0               LISTENING
  TCP    0.0.0.0:49153          Office:0               LISTENING
  TCP    0.0.0.0:49154          Office:0               LISTENING
  TCP    0.0.0.0:49155          Office:0               LISTENING
  TCP    0.0.0.0:49156          Office:0               LISTENING
  TCP    0.0.0.0:49157          Office:0               LISTENING
  TCP    0.0.0.0:49158          Office:0               LISTENING
  TCP    0.0.0.0:63331          Office:0               LISTENING
  TCP    127.0.0.1:4664         Office:0               LISTENING
  TCP    127.0.0.1:5354         Office:0               LISTENING
  TCP    127.0.0.1:5679         Office:0               LISTENING
  TCP    127.0.0.1:7438         Office:0               LISTENING
  TCP    127.0.0.1:27015        Office:0               LISTENING
  TCP    127.0.0.1:27015        Office:49178           ESTABLISHED
  TCP    127.0.0.1:27015        Office:49211           ESTABLISHED
  TCP    127.0.0.1:27015        Office:49224           ESTABLISHED
  TCP    127.0.0.1:27015        Office:49674           ESTABLISHED
  TCP    127.0.0.1:49178        Office:27015           ESTABLISHED
  TCP    127.0.0.1:49203        Office:0               LISTENING
  TCP    127.0.0.1:49211        Office:27015           ESTABLISHED
  TCP    127.0.0.1:49224        Office:27015           ESTABLISHED
  TCP    127.0.0.1:49674        Office:27015           ESTABLISHED
  TCP    127.0.0.1:49683        Office:0               LISTENING
  TCP    127.0.0.1:58030        Office:58031           ESTABLISHED
  TCP    127.0.0.1:58031        Office:58030           ESTABLISHED
  TCP    127.0.0.1:58032        Office:58033           ESTABLISHED
  TCP    127.0.0.1:58033        Office:58032           ESTABLISHED
  TCP    192.168.1.2:139        Office:0               LISTENING
  TCP    192.168.1.2:51835      192.168.15.1:http      CLOSE_WAIT
  TCP    192.168.1.2:55757      od-in-f147:http        CLOSE_WAIT
  TCP    192.168.1.2:55893      od-in-f104:http        CLOSE_WAIT
  TCP    192.168.1.2:56131      mh-in-f103:https       CLOSE_WAIT
  TCP    192.168.1.2:57623      ti-in-f99:https        CLOSE_WAIT
  TCP    192.168.1.2:57646      ti-in-f99:https        CLOSE_WAIT
  TCP    192.168.1.2:58101      a-70-183-191-122:http  ESTABLISHED
  TCP    192.168.1.2:58102      a-70-183-191-122:http  ESTABLISHED
  TCP    192.168.1.2:58104      98.174.29.147:http     ESTABLISHED
  TCP    192.168.1.2:58107      a-70-183-191-74:http   ESTABLISHED
  TCP    192.168.1.2:58113      12.20.40.108:http      ESTABLISHED
  TCP    192.168.1.2:58114      12.20.40.108:1935      ESTABLISHED
  TCP    192.168.1.2:63331      Office:0               LISTENING
  TCP    [::]:135               Office:0               LISTENING
  TCP    [::]:445               Office:0               LISTENING
  TCP    [::]:554               Office:0               LISTENING
  TCP    [::]:990               Office:0               LISTENING
  TCP    [::]:2869              Office:0               LISTENING
  TCP    [::]:5357              Office:0               LISTENING
  TCP    [::]:10243             Office:0               LISTENING
  TCP    [::]:43594             Office:0               LISTENING
  TCP    [::]:49152             Office:0               LISTENING
  TCP    [::]:49153             Office:0               LISTENING
  TCP    [::]:49154             Office:0               LISTENING
  TCP    [::]:49155             Office:0               LISTENING
  TCP    [::]:49156             Office:0               LISTENING
  TCP    [::]:49157             Office:0               LISTENING
  TCP    [::]:49158             Office:0               LISTENING
  TCP    [::]:63331             Office:0               LISTENING
  TCP    [::1]:5679             Office:0               LISTENING
  UDP    0.0.0.0:123            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5004           *:*
  UDP    0.0.0.0:5005           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:51268          *:*
  UDP    0.0.0.0:60761          *:*
  UDP    0.0.0.0:62428          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:51043        *:*
  UDP    127.0.0.1:54805        *:*
  UDP    127.0.0.1:54840        *:*
  UDP    127.0.0.1:58435        *:*
  UDP    127.0.0.1:63052        *:*
  UDP    192.168.1.2:137        *:*
  UDP    192.168.1.2:138        *:*
  UDP    192.168.1.2:1900       *:*
  UDP    192.168.1.2:5353       *:*
  UDP    192.168.1.2:54839      *:*
  UDP    [::]:123               *:*
  UDP    [::]:500               *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:5004              *:*
  UDP    [::]:5005              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:51269             *:*
  UDP    [::]:62429             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:54837            *:*
  UDP    [fe80::18c7:18b5:3f57:fefd%8]:1900  *:*
  UDP    [fe80::18c7:18b5:3f57:fefd%8]:54838  *:*
  UDP    [fe80::c567:a53f:6ca0:c3d0%12]:1900  *:*
  UDP    [fe80::c567:a53f:6ca0:c3d0%12]:54836  *:*

C:\Users\Ryan>

Office is the computer I am hosting from.

I can access my server using the ip address 192.168.1.2 and port 43594 on my client on my other PC.

When you are asking me to try routing only through the VDV, is that just temporary? The VDV has no wireless capabilities, so I really need it to still be connected. Give me a second to see if it works without the WRT.

Thanks so much for your help so far.
View user's profile Send private message
VonTechMgr
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Jan 02, 2008
Posts: 656
Location: NJ

PostPosted: Sun May 03, 2009 8:55 pm    Post subject: Reply with quote Back to top

I did mean only for testing but with any network problem, you always want to simplify things in order to find the root cause. You could just connect the WRT160N to the modem and the VDV21 to an Ethernet port on the WRT160N which would make life much easier for you in long run in case you ever needed to host other services. Traversing single NAT is much easier and more efficient then trying to go through a double NAT solution anyway.
View user's profile Send private message
trekologer
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Dec 04, 2005
Posts: 350

PostPosted: Sun May 03, 2009 9:46 pm    Post subject: Reply with quote Back to top

Quote:
TCP 0.0.0.0:43594 Office:0 LISTENING


I saw the above line and it looks like your the application is bound to a network interface that doesn't have an IP address. It also looks like Windows 6 (aka Vista) has a different output format than Windows 2000/XP so my observation could be incorrect.

However, if you have more than one network interface, can you disable to one(s) that are unused then restart the application?
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic

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

Vonage Service Plans


Vonage VoIP Members
Members List Members
New staronezSt
New Today 2
Yesterday 1
Total 98577

Who Is On Site
Visitors 204
Members 0
Total 204


Vonage VoIP Forum Members:
Login Here
Not a Member? You can Register Here
As a registered member you will have access to the VoIP Speed Test, Vonage Service Announcements and post comments in the
Vonage VoIP Forums

Vonage Stock Price
Value: 6.52
Change:   N/A
Up to 15 Minute Delay

Site Search
 






†AK and HI residents pay $29.95 shipping. ††Limited time offer. Valid for residents of the United States (&DC), 18 years or older, who open new accounts. Offer good while supplies last and only on new account activations. One kit per account/household. Offer cannot be combined with any other discounts, promotions or plans and is not applicable to past purchases. Good while supplies last. Allow up to 2 weeks for shipping. Other restrictions may apply.

1Unlimited calling and other services for all residential plans are based on normal residential, personal, non-commercial use. A combination of factors is used to determine abnormal use, including but not limited to: the number of unique numbers called, calls forwarded, minutes used and other factors. Subject to our Reasonable Use Policy and Terms of Service.

2Shipping and activation fees waived with 1-year agreement. An Early Termination Fee (with periodic pro-rated reductions) applies if service is terminated before the end of the first 12 months. Additional restrictions may apply. See Terms of Service for details.

HIGH SPEED INTERNET REQUIRED. †VALID FOR NEW LINES ONLY. RATES EXCLUDE INTERNET SERVICE, SURCHARGES, FEES AND TAXES. DEVICE MAY BE REFURBISHED. If you subscribe to plans with monthly minutes allotments, all call minutes placed from both from your home and registered ExtensionsTM phones will count toward your monthly minutes allotment. ExtensionsTM calls made from mobiles use airtime and may incur surcharges, depending on your mobile plan. Alarms, TTY and other systems may not be compatible. Vonage 911 service operates differently than traditional 911. See www.vonage.com/911 for details.

** Certain call types excluded.

www.vonage-forum.com is not an official Vonage support website & is independently operated.
All logos and trademarks are property of their respective owners. All comments are property of their posters.
All other www.vonage-forum.com content is © Copyright 2002 - 2013 by 4Sight Media LLC.

Thinking of signing up for Vonage but have questions?
Business and Residential customers can call Toll Free 24 hours a day at: 1-888-692-8074
No Vonage Promotion Code or Coupon Codes are required at www.vonage.com to receive any special,
best Vonage cheap deals, free sign up offers or discounts.

[ | | | | | ]

Vonage Forum Site Maps

Vonage | VoIP Forum | How VoIP Works | Wiring and Installation Page Two | International Rate Plans 2 | Internet Phone
Promotion | Vonage Review | VoIP | Broadband Phone | Free Month | Rebate | Vonnage | Vontage | VoIP | Phone Service
Phone | llamadas ilimitadas a Mexico | Latest News | VoIP Acronyms | Deal | Philippines Globe Phone | Site Maps

The Vonage Forum provides the Vonage sign up Best Offer Promotion Deal.
If you are considering signing up for Vonage and have found our Vonage News, Customer Reviews, Forums
& all other parts of this site useful, please use our Vonage Sign up page.


Vonage VoIP Phone Service is redefining communications by offering consumers
& small business VoIP Internet phones, an affordable alternative to traditional phone service.
The Vonage VoIP Forum Generated This Page In: 1.00 Seconds and 272 Pages In The Last 60 Seconds
The Vonage VoIP Forum