Crazy network problem - at wit's end! VPN, RD

March 30, 2011 at 22:00:35
Specs: Mac, Win7, WinXP
Our shop has been having a weird and really tiring network problem for the last week. We connect to an server at our Point-of-sale (and others) using Remote Desktop connection, but suddenly could not. Still had network connection, just couldn't ping or tracert to the server. We're on Frontier, and they first diagnosed it as an IP migration (from Verizon I suppose), then that maybe we were blacklisted, then they just didn't know. We've since kept our other PCs at the shop running through Frontier, but have tethered an iPhone on ATT to the POS, which works but is super slow. Fed up with that and not wanting to jump to another provider, I've recently thought we could just use a VPN and step around the Frontier issue... And here's where I'm stumped. From at home I can use a browser to connect to their network (on Mac OS) using the VPN (also have Frontier at home), and at work can use the same VPN and get their server on my iPhone (on the internal Wifi network, not 3G, which is what we had tethered via), but all the other PCs at the shop still can't get there even through the VPN. The VPN uses PPTP (also tried OpenVPN), and our dd-wrt router is properly configured with PPTP pass-through. I'm running out of ideas here. Any clues? Need more info?

See More: Crazy network problem - at wits end! VPN, RD

Report •


#1
March 31, 2011 at 07:11:43
As i answer this while on Frontier Wireless...

I've had many problems with Frontier personally as well as others I know. You might want to see if you can switch as I'm pretty sure Frontier screwed up on you.

At least they didn't tell you that water got in the line and it was making your packets get all soggy as the problem like they told my friend.


Report •

#2
March 31, 2011 at 07:15:27
Sometimes updates change firewall rules. What error messages do you get? Have you looked at the event viewer for errors?

How do you know when a politician is lying? His mouth is moving.


Report •

#3
March 31, 2011 at 08:09:18
if the base layer isn't working right you don't add complexity [vpn] on top of it.

first step is you need to tell us your network topology as in what connects to what.
for example you say you rdp to the server. Is this server on your lan, across a wan link or what?
what routers connect each end?
do you have access to the server?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
March 31, 2011 at 08:58:52
Ok - I'll try to describe our network here. We have PCs that connect via wifi or lan to a router that then connects to dsl modem etc. The server we connect to is in Atlanta, GA - we're in Illinois. I know that if a browser can get to their website (addicosolutions.com), then we'll be able to get there via remote desktop. If just on our Frontier network, we can't reach it, but on ATT (or Comcast, Sprint, etc.) we can. PCs are running Win7.

Report •

#5
March 31, 2011 at 10:54:18
when on the frontier network do a tracert addicosolutions.com and post it for review.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#6
March 31, 2011 at 12:54:10
Here's a tracert

Tracing route to addicosolutions.com [66.163.229.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 2 ms 1 ms 5 ms DD-WRT [192.168.1.2]
3 3 ms 2 ms 2 ms dslrouter [192.168.1.1]
4 24 ms 24 ms 25 ms 50.44.129.3
5 31 ms 25 ms 23 ms 50.40.32.57
6 28 ms 27 ms 27 ms 74.42.149.137
7 29 ms 28 ms 27 ms xe--10-3-0---0.cor02.chcg.il.frontiernet.net [74
.40.1.97]
8 28 ms 27 ms 27 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
9 59 ms 53 ms 53 ms Vlan505.icore1.CT8-Chicago.as6453.net [206.82.14
1.105]
10 49 ms 50 ms 52 ms ix-13-12.icore1.CT8-Chicago.as6453.net [206.82.1
41.38]
11 50 ms 51 ms 52 ms te0-2-0-1.ccr22.ord01.atlas.cogentco.com [154.54
.29.21]
12 51 ms 51 ms 50 ms te0-2-0-0.mpd21.ord01.atlas.cogentco.com [154.54
.7.110]
13 53 ms 55 ms 52 ms te0-1-0-5.mpd21.atl01.atlas.cogentco.com [154.54
.29.66]
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.


Report •

#7
March 31, 2011 at 13:12:20
I get similar results at about the 12th hop.
I can not ping that coms associated ip address. Could be they have icmp set to not be responded to.

This would indicate a internet routing issue that is not Frontier or ISP specific.

Usually these things fix themselves.

How about a tracert from the working connection for comparison?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#8
March 31, 2011 at 14:20:01
Here it is from a tethered phone. Is it odd that it times out? Works fine, though.

Tracing route to addicosolutions.com [66.163.229.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.20.10.17
2 359 ms 469 ms 430 ms 172.26.236.2
3 369 ms 459 ms 489 ms 172.16.206.106
4 442 ms 113 ms 111 ms 172.16.207.241
5 148 ms 101 ms 101 ms 172.16.207.117
6 148 ms 97 ms 103 ms 172.16.213.5
7 150 ms 107 ms 109 ms 12.91.232.9
8 198 ms 120 ms 109 ms cr83.cgcil.ip.att.net [12.122.133.2]
9 106 ms 109 ms 109 ms cr1.cgcil.ip.att.net [12.123.7.110]
10 105 ms 119 ms 111 ms ggr3.cgcil.ip.att.net [12.122.133.9]
11 110 ms 112 ms 101 ms 192.205.34.198
12 162 ms 131 ms 143 ms dls-bb1-link.telia.net [213.248.80.149]
13 148 ms 159 ms 171 ms atl-bb1-link.telia.net [80.91.246.73]
14 162 ms 169 ms 147 ms tulix-ic-123900-atl-bb1.c.telia.net [213.248.77.
26]
15 166 ms 169 ms 153 ms atldc-dist2-ge0-28.atldc.com [208.75.224.30]
16 150 ms 185 ms 145 ms dt-dist-1-sitesouth.com [208.75.224.102]
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.


Report •

#9
March 31, 2011 at 14:31:37
this tracert looks almost exactly like mine with the last site being sitesouth.com

I would see if you can contact someone at the web site you want to reach and share with them these tracert results. This is hurting their business and they don't even know it. Them talking to their web host/isp may get folks looking at this to then get it corrected.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#10
March 31, 2011 at 14:50:18
I've had them on the phone, along with Sitesouth techs - both lay blame on the Frontier end.

Report •

#11
April 2, 2011 at 16:45:31
Well, it's working now. I'd like to think that someone from the forums just flipped a switch and turned it on! Thanks!

Report •


Ask Question