No problem with me from PLDT myDSL Biz and Fibr. With Fibr I just have to
use their DNS or the reply gets overridden/dropped.
Try using PLDT's DNS, maybe they give a different route which works. I
might have encountered this before with our office DSL but didn't get to
capture evidence.
On Tue,
To add a few more details to my previous email:* .signin.aws.amazon.com is a CNAME for signin.aws.amazon.com.* signin.aws.amazon.com in turn resolves to various IP addresses (some sort of round-robin), some of which I *can* access over SSL and some of which I *cannot*.* Adding one of the working IP
Hi,
Dan, I don't think it's a DNS issue because I can resolve the hostname and it's
the same IP when querying from my local and other servers.
Fooler, based on the traceroute, it seems to be some kind of firewall issue on
PLDT's side (plus I'm unable to telnet to port 443). I've forwarded it t
hi rob,
basically the correct way to access AWS console is:
https://.signin.aws.amazon.com/console
replace with your AWS account name.
if you think your are still having a problem do the following"
1) "nslookup .signin.aws.amazon.com" in case if
you have DNS lookup problem
2) "telnet .signin.
I was Amazon that was broken.
>From what I've gathered it may well have been DNS related.
Dan
On Nov 18, 2013, at 9:53 PM, John Homer H Alvero wrote:
> Send tracert / mtr to netres_c...@pldt.com.ph
>
>
>
>
> On Mon, Nov 18, 2013 at 9:45 PM, Ben Adrian Sarmiento
> wrote:
> Mine's fine. 8
Send tracert / mtr to netres_c...@pldt.com.ph
On Mon, Nov 18, 2013 at 9:45 PM, Ben Adrian Sarmiento <
benadriansarmie...@gmail.com> wrote:
> Mine's fine. 8mbps business line btw.
> On Nov 18, 2013 9:40 PM, "Robert Locke" wrote:
>
>>
>> The plot thickens. I know at least 1 other person who ca
Just checked from my home DSL. It's working fine for me.
On Nov 18, 2013, at 21:45, Ben Adrian Sarmiento
wrote:
> Mine's fine. 8mbps business line btw.
>
> On Nov 18, 2013 9:40 PM, "Robert Locke" wrote:
>
> The plot thickens. I know at least 1 other person who can't access the
> console on
Mine's fine. 8mbps business line btw.
On Nov 18, 2013 9:40 PM, "Robert Locke" wrote:
>
> The plot thickens. I know at least 1 other person who can't access the
> console on myDSL (as does Zak it appears).
>
> Weird. Any ideas on who to talk to?
>
> Thanks! Rob
>
>
> On Nov 18, 2013, at 7:21 PM,
The plot thickens. I know at least 1 other person who can't access the console
on myDSL (as does Zak it appears).
Weird. Any ideas on who to talk to?
Thanks! Rob
On Nov 18, 2013, at 7:21 PM, Ramon Tayag wrote:
> Rob, not sure this helps, but I'm on a MyDSL connection and don't have issues
Rob, not sure this helps, but I'm on a MyDSL connection and don't have
issues accessing the console.
Ramon Tayag
On Mon, Nov 18, 2013 at 4:19 PM, Robert Locke wrote:
> Hi gang,
>
> Not really a Linux question, but I'm wondering if anyone else is having
> problems reaching the AWS console login
Yeah some folks are experiencing that. Curiously it doesn't seem to happen
on smart (which shares connectivity with pldt)
On Nov 18, 2013 4:20 PM, "Robert Locke" wrote:
> Hi gang,
>
> Not really a Linux question, but I'm wondering if anyone else is having
> problems reaching the AWS console login
Hi gang,
Not really a Linux question, but I'm wondering if anyone else is having
problems reaching the AWS console login page on a PLDT DSL connection:
https://console.aws.amazon.com/
For the past few weeks I've had to use a VPN to access it. But only when I'm
on my home PLDT DSL conne
12 matches
Mail list logo
