OK, this is now getting really beyond a joke. It's almost a month since I reported the initial issue of not being able to connect to my external e-mail provider.
It's been 3 weeks since I reported I cannot access a number of .mil sites that I need to do my "day job".
I've been through too many calls and up to now, 2 supervisors, the first who promised faithfully to keep me updated with progress and I haven't heard of since. The last supervisor suggested they come out and change my modem. Please, is that your suggestion for everything.
So, before I go postal at the local office, what else can I do to try and get someone with some real influence to look at this, before I get fired from my "day job".
As a test, I put both of these addresses below into browser and both reached the intended website without issue. So from Austin Texas routing seems to work. just fyi
https://webhosting.att.com/ Web Design, Web Hosting & Online Marketing | AT&T Website Solutions
https://websitesmail.att.com/#/login Webmail 7.0
Also, your Aliases don't seem to work.
contac the mil sites help desk,,,
Already tried that. No problems, and the Help Desk could reach all the sites with out any problem. Just like @redrock could get to my AT&T mail provider, which I still can't.
Also, your Aliases don't seem to work.
Not sure what you meant there.
wonder if he's on a vpn or has gov mandated spyware...
A couple of the Web addresses I'm trying to get to are in fact VPN gateways, but no spyware.
For the last week, I've been running traces to both my POP3 account and also to one of the .mil sites. The results, especially for the POP3 is interesting.
For the .mil:
02/15/18-17:03:12 - Script started offline 02/16/18-22:51:38 - Offline for 107306 seconds 02/16/18-23:53:41 - Online for 3723 seconds 02/18/18-04:15:28 - Offline for 102107 seconds 02/18/18-04:15:43 - Online for 15 seconds 02/18/18-23:51:47 - Offline for 70564 seconds 02/19/18-00:52:58 - Online for 3671 seconds 02/21/18-00:50:53 - Offline for 172675 seconds 02/21/18-01:51:37 - Online for 3644 seconds 02/21/18-02:06:08 - Offline for 871 seconds 02/21/18-02:06:23 - Online for 15 seconds 02/23/18-01:51:27 - Offline for 171904 seconds 02/23/18-01:51:42 - Online for 15 seconds 02/25/18-01:52:34 - Offline for 172852 seconds 02/25/18-02:52:42 - Online for 3608 seconds 02/26/18-15:39:55 - Script killed after 132433 seconds 02/26/18-15:54:16 - Script started offline 03/01/18-02:51:05 - Offline for 212209 seconds 03/01/18-03:51:02 - Online for 3597 seconds
And the POP3:
02/28/18-01:03:23 - Offline for 7141 seconds 02/28/18-01:04:03 - Online for 40 seconds 02/28/18-03:03:25 - Offline for 7162 seconds 02/28/18-03:04:26 - Online for 61 seconds 02/28/18-05:03:26 - Offline for 7140 seconds 02/28/18-05:04:22 - Online for 56 seconds 02/28/18-07:03:25 - Offline for 7143 seconds 02/28/18-07:04:26 - Online for 61 seconds 02/28/18-09:03:26 - Offline for 7140 seconds 02/28/18-09:04:07 - Online for 41 seconds 02/28/18-11:03:47 - Offline for 7180 seconds 02/28/18-11:04:22 - Online for 35 seconds 02/28/18-13:03:22 - Offline for 7140 seconds 02/28/18-13:04:44 - Online for 82 seconds 02/28/18-15:03:22 - Offline for 7118 seconds 02/28/18-15:04:08 - Online for 46 seconds 02/28/18-17:03:23 - Offline for 7155 seconds 02/28/18-17:04:24 - Online for 61 seconds 02/28/18-19:03:39 - Offline for 7155 seconds 02/28/18-19:04:15 - Online for 36 seconds 02/28/18-21:03:30 - Offline for 7155 seconds Not really on-line for 20 minutes. Port was in FIN_WAIT1 which has a longer time-out 02/28/18-21:20:23 - Online for 1013 seconds 02/28/18-23:03:25 - Offline for 6182 seconds 02/28/18-23:04:21 - Online for 56 seconds 03/01/18-01:03:28 - Offline for 7147 seconds Not really on-line for 20 minutes. Port was in FIN_WAIT1 which has a longer time-out 03/01/18-01:19:30 - Online for 962 seconds 03/01/18-03:03:14 - Offline for 6224 seconds 03/01/18-03:05:01 - Online for 107 seconds 03/01/18-05:03:15 - Offline for 7094 seconds 03/01/18-05:04:06 - Online for 51 seconds 03/01/18-07:03:29 - Offline for 7163 seconds 03/01/18-07:04:25 - Online for 56 seconds 03/01/18-09:03:17 - Offline for 7132 seconds Not really on-line for 20 minutes. Port was in FIN_WAIT1 which has a longer time-out 03/01/18-09:20:34 - Online for 1037 seconds
Oh, and BTW. I can get to all the sites without issue if I either use my phone as a hot-spot. Or I drag a couple of laptops to the local StarSucks.
Care to explain how a modem problem can cause an issue to the same handful of IP addresses solidly, and no others. But WTH.
|Channel||Lock Status||Modulation||Channel ID||Frequency||Power||SNR||Corrected||Uncorrectables|
|1||Locked||QAM256||9||567000000 Hz||8.9 dBmV||41.9 dB||41||151|
|2||Locked||QAM256||10||573000000 Hz||8.7 dBmV||41.6 dB||42||112|
|3||Locked||QAM256||11||579000000 Hz||8.7 dBmV||41.5 dB||45||160|
|4||Locked||QAM256||12||585000000 Hz||8.6 dBmV||41.3 dB||53||166|
|5||Locked||QAM256||13||591000000 Hz||8.7 dBmV||40.9 dB||43||175|
|6||Locked||QAM256||14||597000000 Hz||8.3 dBmV||40.7 dB||49||129|
|7||Locked||QAM256||18||621000000 Hz||8.6 dBmV||40.4 dB||54||153|
|8||Locked||QAM256||16||609000000 Hz||8.6 dBmV||40.6 dB||79||33|
|9||Locked||QAM256||17||615000000 Hz||8.6 dBmV||40.5 dB||48||159|
|10||Locked||QAM256||20||633000000 Hz||8.7 dBmV||40.3 dB||62||67|
|11||Locked||QAM256||31||699000000 Hz||8.6 dBmV||40.0 dB||36||28|
|12||Locked||QAM256||27||675000000 Hz||9.1 dBmV||40.0 dB||55||58|
|13||Locked||QAM256||28||681000000 Hz||9.2 dBmV||40.2 dB||34||45|
|14||Locked||QAM256||29||687000000 Hz||9.0 dBmV||40.1 dB||23||29|
|15||Locked||QAM256||26||669000000 Hz||9.1 dBmV||40.2 dB||37||45|
|16||Locked||QAM256||32||705000000 Hz||8.5 dBmV||39.9 dB||29||29|
|Channel||Lock Status||US Channel Type||Channel ID||Symbol Rate||Frequency||Power|
|1||Locked||ATDMA||19||5120 Ksym/sec||30600000 Hz||43.8 dBmV|
|2||Locked||TDMA||17||2560 Ksym/sec||18500000 Hz||41.8 dBmV|
|3||Locked||ATDMA||18||5120 Ksym/sec||23300000 Hz||42.0 dBmV|
|4||Locked||ATDMA||20||5120 Ksym/sec||37000000 Hz||43.5 dBmV|
You have broadcast TV/ 4G cellular ingress and noise resulting in skipped channels, uncorrected on others. VPN's can't handle ANY uncorrectables, especially on the home channel.
Ccorrectables and uncorrectables, especially if it's node wide, slow down everyone on the node and results in timeouts, 403/404 errors to some sites, especially if your malware and av are trying to resolve the site.
Something is corroded or loose, it needs to be fixed before you can troubleshoot further.
Otherwise you're beating a dead horse.
Copy and paste a cmd level tracert to google.com and then a site you can't connect to:
that should show excessive times, note how long it takes to resolve a route after the first hop to your router.