ATA with Internet Sharing (XP)

Posts: 7 · New Forum Member Joined: Mar 06, 2010 Posts: 7

I have wireless internet sharing enabled on one of my PCs and am able to connect other computers to internet through it.

I connected the Vonage device and connected it using a crossover cable. The device shows "connected to internet" but in the logs it shows that it failed when connecting to Vonage network. Even with this, when I connected a Pc (PC2) behind the Vonage device

PC1 --> ATA --> PC2

PC2 was able to connect to internet and I was able to function. So I am unsure as to why Vonage device is not able to connect / register to Vonage network.

PS: Vonage device works if I directly connect it to my router. I am using FIOS.

Posts: 86 · Vonage Forum Senior Joined: Jan 03, 2009 Posts: 86

could be a DNS or a firewall issue of the host PC

Posts: 7 · New Forum Member Joined: Mar 06, 2010 Posts: 7

Thanks for the reply. I have checked and the firewalls are disabled on PC1 . How do I check if its a DNS issue?

Posts: 86 · Vonage Forum Senior Joined: Jan 03, 2009 Posts: 86

is the Vonage box VDV21?
log into the Vonage box from PC2 (192.168.15.1)
Check the WAN port status and address

Posts: 7 · New Forum Member Joined: Mar 06, 2010 Posts: 7

Sorry for the late reply, here are the details I see on the status page

Hardware Version:
155
Software Version:
3.1.2-0.3.5
Internet Status:
Connected
Ethernet Status:
Connected
Current Time:
Tue Mar 09 19:02:47 2010
Phone 1:
Enabled
Phone 2:

Internet Connection Status
IP Address:
192.168.0.166
MAC Address:
90:4c:e5:75:ad:cd
Subnet Mask:
255.255.255.0
Default Gateway:
192.168.0.1
Duration:
D: 07 H: 00 M: 00 S: 00
Expires:
Tue Mar 16 19:00:20 2010
DNS Servers
192.168.0.1
Disabled
Configuration Server:
Device negotiated with the configuration server successfully.
Parental Control:
Disabled

Posts: 86 · Vonage Forum Senior Joined: Jan 03, 2009 Posts: 86

can PC 2 tracert to vonage.net with success?

Posts: 7 · New Forum Member Joined: Mar 06, 2010 Posts: 7

It seems like tracert to vonage.net is failing. But works for other websites

tracert vonage.net

Tracing route to vonage.net [69.59.253.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms MyComp.mshome.net [192.168.0.1]
2 3 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
3 8 ms 7 ms 7 ms L100.CMDNNJ-VFTTP-35.verizon-gni.net [98.110.91.1]
4 10 ms 6 ms 7 ms 3-0-5-435.CMDNNJ-LCR-04.verizon-gni.net [130.81.146.42]
5 21 ms 19 ms 19 ms P10-0-0.CMDNNJ-LCR-03.verizon-gni.net [130.81.27.249]
6 20 ms 15 ms 16 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
7 20 ms 20 ms 19 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
8 23 ms 21 ms 17 ms xe-10-2-0.edge2.NewYork2.level3.net [4.68.110.233]
9 18 ms 17 ms 17 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
10 23 ms 19 ms 19 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
11 45 ms 29 ms 22 ms ae-6-6.car2.Philadelphia1.Level3.net [4.69.133.169]
12 23 ms 22 ms 22 ms ge-9-2.hsa2.Philadelphia1.Level3.net [4.69.142.46]
13 26 ms 25 ms 24 ms VONAGE-HOLDI.hsa2.Philadelphia1.Level3.net [4.78.147.110]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

TRace complete

racing route to google.com [66.249.90.104]
ver a maximum of 30 hops:

1 <1 ms <1 ms <1 ms MyComp.mshome.net [192.168.0.1]
2 3 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
3 9 ms 7 ms 7 ms L100.CMDNNJ-VFTTP-35.verizon-gni.net [98.110.91.1]
4 8 ms 7 ms 9 ms 3-0-5-335.CMDNNJ-LCR-03.verizon-gni.net [130.81.140.206]
5 15 ms 14 ms 37 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
6 19 ms 19 ms 20 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
7 73 ms 20 ms 16 ms 0.xe-10-1-0.BR3.NYC4.ALTER.NET [152.63.17.57]
8 19 ms 20 ms 17 ms te-7-1-0.edge2.NewYork2.level3.net [4.68.127.21]
9 18 ms 17 ms 17 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
10 20 ms 19 ms 20 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
11 31 ms 22 ms 17 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
12 21 ms 19 ms 18 ms ae-3-89.edge1.NewYork1.Level3.net [4.68.16.142]
13 22 ms 19 ms 17 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.82]
14 22 ms 19 ms 19 ms 72.14.238.232
15 23 ms 17 ms 26 ms 209.85.241.222
16 22 ms 19 ms 19 ms lga15s04-in-f104.1e100.net [66.249.90.104]

Posts: 86 · Vonage Forum Senior Joined: Jan 03, 2009 Posts: 86

Can a successful traceroute / tracert be done on PC1?

Do nslookup for vonage.net and add the name servers ((DNS) to PC1. Also the 2wire or actiontec router's firewall may need to be configured to allow UDP ports 10000-20000 and 69 to PC1. And PC 1 firewall will need to allow the same to the telephone adapter.
A wireless switch may be a better solution for extending the 802.11 WiFi to Ethernet 802.3.

Posts: 7 · New Forum Member Joined: Mar 06, 2010 Posts: 7

tracert to vonage.net fails from PC1 also at the same point

When I do a nslookup, I dont get any details on name servers ...

nslookup vonage.net
Server: Wireless_Broadband_Router.home
Address: 192.168.1.1

Non-authoritative answer:
Name: vonage.net
Address: 69.59.253.143

So what should I add.

How do I allow multiple ports on the windows firewall.

Posts: 656 · Posted: Wed Mar 10, 2010 6:52 pm Post subject:

Your barking up the wrong tree. There is nothing wrong with your traceroute.

Your packets are making to the Level 3 side of the Vonage Border Router however since your tracing to a domain name without a host, there is not a physical machine that can reply back to your ICMP request.

if you were to add a host such as tftp.vonage.net, it would then complete to an actual machine that can reply back to your ICMP. Going just to vonage.net will get you over to the AS number which will stop at the external interface of the Vonage border router on the Level 3 IP link.

This is also not DNS related since the Vonage TA uses Vonage's own DNS servers which are hardcoded into the profile from the initial image. It does not use the DNS servers assigned or obtained on the WAN port.

This is most likely an issue with the Windows firewall not allowing the SIP service through on UDP port 10000. By default it is allowing HTTP which is why PC2 can browse the web. I bet many services outside of basic web and e-mail would not work through ICS unless PC1's firewall was told to do so.