Frontier connectivity issue

[McLovin]

So not only myself, but quite a few of my clients have had an issue with internet service over the past 2 weeks or so. We are all on Frontier DSL and the issue we've been having is that either some web pages won't come up at all or like my major client,everything will work fine but RDP will not.

I had my SE567 Modem/Router setup as a bridge to my D-Link DGL-4500 and everything has worked ok for the past 8 months or so. I started having certain websites and such not come up, so my troubleshooting led me to do tracert's to all the websites I'd been having issues with. The tracert was able to pickup the websites IP, leave my home network, and start working its way across the web until it hits a certain point then the request times out. After having frontier replace the modem and re-setup the bridge to my router, I still had the same problem. I removed my router entirely and set the SE567 back to default and was able to hop on the internet and tracert's complete with no issue.

My client who is having RDP issues, had a SE567 as well with no problems browsing the web, but obviously could not use RDP. Tracert shows the same symptoms as my issue. Frontier came out and replaced the modem, but we are still having the same problem.

Seems to me that it's a DNS issue but how in the world am I supposed to fix that? Isn't that an ISP issue?

 

[McLovin]

Anyone have any thoughts at all? I tried to explain the situation the best I could, so if my description isn't very good or help ful let me know.

 

[degibson]

Seems to me that it's a DNS issue but how in the world am I supposed to fix that? Isn't that an ISP issue?

Not likely a DNS issue if your tracert can figure out the IP. You might want to make sure its the same IP that a non-Frontier customer sees.

Speaking of which, if *all* Frontier customers cannot see the same set of sites, it could be an intentional or accidental traffic filter on the part of Frontier or one of their upstream providers.

 

[McLovin]

Not likely a DNS issue if your tracert can figure out the IP. You might want to make sure its the same IP that a non-Frontier customer sees.

Speaking of which, if *all* Frontier customers cannot see the same set of sites, it could be an intentional or accidental traffic filter on the part of Frontier or one of their upstream providers.

Well see the server that we are trying to RDP to, is on a frontier connection. the CA office has absolutely no problems getting online and I can RDP in to the server no problem.

The client's computer we are trying to RDP from, does not have a static IP setup for it's lan based connection and does not, based on scan results from MSE and Malwarebytes, appear to have any infections. Frontier is adamant in its refusal to do anything else to resolve the issue because it's "not their problem".

 

[kevnich2]

Are you RDP'ing to a hostname (example.domain.com) or an IP address (123.45.56.78)?

 

[McLovin]

RDP'ing to an IP address

 

[Crusty]

RDP'ing to an IP address

Then it's definitely not a DNS issue.

 

[bruceb]

On the computer that can not do the RDP, check the firewall settings to be sure that the program being used for RDP is not blocked in the firewall. You also may need to open a specific port that is being used by the RDP program on his Router

 

[McLovin]

I'm using Remote Desktop Connection in Windows 7 and I do have the port forwarded on the router where the server is. Are you saying I'd need to also do a port forward on the frontier modem/router?

 

[McLovin]

I should also mention that as of last friday, the office in question that's been having the RDP issue, had no problems using RDC at all for the past 2 months.

 

[kevnich2]

Can you RDP from another computer on the same network? If you can - the firewall settings of the computer where the RDP is at (server RDP system) should be fine. Next step would be something in the router/firewall at the office itself. Make sure port 3389 is forwarded to the correct internal IP address. Is the office on a static or dynamic IP address?

 

[McLovin]

Can you RDP from another computer on the same network? If you can - the firewall settings of the computer where the RDP is at (server RDP system) should be fine. Next step would be something in the router/firewall at the office itself. Make sure port 3389 is forwarded to the correct internal IP address. Is the office on a static or dynamic IP address?

RDP'ing from a local machine at the Server Office works just fine. I took a laptop up to the other office just to make sure it wasn't the machine itself and the laptop could not RDP to the server. I came back up to the other office today and the following tracert:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\River Valley AC>tracert xx.xx.xx.xxx
Tracing route to static-xx-xx-xx-xxx.dsl2.kgm.az.frontiernet.net [xx.xx.xx.xxx]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms sx762.subscriber.frontiernet.net [192.168.254.25
4]
2 6 ms 6 ms 6 ms 74-33-0-1.dsl1.kgmn.az.frontiernet.net [74.33.0.
1]
3 6 ms 7 ms 6 ms 216.67.222.29
4 6 ms 7 ms 6 ms 216.67.222.14
5 7 ms 8 ms 9 ms 216.67.222.29
6 7 ms 7 ms 7 ms 216.67.222.14
7 6 ms 8 ms 8 ms 216.67.222.29
8 7 ms 6 ms 6 ms 216.67.222.14
9 10 ms 9 ms 7 ms 216.67.222.29
10 7 ms 6 ms 6 ms 216.67.222.14
11 7 ms 9 ms 7 ms 216.67.222.29
12 9 ms 8 ms 7 ms 216.67.222.14
13 9 ms 10 ms 7 ms 216.67.222.29
14 8 ms 8 ms 7 ms 216.67.222.14
15 8 ms 8 ms 8 ms 216.67.222.29
16 8 ms 8 ms 8 ms 216.67.222.14
17 8 ms 8 ms 9 ms 216.67.222.29
18 8 ms 9 ms 11 ms 216.67.222.14
19 9 ms 9 ms 9 ms 216.67.222.29
20 8 ms 8 ms 8 ms 216.67.222.14
21 10 ms 10 ms 9 ms 216.67.222.29
22 8 ms 24 ms 12 ms 216.67.222.14
23 10 ms 8 ms 10 ms 216.67.222.29
24 10 ms 16 ms 10 ms 216.67.222.14
25 8 ms 11 ms 8 ms 216.67.222.29
26 10 ms 9 ms 8 ms 216.67.222.14
27 10 ms 11 ms 9 ms 216.67.222.29
28 8 ms 12 ms 10 ms 216.67.222.14
29 10 ms 10 ms 12 ms 216.67.222.29
30 10 ms 9 ms 12 ms 216.67.222.14

Trace complete.

I can assure you neither of those IP's are even close to what the destination IP is.

I also did port forwarding for TCP and UDP to the correct computer and nothing changed.

 

[McLovin]

This is the ping and tracert logs going from the CA Office (where the server is at( to the AZ Office (office that can't RDP)Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\xxxxxxxx>ping xx.xxx.xxx.xxx.

Pinging xx.xxx.xxx.xxxx with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for xx.xxx.xxx.xxx:
Packets: Sent = 4, Received = 0, Lost = 4 (100&#37; loss),

C:\Users\xxxxxxx>tracert xx.xxx.xxx.xxx

Tracing route to xx.xxx.xxx.xxx.dsl1.kgm.az.frontiernet.net [xx.xxx.xxx.xxx]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 1 ms 1 ms 1 ms static-xxx.xxx.xxx.xxx..dsl2.kgm.az.frontiernet.net
[xxx.xxx.xxx.xxx]
3 19 ms 14 ms 17 ms 74-47-96-1.dr02.kgmn.az.frontiernet.net [74.47.9
6.1]
4 21 ms 17 ms 17 ms gi9-0-0.dr01.kgmn.az.frontiernet.net [74.40.38.2
02]
5 16 ms 17 ms 20 ms dsl1.kgmm.az.frontiernet.net [216.67.222.30]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

 

[Crusty]

Send frontier your first tracert that has the routing loop in it. It's definitely their problem.